For what seems like ages .... (about 6-8 weeks), I did not want to touch anything on my yunohost mastodon app, because the webinterface was broken, but the barebones settings were accessible. And I could still toot via my mobile app.
Finally, the interface is up and running again, but I fear a mastodon-move will be in the works, as I find the yunohost masto version very dodgy and not well maintained.
Any tips on how I can install my own server and keep all data of this version in the new one?
@leonieke
I don't know what well-developed means to you, but Hubzilla/Streams are older, more versatile, and more conservatively developed than the Mastodon juggernaut. They have their drawbacks, but are not resource hogs.
A more Mastodonistic but simpler-admin alternative might be #Pleroma ... @meneer
Wait, #Pleroma has a thing where instance admins can manage emoji collections with a package manager? Does it just use the URL once and forget it or does it set up a chron job to check for updates? Is there a way to set up an auto-updater for #Sharkey? I don't want to bother @Kitty every time @volpeon adds new ones.
I've just done a bit more testing, since my friend emma in this Raddle thread was able to confirm in her own #Postmill instance (I've tested against #Raddle too because why not) that it's a caching reverse proxy causing images to stay longer on the server. I'm able to confirm that using a query string bypasses the proxy's cache and results in the expected 404. Hooray, and I couldn't expect any better from Raddle! :ai_yay: They always take #privacy seriously. :alice_wine:
I've used this method against #Mastodon, #Pleroma, and #Misskey. The first two still returns the image I've uploaded even though I've deleted my account AND used a query string to bypass proxy cache (yikes). Misskey forcibly rewrites the URL to strip out the query string, therefore I can't conclude for 100% sure that it's a proxy's fault. But I'm still pretty confident it is the reverse proxy's doing in the case of Misskey due to the observation I mentioned earlier where the generated file URLs that never got accessed don't get cached.
Alright I'm done with this shit, #fediverse devs, do whatever with this info with mind :seija_coffee:
> Fediverse spam problem
> Eugen flaunts his superiority as mastodon.social is clearly the best and we're all just peons
> No mention of planned moderation features to let operators help themselves
> Only advice given is to disable disposable emails or switch to approved registrations, neither of which helps the rest of the fediverse, only the zombie instances used to facilitate the spam.
@graf@eriner Graf's hitting the nail on the head, folks! It's SAD, really sad, that Matt didn't do his homework. Over in #pleroma#darkfedi, spam's as invisible as Sleepy Joe's energy! ZERO, nada! That's what SMART planning looks like. Not like these other guys, stumbling around in the dark, clueless. We need more brains, less complaining. Let's get with the program and beat this spam the RIGHT way. MAGNIFICENT strategy beats sloppy work any day! #Winning
For example, on #Pleroma admins can set posts from the given instances to be visible by followers only. This way you can restrict instances without fully defederating them. I don't know if #Mastodon has it.
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.
Other recent changes include updated Spanish translations, fixing the font shown when viewing a post's history, workarounds for buggy behaviour from #Mastodon, #Pleroma, and #Friendica servers, and more.
I'm still in the process of putting things together - namely: implementing the Oliphant T0 blocklist, writing out our policies and Terms of Service, and tweaking everything to our liking.
We decided to go with #Akkoma for We Distribute Social. It's powerful, reliable, and carries on some great ideas from #Pleroma while adding in great ideas like Bubbles.
Anyway, please keep an ear out, as things will be developing fairly quickly!