Mastodon 4 adds a new endpoint, /api/v1/instance/domain_blocks
This endpoint contains your instance's block list in an easily machine-readable format. As far as I know, the only tool that currently uses this endpoint is the kiwifarms one.
The endpoint does not require any form of authentication, so it's very easy to scrape. I recommend editing your web server configuration to prevent access to the endpoint until there's something legitimate that uses it.
I believe it has the same Heterogeneous Multiprocessing design from cell phones, a combination of low-power and high-power cores, which helps a lot in terms of power efficiency especially when the software can take advantage of it.
Anyways, it's happening. The meek little SBC has grown up, it's a Real Computer now. Yes, things like graphics drivers and virtualization support are surely lacking. And it's not $35 any more. But as an affordable server platform for linux-based apps and containers, these little boards just keep getting better and better.
a user on the radxa discord quoted 18 Watts at the wall under 100% CPU stress. 4-5 watts at idle was a little bit of an underwhelming result, but it may be tune-able to get that figure lower.
RK3588 CPU has been picked up by Radxa, Orange Pi, and Firefly, and it pushes **serious** numbers on the CPU benchmarks, almost 4x better than the Raspberry Pi 4. Comes in 8GB and 16GB RAM flavors.
That would be a bold move on their part -- some fediverse admins will ignore it, some will fediblock right away. The more blocked tumblr gets, the less metadata they can collect from this fedi excursion.
Yes, injecting ads is standard practice for social media -- but injecting ads that masquerade as real posts has traditionally been done via "hiring an influencer" rather than by simply inserting rows into a database somewhere.
I think centralized social media is a very carefully orchestrated frog boiling operation, and tumblr probably can't afford to do something this drastic.
ESRB rating: Blood and Violence (of software)
Wow this is an incredibly long and detailed read, great for desktop / integrated software developers like me to understand how these kind of attacks work and how to prevent them
Sure, I can purchase a new computer with more RAM, but I just don't like that solution. I'd rather invest in GoToSocial development. Computers have been "fast enough" for 10 years now, I dont think we should have to keep buying new ones all the time
because if I did, my RAM alert would start going off. Per what I've heard from my friend who runs an instance with about 10 users on it, it needs at least 512MB. His was getting oom killed at that level. That's more RAM than the top 3 apps I have running my server right now combined
I'll be the first one to complain about how inefficient and resource-hungry mastodon is, I dont give a shit that its "uncool" to mention.
I just want to be able to run mastodon on my server. But I can't
@gabek on windows 11 no less https://video.strongthany.cc/watch?v=9kaIXkImCAM
@maloki There is also a bot that measures total active fediverse accounts: https://github.com/gallizoltan/usercount
@chaosmonkey@masto.ai @huan yes this post was a part of a series I made where I talk about how gotosocial is being sponsored by NLNet. The good news is that its not a mastodon rewrite, its just a different fediverse server implementation. They are all compatible & part of the same network
The hardware requirement to federate George Takei's toots right now is surely massive -- think ThreadRipper.
GoToSocial will probably be able to achieve a similar result on a mere Raspberry Pi 4.
It's going to be a long time before GoToSocial is usable enough that it can see real-world load. But based on what I have heard about Mastodon outbox federation performance, I'm very confident that GoToSocial should smash Mastodon in terms of its ability to keep up with accounts that have thousands of followers from thousands of servers and post frequently.
There's a lot that I don't know.
GoToSocial has had some performance issues in the wild already, mostly related to missing indexes on database / non-optimize queries. That's typical for any new application and usually very easy to solve in a relational database.
So I see two ways forward for the fediverse, either:
A. Mastodon has to be refactored / rewritten to use Ruby Fibers, the non-blocking concurrency feature for Ruby
OR
B. We have to switch to a different Fediverse software that is based on a more modern software development framework.
Personally I think B might be the best option, and my money is on GoToSocial!!
I am a web technologist who is interested in supporting and building enjoyable ways for individuals, organizations, and communities to set up and maintain their own server infrastructure, including the hardware part.
I am currently working full time as an SRE 😫, but I am also heavily involved with Cyberia Computer Club and Layer Zero