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.

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

Have you tried it with gunicorn?

Invite code is here: https://piefed.social/post/484755

I have an idea of how to fix that. Other fedi Devs are trying similar things too.

A nice comment is worth more than 1000 upvotes, emotionally.

Cool! Before you dive in, check this out https://join.piefed.social/docs/developers/

I’ve never seen a Lemmy DB, sorry. But I hang out in the Lemmy matrix rooms and read about admins struggling with their 300 GB databases quite often.

Ok. Watch this space: https://codeberg.org/rimu/pyfedi/issues/540

Definitely alpha, yeah. But moving fast!

We won’t 100% know the answer to that until we get there. But in 2025 fear of a lack of CPU cores is NOT what keeps me awake at night.

Early performance results are positive. Check these links out:

https://join.piefed.social/2024/02/13/technical-performance-of-each-fediverse-platform/

https://join.piefed.social/2024/02/09/comparing-network-utilization-of-lemmy-kbin-and-piefed/

There are many many ways to ruin web app performance and choice of backend language is not really a big one. It’s what you do with it that counts.

https://piefed.social/ is running on a low end VPS which costs $7.50 per month. Load average is about 1.45 during the busiest part of the day. Most of the load is caused by federating with lemmy.world and that won’t increase as more users come on board.

PieFed is also really efficient with storage. After 16 months of operation, subscribed to every popular community, the piefed.social DB is 30 GB and the media storage is 28 GB. A Lemmy instance would be 10x that. I haven’t bothered to add S3 storage code because we just don’t need it (yet).

Anyway, all this focus on costs and downsides is only half the coin. There are massive benefits that come from using Python:

• Easy and fun
• Fast development velocity
• Huge amounts of developers know Python
• Extensive and mature libraries with good documentation
• Good readability
• Cross-platform without re-compiling

For a FOSS project where volunteer contributions from people play a big part these things are really important. There are many ways a project can fail (not just technical reasons but social & governance too) and running out of CPU is way way down on the list.

Welcome to the jungle

If you use a mobile app then whether your account is on Lemmy or PieFed makes no difference - most of your experience will be determined by which app you choose.