@waifu Did Zuck persuade him to make a threads.com account? See, once threads start properly federating, it is expected that threads users will be able to migrate to other instances
So I don't see any fundamental difference between FEP-400e and FEP-1b12. The authentication issue, however, is quite important, because without FEP-8b32 the group either doesn't scale or can impersonate anyone.
@takeshikovacs No, mitra.social is specially for me. You can generate signature in Monero wallet, in Monero GUI this feature is hidden in Advanced features:
@takeshikovacs Will send the invite code in a couple of minutes. If you want you can log in without password using your Ethereum wallet (Metamask should still work).
@takeshikovacs No idea. All accounts I've been following there stopped posting shortly after the migration, I guess everyone just went back to Twitter.
@tadano@Tadano Old notifs should display properly too, but I am not surprised they are still blank, because the API is not 100% Pleroma compatible yet. I'll finish this job in the next release.
@Tadano@tadano In v2.20.0 I added lists of emoji reactions to post, in Pleroma format. If Husky can display emoji reactions, maybe it will do that with Mitra now.
Also changed the notification format, although it is still not fully compatible with Pleroma. Give it a try too.
Do you know any other clients that support emoji reactions?
@MoneroIsTheFuture@erc ErC is right about operators being able to steal funds, but that doesn't mean they will actually do it. Operators risk their reputations, and I think unlike DNMs they can't make a lot of money from an exit scam. So this approach might actually work reasonably well.
>illegal
Even if it is not illegal today, it will be in a couple of years. Why even care, lol
I think you're right, other solutions require dev work, but centralization caused by default instances is usually irreversible, they tend to grow bigger over time (and more generally in federations, big instances are getting bigger - email, matrix and mastodon are good examples)
An ideal protocol should work like RSS. There, the cost of participation for content consumers is almost zero. One just needs a client. The cost of participation for content producers is low (one can use any static site generator), and they enjoy all the benefits of decentralized infrastructure.
How we can get to that point with ActivityPub? Some ideas:
- More efficient servers. Instance setup should be as simple as creating a static website with an RSS feed - Read-only accounts. These users can participate as content consumers, but the cost for instance operators is much lower because they don't require moderation. - Universal UIs. People shouldn't be forced to create accounts on different federated services. - Pulling from outbox. Instance blocks punish content consumers for no reason, and this can be fixed by switching to pull model in some situations.
>implementation of an upload system for attachments using IPFS.
Nowadays I think #IPFS is not the right choice (see FEP-ef61 for a better solution), but nevertheless, it is good that this topic is getting more attention
@laxla Do you really need it? JSON-LD is not required for federation, and may even be harmful because some fediverse servers don't produce valid JSON-LD (at least that's what I heard - I don't do JSON-LD processing myself)
Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. Working on Fediverse standards: https://codeberg.org/silverpill/feps