@miscbrains@p@xue@icedquinn@lanodan bro just use a core 2 duo from a thrift store (except goodwill they dump it all in ewaste now). It'll do anything a rpi does and run emulators better.
@Ryle@Fez@yeri yep just directly from the domain. I know a few instances do this.
Also, it uses 10-15% per CPU idling (it's dual CPU) and logging in takes like 15-20 seconds as the CPUs jump to 100%. The hardware is so old it wouldn't scale well for multi user instances, I'm sure a t4 or similar would be better.
@yeri@Ryle@Fez if you use pleroma you can disable caching entirely or just for domains that you don't want cached for obvious reasons like pawoo/baraag.
Meanwhile I'm running this single user instance on an old sparc from 2006
@vidar@catvalente@mastodonmigration@vitruvianmeeple The other thing I'd mention is to change the user agent if you run a Pleroma instance. You can do this easily in settings, and this is because some instances run by sysadmins new to the fedi automatically began to block Pleroma instances in the nginx config because of some harassing instances running it.
My friend running the furry server had this issue as well. His fix was to change the user agent to what he called his fork and suddenly he found himself able to federate with instances that had issues federating with Pleroma.
@vidar@vitruvianmeeple@catvalente@mastodonmigration Yep and just like how there's mastodon forks like glitch-social or hometown, you can easily make a soapbox fork. There's some soapbox fork for example for some guy's instance to allow it to work better with Akkoma (a Pleroma fork) and with modifications for his own site. Rebased is also another Pleroma fork as well.
There's also at least two Misskey forks such as FoundKey and Calckey.
This is the cool part about the AGPL license used on the fedi. Nobody "owns" the software. Even if you hate the developer, you can fork it and fix features the developer removed for example or add in ones he won't add.
While Soapbox did have a stigma due to the people who initially ran instances with it, I know a friend who is running a pro LGBT furry instance with it for example and I know someone else who is trans trying to run an art instance with it. As long as you make sure to specify in your rules exactly what your views are, you'll be fine running one with it blocklist wise.
The other thing with Pleroma and it's forks and other fedi software, is they are a lot less resource heavy than Mastodon is IMO.
Recently there was a semi viral post as well about how a Mastodon instance was having to spend 800 Euro a month to be hosted for a 15k user instance, and then SDF needed excessive high-end hardware to run a 50k user instance.
@sj_zero@crschmidt@alex@jefftk the real thing is to host a pleroma server on a old server or core 2 duo Dell you got for free or $20 at ewaste/the thrift store under your bed, with dynamic dns.
@PaterSnape@crschmidt@jefftk it's defederation as many instances block others and don't even tell you. Click the view external link button if Eugen still let's you (it was in the timestamp).
@alex@crschmidt@jefftk@sj_zero look at meow.social it kept going down and running slow because of mastodon while the only way you can make a single user instance slow is to bloat up the db or be me and run an instance on a old sparc haha
@Kye I don't think they're fake users. They're genuinely all real people who got banned from every other social media site online.
And it comes down to the fact that Pleroma will run on literal garbage hardware from an ewaste center dump. Keep in mind, the developers of Pleroma don't condone behavior even "remotely" tied to it, they just don't make it as obvious. The fact they're on good terms with the Akkoma devs as opposed to Rebased sums it up more than words and PR releases can.
@Kye I feel the other issue with federation as well with if a site were to take off is the amount of times it uses the blocklist.
The other day I found out about an extremely excessive blocklist that literally blanket blocks all known Pleroma instances because some infamous instances run it. It's stuff like that which splits the fediverse into two sides like it already is right now.
@Kye So here's something interesting too, Wordpress not only has ActivityPub plugins, but also I've had a similar idea with art sites being decentralized. Personally I prefer the dA style of community and content discovery over Tumblr's social media feed, especially as you could find related art by different/the same artists easily or "groups" where different artists could post stuff with a common theme.
The nice part about making Tumblr-likes or art sites decentralized is it takes care of the inevitable moderation issues with running an art site, as art sites are very prone to have people argue "stop liking what I don't like".
Of course the problem is, how many people are going to do what is done to Mastodon.Social and just block it for being "too big" like what already happens in some corners?
It was unthinkable in 2020 that Tumblr would have #ActivityPub support on its roadmap. The quick shift in narrative, from a rehash of tech journalists going "it's too haaaard", to serious people giving it a try, then ordinary people.
My view back then was Mastodon probably wouldn't be The Thing. It would get us there, but would struggle to keep up. I'm starting to think Tumblr might be the thing. Automattic hasn't really been an EEE company, so I anticipate them being responsible players here.
I don't think Mastodon is going to go away, but a federated Tumblr answers a lot of the annoyances I've had with it. It supports all the media types I want to post without complaint, and presents them each in a media-appropriate way.
If they can get it open source and decentralized, even better. This seems to be their long-term plan based on things I've seen in posts around the intwewebs. Making it WordPress-based is the goal, maybe as a major extension alongside WooCommerce and co.
@freemo Mostly in smaller instances IMO, as in ones that restrict registration to keep out people who would definitely look to fighting half the internet and fediverse.
The problem with a blanket Pleroma blocklist because "bad people" use it, is there are a lot of left-wing instances and hobby based instances that run it. Sure many of them moved to Akkoma, but a lot run vanilla Pleroma and the thing is, the developers of Pleroma are definitely not Nazis (see the Alex Gleason feud). I know for a fact most of the devs are LGBT and at least one former Pleroma dev was transgender. The same goes with soapbox, I know a trans person runs ap.maladaptive.art and it's blocked for being problematic just because of running Soapbox. The admin doesn't agree with Alexes views, but likes the UI of Soapbox and feels that it overcomes a barrier to fedi adoption.
Put it this way, this instance of mine that I don't use that often on a SPARC box (for a month long challenge of using old hardware) is now on that list because they just scraped all Pleroma instances.
@freemo It's a fork of a tool that was originally written by worse people than KF (a nonce instance which was whining about being blocked). I have no idea if Mint actually uses the farms themselves other than the Git and possibly the fedi instance.
But I have a strong feeling they're using that to discredit anyone complaining about being blocked. These kinds of people just created another blocklist to block all the Pleroma and Soapbox instances, and I mean a 1200+ domain list. https://ligma.pro/@r000t/109396033621130514
They're the same types on Twitter who'd run "blockchain" scripts on peoples accounts.