silverpill

Nice project!
I am very curious about the "emeddable" part. Is it already possible, or only planned?

@i2p

@rbrunner7 Nice explainer, thank you

@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.

@monero

@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.

@fediverse

@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).

@fediverse

@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.

@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 You cite an abandoned project and withdrawn WebMonetization FEP and then say "most efforts have not advanced beyond the planning stages". This statement is misleading because those planning stages are far behind us. Mitra had subscriptions since 2022 and there are other projects that provide monetization options, like PeerTube Lightning plugin and PeerTube Premium Users plugin. FEP-0ea0 and FEP-0837 were published and implemented. Your co-author @quillmatiq should be well aware of these developments because we talked about it

@deadsuperhero @fediverse

Why did't you mention Mitra, the open source and fully decentralized Fediverse service that also offers paid subscriptions, and which has been around for several years?

@kowalabearhugs Currently, some parts of Cuprate are licensed under AGPL-3. This means anyone using this code should keep their derivative works as open source and use the same license. The license protects the project from hostile forks and generally serves as a deterrent against privatization of public goods. Lemmy, Mastodon and many other Fediverse servers use AGPL-3 license and it is totally reasonable choice for Cuprate too.

However, when this CCS proposal was discussed some people started to push aggressively against AGPL (going as far as calling it "legal nightmare") and the developer agreed to change the license and even agreed to re-write AGPL-licensed parts of the application if needed.

As I said, this is a mistake, and makes Monero weaker. I think Cuprate may eventually become a dominant implementation because Rust provides a better security and developer experience, and a big chunk of modern cryptographic libraries is being written in Rust (especially in zero-knowledge cryptography). But now any company can safely use Cuprate as part of their infrastructure because it has business-friendly license, create a closed-source fork and hire developers who were previously working on open-source version.

The change of license is basically a signal that corporate interests are more important than interests of ordinary users. As for examples of where this attitude leads, see any cryptocurrency project where companies or "foundations" pay developers for their work and therefore shape the product. Exceptions are rare, and Monero is one of few that relies on donations and crowdfunding.

@Rucknium

>All code produced for this CCS will be licensed under MIT.

The decision to change license from AGPL to MIT was a mistake. And what is particularly concerning, apparently a lot of people are okay with that.

Such attitude led to demise of many other communities where independence was sacrificed for "adoption" and corporate takeover was perceived as a good thing.