Yep, I’ll document it in some way. A FEP seems overkill as it’s really just adding a bit more data onto Actors and Activities, not a big deal.

You say that like it’s a bad thing.

Lemmy users missing out is THE reason they’ll become PieFed users.

I did the DB structure changes at the same time as the ones needed for community flair as they’re quite similar. Might be able to do the rest tomorrow.

Tags, aka hashtags, are instance-wide (not just in a community) and interoperate with Mastodon, Pixelfed, Mbin. Anyone can make a new hashtag and they are completely unmoderated.

Flairs are a limited list determined by each community’s mods and are only used in that community. They will federate with other PieFed instances and with Lemmy (when they finish coding what they’re calling “tags”, a really unfortunate choice of name).

Watch this space.

Lol, rip

IFTAS is pretty amazing.

Check out these resources - https://connect.iftas.org/library/

They also have a matrix room for moderators to chat with other moderators. PM me for a link, I don’t know how public they want it to be so I won’t put it here.

You’re going to have to prioritise.

Find changes that:

Save a decent amount of money Are low risk Don’t take too long to do Can be easily backed-out of

Yup. In PieFed you can get an alert based on comments on a post, comments in reply to a comment, posts in a community, posts in a topic, posts in a feed, or posts done by a particular person. We’re really gone to town on it.

Increasing amounts of code running on my computer and in the online services I use will be written by generative AI.

Emphasis added by me.

Thing is, it’s not black and white most of the time - usually a developer is using Gen AI as an assistant in some capacity. There are a wide range of ways to do that with really big differences in how firmly their hand remains on the wheel of where things are going. Only in the most extreme “vibe coding” scenario would it be fair to characterize the code as “written by AI”.

There reaches a point somewhere on the spectrum of dependency on AI where quality would suffer and developer capacity-building would be stunted. Where that point is, is a more productive question than a binary Yes or No to all AI.

It’s on the radar, yes.

if you turn off “Show posts from child feeds” on the Forumverse feed then https://piefed.social/f/lemmycategories will load much faster…

This idea is quite similar to what Bluesky is doing, with “Labels” https://docs.bsky.app/docs/advanced-guides/moderation.

We’d need some way to crowdsource the verification and validity of the labels so people can’t just put low-quality or abusive labels everywhere.

It could potentially reduce the amount of work moderators need to do because spam would be labelled as such by anyone and if a few others also label it the same then it would reach a threshold where the label becomes active.

Does anyone have experience with this way of moderating content on Bluesky? How well does it work in practice?

Imagine you want to write a competitor to PostgreSQL and you start out by importing SQLite into your project and building on top of that. To you it seems like a good idea because you’ve never written a DB app before and the only DB you’ve ever seen before is SQLite. You’ll get a prototype real fast but you’ll never build a PostgreSQL equivalent because you never learned the foundational knowledge of how a DB works and because SQLite forecloses all the pathways you need to get there.

Same thing.

Because outsourcing your core business processes is a bad idea. A fediverse app that relies on a library to do all the fediverse stuff is going to have a bad time. Not straight away, but eventually.

Compact mode has been added now, FYI. Screenshots at https://codeberg.org/rimu/pyfedi/issues/540#issuecomment-3788240

Yeah, federation is kinda inherently “wasteful” in that so many copies of everything get made.

There are ways to reign it in a bit, by aggressively pruning old content, leaving original copies of images on their home instance, etc… But fundamentally saving on resources is pretty difficult to do if you want redundancy, decentralisation and resilience.

Not :)

One day it would be cool if the creation and curation and maintenance of feeds more collaborative, like a wiki. Right now one person can squat on a tasty name/url and just do nothing with it, potentially. It’d be great if there was a process to get others involved in each feed, if necessary.

One day…

Great video, thanks!