FYI, next version of PieFed has an “Unban All” button for clearing all domain bans to try to make this easier.

Screenshot from my instance:

PieFed has a default list of domains/instances that are blocked when you do a fresh install for a brand new instance. A critical difference between PieFed and the Tesseract blocks is that any of the blocks in PieFed are completely visible to, and under the control of the admins of the instance. So, ultimately, it is just an out-of-the-box default, but the instance admins always have ultimate control over moderation/federation choices. This Tesseract stuff is taking those powers away from the admins.

there is a work-in-progress page for Piefed that a contributor is working on

Yeah…sorry for the delay on this one. I have been absolutely slammed with irl work and haven’t had time to do much of anything recently. This is also why my actual contributions to PieFed have dried up the past couple weeks. I swear I haven’t forgotten about this, and I think the new structure will make this contribution a lot easier as I don’t have to replicate a lot of what existed for lemmy already.

Yeah, there was recently a case where somebody was doxxed in the modlog. At that moment, there really wasn’t anything that you can do about it. So, being able to have some control over modlog visibility is a way to prevent abuses like that.

No. Anonymous voting used to be in Piefed, but was removed in favor of not federating votes as a user setting instead. Vote manipulation is a thing and this obscures it too much.

I don’t think the privacy issues here are too salient. Pretty much everything on the fediverse is public already and have likely federated outside any particular region like the EU, so GDPR doesn’t really have any teeth. The exception to that would be if instance admins are using database access to also feed private messages to an LLM (especially a corporate LLM). I know that the “private” in private messages on the fediverse can be conditional…but it should at least be considered private from LLMs as an expectation since those messages are inaccessible to things like scraper bots or listening instances designed just to harvest data.

My biggest concerns here would be twofold:

1. False positives - LLM sycophancy is a thing. So, I worry that if you ask an LLM to dig through a big pile of text looking for a thing, that it will tell you that it found that thing…even if it is completely removed from context or completely made up. The false positive rate might be low (I have no idea), but I guess I just don’t trust the LLM enough to let it take the wheel with stuff like this.
2. Outsourcing moderation - LLMs are not going to be up to the task of moderating everything, just ask digg. However, tools to help moderators effectively do their jobs are helpful as well. There is a balance to be struck here. I think, for me, something like asking an AI essentially, should I ban this person, just feels like you are outsourcing your decision making too much. It is too far on the automation side of the scale for my tastes.

All that said, people can run their instances how they want. I don’t really have strong opinions on LLMs/AI in general, I just kinda hate big tech companies. That is my foundational belief in the work that I do for the fediverse - fuck big tech and the oligarchy they have built/funded in my country. That is really the only axe I have to grind in all this.

When I am translating from Japanese, I find that DeepL is the most consistently understandable and accurate. I have copy/pasted many an article from Comic Natalie into translators to compare with what Anime News Network writes, and that is my experience.

In general, the popups don’t work great on mobile. We have them on lots of other UI elements (like navbar buttons in the upper right on desktop) and they are a native Bootstrap thing (the css framework we use). However, they aren’t really touch friendly, and seem to get stuck a lot (even on desktop). If any web dev folks out there know a better solution for this functionality, we are open for suggestions.

piefed.social seems to be having some federation issues in general right now. Hang tight until its Kiwi time and rimu will likely kick the server.

I am not sure what you mean by pop out? Do you have an example or a screenshot?

As for blurring, that could be caused by post flair. I have seen some communities in the past create a post flair called NSFW that applies blurring in addition to the actual NSFW flag that can be set. The post flair causing blurs is an option that community mods can set when they create/edit the post flair. The intention behind that was for stuff like spoiler blurring, but there isn’t anything stopping them from applying it to whatever they want.

This is happening because at least one user from your instance is a moderator for the community. This issue has been reported previously to us in matrix. Here is the relevant issue on codeberg. I have previously tried to figure out what is causing this to happen to no avail. It seems like whenever PieFed tries to send a report to a moderator, lemmy will also send it to the admins on that instance.

Maybe if @rimu@piefed.social gets a chance to dig into this some more, he can figure out how to prevent the reports from escalating to admins when they should stay at the mod level.

