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:
The latest build (mobile) works fine, except I get alerts for unimplemented endpoints. The stable release worked for me as well on desktop last time I tried it @gombang
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.
@danieldekay no the same - I have hundreds of different followers on each network, although all could follow on either one. I post manually to Hubzilla, but my Friendica site auto-posts from my blog RSS feed.
Both networks are profile -only posts, so no separation into topics like Google+ had. I loved posting into topics as that gave some focus for followers. Actually think Reddit has that inside channels, but I left Reddit for Lemmy.
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!
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.
#Question about #Friendica
Once Friendica is installed, it fails to display messages from remote users.
I have made 2 changes, but they have had no effect: