My anti-spam #lemmy automoderator bot #Threativore is now available as a docker container and it is now fully enabled for reporting, removing, and banning. Here's my lemmy announcement: https://lemmy.dbzer0.com/post/15112791
"Over the past week or so there has been a serious spam problem hitting mastodon and rest of the fediverse especially misskey over on the japanese side of things and the story behind it is absolutely wild."
Die ursprünglichen #Forum'e im #Internet gelten schon länger als #veraltet und die scheinbare alternative Lösung #Reddit hat nun #KI integriert und schnuppern die #User aus. Die wahre #Alternative finden wir wieder im Fediverse und sind ua #kbin / #Mbin so wie #Lemmy. Ja das #Fediverse ist viel mehr als nur #Mastodon und Co und kommuniziert nicht nur auf einem Server, sondern in der #Community (ihr kennt es evt schon)
I like being able to browse #Lemmy without a Lemmy account and choose to reply or otherwise participate with my #Mastodon account. The #fediverse is awesome.
Hello again #Fediverse, I may need your #fedihelp. So, here's a list of the Fediverse software I'm about to make temporary accounts for to test all the features and differences:
So, did I miss anything noteworthy? Does anyone have any tips or recommendations before I choose a server for any one of these? I'll probably be going for the most popular server on each for improved federation and maintenance.
Note: I'm using #Sharkey right now and Misskey forks are already overrepresented, so that's why it's not included.
It's been two months since I got my #RaspberryPi and I won't lie, everything is still so exciting. I get so happy when I do stupid little things like upgrade my #Zigbee dongle without everything breaking. Honestly, #SelfHosting is a beautiful world. Though it's all down to how kind and helpful everyone is. I'm super grateful for the tremendous communities behind #HomeAssistant, #Docker, #JellyFin, #Navidrome, #Immich and obviously #Mastodon and #Lemmy.
The #Fediverse spam attack is pretty interesting as a single user instance owner. Unless someone I follow on #Mastodon interacts with a spam post, I don't get to see it. Consequently, I don't think I've seen a single one via Mastodon.
I use Mastodon to follow a bunch of #Lemmy and #Kbin communities though, which function when viewed by Mastodon as a user boosting every post to their community. Therefore I'm seeing a lot of posts that way (before blocking and reporting).
> Private spaces are a fundamental aspect of human communication. They allow discussing sensitive topics without interruption from outsiders. Supporting private communities in Lemmy gives a major new use case for talking among friends or within organizations. This use case is currently not covered by major Fediverse projects.
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.
Two things I need to find: A new Matrix homeserver (currently on matrix.org) and a good Lemmy instance...
I mean, I could selfhost both of them, but I think that would blow up my available resources...
Edit: I don't want ANY finacial offers. I am here to seek advise, to get into a discussion if an instance is actually fitting. If I would want to a "private" instance, I will do it by myself!
The fediverse is working. I am now following (using Mastodon) a "Learning Rust" community on Lemmy [1], who I found through them commenting on my peertube video [2] using Lemmy.
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.
Welche #Reddit Alternativen gibt es denn gerade?
Ich habe #Lemmy und #kbin auf dem Schirm und habe nur ein unbestimmtes Gefühl dass es an Lemmy viel Kritik gab, vielleicht auch an Kbin. Habt ihr mir da mehr Infos?
Hintergrund: Ich würde r/fellnasen auch gerne hier im Fediverse haben. Die Community hier ist wahrscheinlich sehr klein aber einen Versuch wäre es ja wert. #Ratten#haustiere