Go to their user profile page and click the More dropdown. You can then select Edit note. This lets you put a bit of text next to their username wherever you see it.

As an example, I made a note for rimu’s account and I can see it in the sidebar because he is the moderator:

Edit: This is in the API as well, but I don’t know what apps do or don’t support this yet.

I am not a webfinger expert, but my understanding is that what lemmy does is not technically compliant and messes stuff up for some other software (relevant github issue).

My thinking on a per-device basis was that themes might work better/worse in a mobile vs. desktop browser, so people might prefer different experiences, but I could see the other side of things as well. That was also the rationale for making compact mode be in the cookie rather than saved in the db.

I honestly don’t know what the expiration of the session cookie is. It might depend on the browser. I think it is pretty long-lasting unless people clear their cache because I have definitely loaded up piefed instances after a long time and have still been logged in.

As for technical details, to save space, it might make sense to make a key (maybe like ignore_comm_theme) be a comma-separated list of community id’s that people have unchecked the box. That means you can easily convert this to a list with split and then see if the currently requested community id is in that list. Being the id means that it is unique for the instance and avoids name collisions like the actual community name might have (how many linux communities do we have now). It also keeps things relatively small since the cookie has a pretty small size limit iirc.

To do this on a per-community basis, it might make sense to store it in the session cookie rather than in the db. Look for instances of response.set_cookie and request.cookies.get to see other examples of where we do that.

Some user settings are stored in the cookie to look at as an example; stuff like the compactness level, low bandwidth mode, etc. Basically anything that is set on a per-device basis rather than stored in the db.

As mentioned already, our API links are in the codeberg: stable and dev branches.

There isn’t yet a pythorhead-like library that I know of, so API requests would need to be done using an http library. As much as I love requests, I believe it is largely unmaintained at this point, so something like httpx might be better (though that is having issues now too, we’ll see). The general workflow for interacting with the API is to make a network request, getting a json back. Then, parse the json in python exactly like you would a dictionary (or nested dictionaries).

Also, you might want to check out the work done over at !lemmydirectory@lemmy.dbzer0.com to see how they do things.

Yes, actually! There are two ways you could force a user to get fetched that I can think of:

1. @-mention them in a post or comment and then click that link after the post/comment is made…if piefed doesn’t already know that user, it will go fetch that user.
2. Just input the lookup url directly. This is what is happening behind the scenes in #1, but the url structure looks like this (looking up myself using piefed.zip as an example): https://piefed.zip/user/lookup/wjs018/piefed.wjs018.xyz

All the comments are there, but they are split across two communities (1 in !sciencefiction@lemmy.world and 8 in !solarpunk@slrpnk.net):

• https://multiverse.soulism.net/c/sciencefiction/p/86593/so-solar-cars-are-a-reality-indeed
• https://multiverse.soulism.net/post/86632

The number of comments under a post in the web UI is the combined number of comments including crossposts.

I am not going to name names or point to specific PRs so as not to shame anybody since that isn’t my intention, but we have had a couple AI-assisted PRs in the past and rimu has generally not been very receptive to them. I even really liked the functionality that one of them provided. However, they have generally been huge in that it is a ton of very verbose code that is difficult to review. I don’t believe that he has an official policy on AI-assisted contributions other than that it is easy enough to review and confirm that it is working as intended as well as not completely changing up coding style and conventions we have used elsewhere.

As a bit of disclosure, I have occasionally used very basic AI queries to help me understand something in a python library I haven’t used before or couldn’t find docs about. A specific case I remember was that I didn’t understand how to do something in the orjson library and I couldn’t find a good example in their docs or on stack overflow. Out of desperation I asked ChatGPT and it gave me a minimum viable example that I was able to adapt to what I needed. I have done similar a couple times when trying to craft regular expressions as well as dealing with some edge cases in the marshmallow python library that I couldn’t find answers for in their docs. I do make sure to test any code I write to make sure that I wasn’t just fed a hallucination or something that applied for an older version of the library but is out of date now.

Brave Bang Bravern! - A great show and one of the finalists for anime of the year from 2024 in this community. It never fails to escalate the weirdness while not losing touch with the heart and what it means to be a hero.