Google provides a tool called PageSpeed Insights which gives a website some metrics to assess how well it is put together and how fast it loads. There are a lot of technical details but in general green scores are good, orange not great and red is bad.
I tried to ensure the tests were similar for each platform by choosing a page that shows a list of posts, like https://mastodon.social/explore.
The rest don’t seem to have prioritized performance or chose a software architecture that cannot be made to perform well on these metrics. It will be very interesting to see how that affects the cost of running large instances and the longevity of the platforms. Time will tell.
I’m pretty happy with how #moderation tools for #PieFed are coming along!
Moderators can:
delete & edit anything in community
ban people from community, and unban them.
review reports about content in that community
mark a report as resolved / ignored.
When a report is resolved or ignored, all reports regarding that content are also resolved. So if something receives 150 reports then mods won’t need to click 150 times to resolve all reports. Ignored reports stop all future reports from being accepted.
The person who created the community can appoint other moderators.
Reports federate to and from #Lemmy so if a PieFed user reports some content that came from a Lemmy instance the moderators on the Lemmy instance will be notified about the content being reported.
There’s still more to be done with federation of bans, a moderation log, etc. But it’s shaping up nicely!
Hercules was the brand of graphics card for the IBM PC that was widely used in the 1980s.
It could do two colours - black and whatever colour the monitor was. For my first year I had a green monitor and then an amber one for the next two years.
Have you even tried #Piefed? Piefed.social is:
"A lemmy/kbin clone written in Python with Flask.
-Clean, simple code that is easy to understand and contribute to. No fancy design patterns or algorithms.
-Easy setup, easy to manage - few dependencies and extra software required.
-AGPL.
-First class moderation tools."
It's actually really quite nice, and I don't hear much noise about it. Go give this project a look at https://piefed.social.
Be sure to check the Link below in the link that @jeze left and sign up!
Pretty kewl, IMO. Thanks for sharing Elley :) it looks really nice and I created an account for myself. Seamless federation with the others too - very nice :)
A super helpful feature that PieFed (a new fediverse thread aggregator like Lemmy & Kbin) has is an "Add Remote" button on its communities page. This button allows you to get a community on another instance to appear on your PieFed instance (and thus get the PieFed instance to start getting posts from that community)....
Not sure if you noticed but half the #ThreadVerse is memes. They're not my thing but I enjoyed putting together the best meme consumption experience I could.
If you haven't heard, sadly, #ChirpSocial, one of the popular #ActivityPub “groups” platform, is shutting down “probably” on February 29th.
In an email they sent to admins, the owner and developer can no longer support https://chirp.social financially as they failed to find a new job after they were laid off by #Google last year.
This reminds us the importance of having a built-in groups feature, and one where the groups feature actually federates.
Back in 2008, when the #Fediverse was born, we did have a built-in federated groups in #Laconica / #StatusNet (today known as #GNUsocial). We used bang (!) instead of at (@). A built-in groups feature is more stable as established instances can host them.
Today, we have #Friendica and #Hubzilla (as well as #Streams-based instances) to fill in that, as groups is a built-in feature in those software products. It's just a matter of finding an instance that's open to hosting groups for any topic for the ActivityPub protocol.
That said, any Friendica, Hubzilla, Streams-based instances you suggest for groups?
After reading a massive tome about #ElasticSearch earlier this week I realised it was complete overkill and just used the full-text capabilities of #PostgreSQL instead.
Currently PieFed has 46,000 posts and results are fast. It'll be interesting to see how well it copes when there are more posts. Anyone want to make a guess when it'll bog down?
PieFed is a link sharing platform so every post has a 'url' field. By embedding the post url into the RSS feed entry, we get images in our feed if the posts have images. The example I gave in the earlier toot uses images but it could be anything, including video or audio.
Podcasts are just RSS feeds with audio files. This means #PieFed is also a federated #PodCast platform - every community is also a podcast, if the things you post in the community are just links to mp3 files.
For a very small instance with only a couple of concurrent users a CDN might not make much difference. But if you take a look at your web server logs you’ll quickly notice that every post / like / vote triggers a storm of requests from other instances to yours, looking up lots of different things. It’s easy to imagine how quickly this would overwhelm an instance once it gets even a little busy.
One of the first web performance tools people reach for is to use a CDN, like Cloudflare. But how much difference will it make? In this video I show you my web server logs before and after and compare them.
The short answer is – before CDN: 720 requests. After CDN: 100 requests.
Usually just turning on a CDN with default settings will not help very much, you’ll need to configure some caching rules or settings. By watching your server logs for a while you’ll get a sense for what needs to be cached but check out mine for a starting point:
Beware of caching by URI Path because often fediverse software will return different data depending on the Accept header that the requester sets. For example, on PieFed and Lemmy instances a request by a web browser to /post/123 will return HTML to show the post to someone. But when that same URL is requested with the Accept: application/ld+json header set, the response will be an ActivityPub representation of the post! You don’t want people getting activitypub data in their browser and you don’t want to be serving HTML to other instances. Once you spot a URL you want to cache, use a tool like Postman to set the Accept header and make a fake ActivityPub request to your instance and see if you get back HTML or JSON.
Another problem that can happen is that often a response will vary depending on whether the viewer is logged in, or who is logged in. If you can figure out how to configure the CDN to pay attention to cookies or whatever headers are used for Authentication by your platform then you might be able to cache things like /post/*… I couldn’t.
The things I’ve chosen to cache by URI Path above are ones that I know don’t vary by HTTP header or by authentication.
Although we can’t use URI Path a lot of the time, we can cache ActivityPub requests by detecting the Accept: allocation/ld+json header:
https://join.piefed.social/wp-content/uploads/2024/02/caching_activity2-1024x811.pngThis will cache all ActivityPub requests, regardless of URL. People browsing the same URLs as those used by ActivityPub will be unaffected as their requests won’t have the special HTTP header. I used a short TTL to avoid serving stale data when someone quickly edits a post straight after creating it.
There seems to be a deep vein of optimization here which I’ve only just started to dig into. These changes have made a huge difference already and for now my instance is under very little load so I’ll leave it there for now…
Us sitting here with our fiber internet and recent model phones have it pretty good. But the “i” in iPhone stands for “inequality”. Most people in the world still have pretty bad internet and old/slow phones. For a platform to be widely adopted and to serve the needs of those who often miss out, it needs to be frugal in network and cpu usage.
Lemmy
Kbin
PieFed
Home page
4.5 MB
1.65 MB
700 KB – 930 KB
Viewing a post
360 KB
826 KB (varies)
29 KB
Home pages
Due to Lemmy’s javascript-heavy software architecture, visiting a Lemmy home page involves downloading . And this only gets you 20 posts! Also community thumbnails, even if displayed as a 22px by 22px icon are served directly from their home instances, unresized, which can often be multiple megabytes in size. The home page of lemmy.nz is currently weighing over 9 MB.
Kbin’s home page comes in at a respectable 1.65 MB due to relying less on JavaScript. However it is let down by not using loading=”lazy” on images so they all need to be loaded immediately and by generating post thumbnails that are twice as big as they need to be.
When viewing a post, we can assume various assets (CSS, JS and some images) are cached due to loading the home page first.
The picture looks similar when viewing a post, which is a bit surprising. One of the usual benefits of the JS-heavy SPA architecture used by Lemmy is that once all the ‘app’ is loaded into the browser, subsequent pages only involve a small API call. However, going to a page in Lemmy involves two API calls (one for the page and one for the comments) both of which return quite a bit of data. If you look at the ‘get the comments on this post’ JSON response you can see the developers have fallen into the classic SPA pitfall of “over-fetching“. They’re retrieving a whole haystack from the backend and then using JavaScript to find the needle they want, which involves transferring the haystack over the internet. Ideally the backend would find the needle and just send that to the frontend.
Kbin sends more data than it needs to when viewing a post, again because of not using loading=”lazy” which causes every profile picture of the commenters to be loaded at once. Making this simple fix would bring the weight down, from ~800 KB to around 50 KB.
PieFed only sends 10 KB – 30 KB to show a post, but it varies depending on the number and length of comments. This could be reduced even more by minifying the HTML response but with PieFed under active development I prefer the source to be as readable as possible to aid in debugging.
This is no accident. It is the result of choices made very early on in the development process, well before any code was written. These choices were made based on certain priorities and values which will continue to shape PieFed in the future as it grows. In a world where digital access remains unequal, prioritizing accessible and fast-loading websites isn’t just about technology; it’s a step towards a more inclusive and equitable society.
Could we get something like PieFed's "Add Remote" button?
A super helpful feature that PieFed (a new fediverse thread aggregator like Lemmy & Kbin) has is an "Add Remote" button on its communities page. This button allows you to get a community on another instance to appear on your PieFed instance (and thus get the PieFed instance to start getting posts from that community)....
Rethinking Moderation: A Call for Trust Level Systems in the Fediverse
cross-posted from: discuss.online/post/5772572...