In a similar fashion, it would be great to find a way to migrate your post history, not just your followers, between one service and another. So far it’s possible to request a backup, but only a few services allow importing said backup, let alone import a backup from a different provider (so far only Firefish, Pixelfed and its derivatives allow for the latter).
If you want to read the gritty-nitty of how exactly was the Widevine blob patched and worked around specifically to not violate the DMCA, here’s the specific article
I’d love to move to mainstream Misskey, but there’s a core reason why I’m using Firefish at the moment, namely the ability to actually import my old posts from Mastodon. To my knowledge, pretty much nothing supports importing posts in the Fediverse, except for Firefish and forks, Friendica and forks (to an extent), and PixelFed.
A potential workaround: quote-repost your blog post via Akkoma or Firefish, mention the community you want to post the blog post on, and add the title on the beginning
My only complaint is that each individual blog administrator must learn about this addon and enable it. So subscribing to a given blog in the hopes of having AP support is literally trial and error.
I wonder if they’re moving to KBin or even Mastodon instead, and that explains the dip in Lemmy specifically.
I’d be unsurprised if they’re using ForgeFed proper
As soon as Forgejo and Gitlab are able to share issue tracking between them, Github is so doomed in the open-source community
Today I learned that one of the biggest Spanish instances, Mujico, apparently doesn’t federate with anyone else. Ah well
Alright, but should the banned user be able to see posts from the banned instance if they’re cross-posted to a non-banned instance?
There is one major problem with the implementation that I hope you can understand with an example. Suppose there are three forums - motorsports@example1.com, motorsports@example2.net and motorsports@example3.org, which eventually start mirroring each other by default. Let’s also suppose that a user is, for whatever reason, banned from example1.com but not from example2.net or example3.org. Should the user try to subscribe to motorsports@example2.net, must the latter honor the ban list from example1.com and ban the user as well, or should each instance have its own ban list, knowing well that users can evade bans by subscribing to another of the mirrored communities?
I tried using Friendica as my main Fediverse hub. Unfortunately it still has big issues regarding the handling of large lists of users (I, for one, follow around 1000 Mastodon users plus about 300 Lemmy/Kbin communities), so with much pain in my heart I had to return to dual-wielding Akkoma + Lemmy.
Probably merged with all the other ActivityPub frontends into a single, hyper-customizable mega-app.
It depends on how privacy-conscious does Automattic (the current owners of Tumblr and Wordpress) decide to make Tumblr. If they actually make good in their offer to open-source Tumblr though, you can expect people to federate with no issues with both Tumblr and other “Tumblr nodes” as well.
I’m currently using Akkoma, but I intend to switch to Calckey as soon as it has a stable way of transferring my posts.
If that means a way to view Instagram accounts without actually having an Instagram myself: I might give it a spin from my instance. I totally understand the admins burning the bridge before it’s even built, though.
Not gonna lie, the article is right in the sense that the Fediverse is still rough on the edges. Hopefully the fact that everyone and their parents had to move out of most social media will make organizations reconsider investing government money into making them better.
Lists are your friend! Not sure if Mastodon can do it, but on Pleroma/Akkoma you can add users to a list without adding them to your main followed list.
That’s because you haven’t found The Good Ones ™ such as TILVids
Not sure whether this implementation will be lighter on resources than what Lemmy currently uses. Given the overhead of the JVM though, it’s unlikely it will be supported by, say, a single Raspberry Pi