PieFed is unfortunately pretty poorly documented. There's a brief overview of theming that seems to be directed at people who don't know CSS, but that's pretty much it. If you want to create your own theme, their recommendation is to just...inspect whatever element you want to change and then start a stylesheet from scratch. Which is completely bizarre compared to any other similar software I've ever used, which always includes some kind of "default" theme you can tweak to your liking.

Ooooo. Or even just a color palette! Would love to use it in my various Internet escapades!

Yeah, that is the kind of behavior I would expect from someone that would use an LLM to scan an entire codebase to find issues... fucking hell, people.

Thanks for reacting quickly to this mess, though. <3

Someone ran an LLM through the piefed codebase to identify possible exploits and found a couple. And then, rather than holding off public disclosure of the exploits to give the devs and admins time to fix the issue, they announced the full details of the exploit in public.

It appears to have been a deliberate attempt to discredit Piefed and the lead Piefed dev, without any consideration of the impact it has on anyone else.

Piefed.social went down for what they called urgent maintenance. Just a couple hours before this. That can't be a coincidence. I'm assuming the reason why no one is saying anything for now is to keep other Piefed instances safe.

Thanks for the info! It’s not urgent obviously, I just couldn’t figure out if it was an issue on my end.

We had customised the way modlogs work on our version of Piefed, but it broke somewhere along the line. It's on the list to be looked at and fixed and/or reverted to stock

They're not doing that good of a job. Noted though. I respect your decision. I'll delete this thread and block the entire instance on my account, I don't want it to happen again.

If you check the most recent edit we long ago refederated with programming.dev. It was a temporary measure to avoid some abusive spam. The admins of programming.dev are very active to work against this sort of stuff and we are now in frequent contact with them.

Thank you, I'll do that.

You're moderating across instances, and from piefed to lemmy. Moderation on the threadiverse is only completely reliable when done with an account on the same instance that hosts the community. Other mods can help, but they won't see all reports, you can't rely on their removals federating properly, and you get moments like this.

I'd suggest making yourself a lemmy.world account just for moderation, add it as a mod with your blahaj account, and then do the updates from the lemmy.world account.

Yeah I assumed as much. Generally other mod actions for that community from this account works without issue, so I'm curious if this particular case is a known problem or not.

It's usually best to moderate with a local account from my experience

Thanks for the explanation, and I probably should have assumed y’all were already on it! Good to know it won’t be an issue going forward, and thanks for all the work you do 👏

Ok, so we had a bunch of emojis in our database that weren't delimited with a : so they were called things like red instead of :red:. It didn't cause an issue until we upgraded to 1.6, because inline emojis were not available in the version we were running.

So when we updated to 1.6 (around 6 hours ago), there was a window of about 3 hours, where text in posts and comments that mentioned any of those undelimited emoji names, would get replaced with the emoji (but only on our instance). We updated the emoji list to delimit them properly, and it is no longer occurring on new content. Existing content posted or edited during the period where we had the undelimited emoji on 1.6 will continue to show the emoji, but posts made before or after that window are fine. There's no way for us to identify or push a fix to the posts that made it through, though if any of them belong to you, you can edit the post, which will fix it.

Somewhat. But when writing in Spanish, Portuguese, French, Italian, Polish, Croatian, Ukrainian, Czech, Slovak, Slovene, Serbian, Russian, Madeonian, Bulgarian, Latvian or Lithuanian (and maybe Greek? And how about the Gaelic languages?), you do need the information about genders when writing an adjective about the person you are talking to. So in Spanish "you are lovely" is "eres encantador" or "eres encantadora" depending of whether you're talking to a man or a woman.

Additionally, in most Slavic languages, whenever you talk about anything that has happened in the past, you must always tell the gender of the subject.

So, "Anna, you flew!" and "Michał, you flew!"
are in Polish "Anna, ty poleciałaś!" and "Michał, ty poleciałeś!".

You almost always need to know the gender of the person when talking to them in a Slavic language, and you often need to know it when talking to them in a Romanic language. So, good info to have!

(...and of for me, as a Finn... In my mother tongue there is never any need to know the other person's gender when talking to or about them. Except if you want to explicitly use the words "man", "woman", "boy" or "girl". But even then you can just say "adult" or "child", so whatever.
Every Finn lives their first 7 years without caring a damn about their conversation partners' genders. They are all just people, and that's enough for almost any situation.
It's interesting how often you see children in English classes get angry at the teacher for having to differentiate between "he" and "she". An argument I've often heard is "It is such a hassle for no reason!"
In my eyes, all these very visible gender declarations are programming my brain towards thinking more about people's genders, while I would prefer just ignoring the whole concept of genders in my thinking.)

most people won’t read it since they’re conditioned to ignore this normally useless text.

They might actually very well read it, because they'll eventually notice the information might be there and would know to look for it.

But the chosen solution with flairs will work very well, probably a bit better even :)

Thank you for your ideas and feedback, everyone!

I'm going to make it so that when someone adds pronouns to their Extra Fields it will also be shown as a flair beside their name, like this:

That flair will be used wherever you haven't set a community-level flair. If you've set a flair within a community that'll be used on posts in that community instead.

If the same pronouns are in the display name then the flair isn't shown, to avoid showing it twice.

Because the pronoun flair comes from the Extra Fields, it's already public information so there's no possibility of unexpectedly disclosing it in places where you'd rather not (it'll always be public everywhere, this change just boosts it's visibility). I love the idea of having proper controls over who sees it and when but ActivityPub doesn't have fine-grained access control built in to the protocol so I'd rather not go there and become responsible for sensitive data.

@ada@piefed.blahaj.zone @catfeeder@piefed.blahaj.zone @hildegarde@lemmy.blahaj.zone

What you’d need are the pronouns of the person you’re writing about, not to

Oh yeah! That does take the shine off it somewhat.

I might be in the minority here, but I like the options we have today.

Individuals can choose to include their pronouns in their display name if they like. This info is highly visible, being present on all posts and comments a person leaves. If users want to broadcast their pronouns this way, they're welcome to do so.

But I also appreciate the flexibility for people who want to make their pronouns available to anyone interested, but not necessarily make it a part of their display name. I'm in that camp. For people like me, keeping a slot for pronouns in the user's profile / bio page is perfect.

Being able to do both, either or neither is great!

I absolutely love the creativity of using auto-clearing placeholder text in a reply's text body to remind folks of pronouns. That's really cool! But as a practical matter, when I write a reply to someone I'm always using English second-person pronouns (you/your/yours), so I generally don't need to know the gender/pronouns of the person I'm replying to. What you'd need are the pronouns of the person you're writing about, not to. It's still a slick idea, though!

Only showing pronouns to others with pronouns, and users of the same instance were the two specific cases I mentioned later in the initial comment.

Oh, you're right, that part somehow escaped my attention 😅

I however am unfamiliar with any of the technical specifics behind the fediverse. Could be impossible, infeasible, or easy. We’ll see!

I suspect the hardest part is to make it work with Lemmy too as well as all the mobile apps.

Thx for the clarification! Only showing pronouns to others with pronouns, and users of the same instance were the two specific cases I mentioned later in the initial comment. I feel certain that users with pronouns and users on blahaj are not transphobes!

I however am unfamiliar with any of the technical specifics behind the fediverse. Could be impossible, infeasible, or easy. We'll see!

No, I just worded that comment incorrectly :)

It COULD be made so.

Is that in its current implementation? Apologies I have not yet switched over, and don't know piefed specifics.

Another possibility I would like to bring to the discussion, if possible, would be an ability to choose who the pronouns are shown to.

It could be made so your pronouns would only show up to users who also chose their pronouns. Most transphobes won't bother with setting it up anyway.

edit: poor wording