This is what ActivityPub client-to-server API was designed for.
Most servers don’t implement it, but some do:
https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130
Clients are even harder to find, and none of them are good, AFAIK
Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. Working on Fediverse standards: https://codeberg.org/silverpill/feps
This is what ActivityPub client-to-server API was designed for.
Most servers don’t implement it, but some do:
https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130
Clients are even harder to find, and none of them are good, AFAIK
FChannel is a federated anonymous imageboard powered by ActivityPub:
@g2devi @XMRbutterfly @monero PoW doesn’t guarantee that wealth is deserved, because computing power can be bought too. It’s a bit harder to buy than tokens, but that doesn’t change the big picture.
Monero should stick to PoW, though, because it works. It didn’t work for Firo, apparently, so they had to change it, but I am not aware of any 51% attacks on Monero.
Looks reasonable overall, but I don’t understand some of your assessments.
>Easy (Leverage email hosting services)
What are those email hosting services? If hosting and maintenance are delegated to 3rd parties, that doesn’t count towards decentralization.
>Top Provider User Share: Reddit ≈ 48.4%
Why this is not 100%?
>Very Easy: One-command Docker,
I think the easiest option is distro’s default package manager – docker is additional layer of complexity. Also some services are nearly impossible to self-host without docker, and points should be subtracted if that is the case.
@RealPappenheimer This issue was discussed at length in monero-community matrix room when proposal was submitted. I guess it’s too late to reverse the decision. Even the person who wrote AGPL-licensed modules appears to support the change, although I don’t know why they suddenly changed their mind.
@Ferminho @maegul This proposal describes a very simple marketplace, and some things were intentionally left out. However, it is based on Valueflows system which can be used to describe many different economic processes, including planning, production and transportation:
https://www.valueflo.ws/introduction/core/
So developers may use object types and properties defined there if they want to build something more complicated. And social interactions can be represented as standard ActivityPub activities. I think Valueflows and ActivityPub nicely complement each other.
@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.
>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.
@Emperor @MostlyLazy If the server doesn’t process payments it should not cause admin a headache in most (?) jurisdictions.
Alternatively, one could focus on grey markets.
>Bitejo
By the way, Bitejo was planning to add federation, although now the future of the project is a bit uncertain. It might be added to Bitejo fork, as I suggested in this CCS: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/395#note_21836
There was a proposal to set up Mobilizon instance: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/70#note_21324 (federated & self-hosted platform for events)
@alvvayson @trymeout I think the easiest way to make Monero payments possible in Lemmy is to convince devs to support profile fields: https://github.com/LemmyNet/lemmy/issues/246.
Then you can add your address to your profile and it will be visible to other Fediverse servers (profile fields are widely supported). People often use labels like $XMR and $BTC, that makes the address field machine-readable, so clients may display a donation button somewhere.
>ANON + NERO leverages the power of the Uniform Resources (UR) standard to transmit Monero’s relatively large payloads via animated QR codes.
Interesting. Are you referring to this? https://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/ur-1-overview.md
Boards are actors, and every message on the board is attributed to the board actor.
I think it would be easier to make it interoperate with microblogs than with forum-like software.
@fediverse