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

@nihilist @monero Consider the following situations:

- Bob and Arbitrator are colluding against Alice
- Bob and Arbitrator are the same person

I think this system needs a higher authority to function properly. And there's a simple non-technical solution to this problem. If you don't agree with Arbitrator's ruling, you make the case public and provide proofs. As a result, Arbitrator's reputation is destroyed.

Someone can even create a rating service similar to @kycnotme that will list arbitrators with good reputation

@OrangeFren @monero Why make a non-federated forum? You can run a Lemmy or a Discourse instance, and let people from monero.town and beyond participate in discussions. Otherwise there won't be much activity

@gunnm @monero

>There is no social media using tipping as piconeros

There is, I'm using it right now. Try to click on the "fediverse" icon near my comment, and on my site you'll see a donation button.

>looking for opinions and discussion of this could be done in Monero.town

The easiest way is to convince Lemmy devs to implement profile fields: https://github.com/LemmyNet/lemmy-ui/issues/2411

After that you can add a machine readable XMR address to your profile

@gunnm @monero Yet another attack on open source software developers and a wake up call for everyone, especially bitcoiners. If they will fail to save these guys, Bitcoin will be officially over.

@DisgracedDoctor @monero @monerobull I think this is because monero today is a boring tool that just works. The community calmed down and many activists/shills moved to greener pastures. This is probably a good thing

If you want more activity in fediverse, you can try to get micro-blogging sector going. There are many people who are interested in monero but no organization. I've seen a couple of accounts run by projects which mostly cross-post from twitter and do not engage with audience. No follow lists. We had a xmrposter Pleroma instance, but it was shut down.

@tusker @monero Chain growth is a real problem that is often dismissed because storage prices are falling. This makes sense when you're small and there is not much activity, but that could change in the future.

However, I don't think you can simply drop old blocks without burning someone's savings? One probably should look into what Ethereum people are doing with their state expiry proposals.

@tusker There seems to be an overlap in functionality between Kuno and my project Mitra, which also provides a way to support individuals with XMR.

Have you looked at it? The software is well-maintained, and has federation capabilities (I'm posting to monero.town from my own server right now). If any feature is missing (e.g. the ability to set goals), I could add it.

@Wave

>On the other hand this alone may push the hardfork to Seraphis and Jamtis a full year further out

Move slow and don't break things. I think an additional year of development is not a problem for end users

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

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