@julian Take a look at this document: https://codeberg.org/silverpill/feps/src/branch/main/f228/fep-f228.md
I wrote it for Conversation Container implementers, but maybe others will find it useful too.
silverpill
@rafael_xmr @monero This app connects to 30 clearnet domains and all images are stored on nostr.build.
@lionroe Sounds complicated, and the biggest flaw of OpenBazaar still remains: the lack of web client. We discuss this article because it is available on the web. Lemmy and other Fediverse apps are successful because they have web clients.
Why not start with existing federated software like flohmarkt? Make it federate over Tor (maybe it already does). That would solve the hardest problem, discovery. Other features can be added later.
Vendors will host everything themselves, so there is no need for any incentive model.
@Teknevra It can be done with FEP-ae97:
https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md
Which enables shared identity and seamless migration as you describe, but I don't think traditional web login needs to be abandoned. Fediverse will support both types of identities.
@Fitik @Teknevra Tipping will also be supported in the future (in addition to subscriptions).
And people on other platforms may put addresses in profile fields (Lemmy doesn't have them yet?). Mitra displays a donation icon when address is detected (the name of the field should be like $BTC).
@5dh @fediverse Financial incentive is not the only possible cause. If project leaders stop listening to their users for some other reason, you'll get the same result.
And there is another, more subtle problem: protocol bloat. Fediverse services are getting more and more complicated, and the cost of creating a new platform is constantly increasing. If this problem is not addressed, at some point Fediverse will start looking like a web browser market, where new players can't compete due to an immense implementation complexity.
@sun @fediverse @deadsuperhero Not yet. But Mitra can display a "Subscribe" button and subscription terms for sub.club accounts if they start publishing a Proposal
object as described in FEP-0837. Alternatively, I can add support for their custom subscription
property
@deadsuperhero @fediverse @quillmatiq Protocols described in these FEPs are currency-agnostic and developers can build actual platforms and solutions on them (as I did). This is the only ongoing effort to bring a payment layer to the Fediverse - there are no alternative proposals. FEP-8c3f was withdrawn in favor of FEP-0ea0.
Okay, you didn't know about it. But now you do and it would be nice to include at least some of that information in the article.
@deadsuperhero @fediverse FEP-ef61 is what Mike was implementing and rolled out in production this summer. It's not like we didn't advertise that. All work on this FEP (and ones that precede it) was done in public channels, it's really hard to miss if you're interested in nomadic identity.
Give @weekinfediverse a follow. It provides a concise summary of what is happening in Fediverse
https://wedistribute.org/2024/03/activitypub-nomadic-identity/
In another article @deadsuperhero talked about nomadic identity and Mike Macgirvin's efforts to implement it in ActivityPub, but similarly failed to mention another project that implements it (Mitra) and the person who wrote the spec (me).
At least my work was mentioned in a footnote. In the current article it is completely ignored.
@julian FEP-1b12 only works with activities,
but Lemmy also announces Page objects for (micro)blogs.
https://socialhub.activitypub.rocks/ap/object/443fb143373ebc5a4df190cddcd2da1f