Comment on
Can we make federation less dependent on domain names?
Yes, domain names can be replaced with cryptographic identifiers: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
Comment on
Can we make federation less dependent on domain names?
Yes, domain names can be replaced with cryptographic identifiers: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
Comment on
Inside I2P: The Underground Internet Shielding Users in 2025
I think this article is generated by AI.
Fake CVE numbers. For example, "critical vulnerability (CVE-2021-34527) revealed that Tor Browser leaked real IPs under certain configurations", but if you look it up, it is about Windows Print Spooler.
I2P sites also look fake.
The debian package is called i2pd, not purplei2p
Comment on
ActivityPub vs RSS Atom etc. Why Federate instead of aggrigate?
The main advantage is efficiency. You don't need to poll 1000 servers every minute to get fresh content because everything is delivered straight to your inbox.
the cost of broad redundancy of content and authorship issues
ActivityPub doesn't have redundancy or authorship issues. An object only exists on the originating sever, other servers merely cache it. This is not different from what RSS readers do, for example.
Comment on
Can federating be modified so it's not dependent domain names?
Yes, it is known as "nomadic identity":
https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md
Comment on
[CCS] Alternative Monero node written in Rust has moved to Funding Required
Reply in thread
@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.
Comment on
Why ActivityPub over Nostr? - function only
I don't know much about recent developments, but the early version of the protocol had several major flaws:
- Identity is based on a non-rotatable key, other types of identity are not supported.
- No privacy without encryption.
- Media attachments are not supported, all images are stored on a single server.
- Servers only store data and don't do anything else, so they get abstracted away and everyone uses the same 5 relays (in Fediverse each server has a personality, and that creates a strong incentive to self-host).
There are also many minor things that I dislike, for example the use of numbers instead of human-readable names, unusual cryptography and so on.
Comment on
Can we make federation less dependent on domain names?
Reply in thread
I doubt that it will be implemented in Lemmy, the application architecture needs to be different in order to support cryptographic identities.
But there are other implementations (they are listed near the end of the document).
Comment on
[CCS] Alternative Monero node written in Rust has moved to Funding Required
>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.
Comment on
Would blockchain work better for the Fediverse, instead of Email Style Instances?
Blockchain is a bad choice for a social network, it's expensive and all data is public. But since we're talking about decentralization, let's make a rough comparison.
Bitcoin: 24229 nodes (source: https://bitnodes.io/)
Fediverse: 30005 nodes (source: https://fedilist.com/)
Most of blockchain networks are much smaller than Bitcoin, so they don't even come close to the Fediverse in terms of decentralization.
Comment on
The case for dropping old blocks to keep Monero blockchain size under control and future proof
@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.
Comment on
Implementing Portable User Identities with DIDs
FEP-ef61: Portable Objects describes how to use DIDs with ActivityPub. Here's a slightly less technical introduction: https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md
It's not easy, though. Adding this feature to an existing project will require a lot of work, especially if you don't want to share signing keys with servers. This was discussed in #3100, Lemmy devs are not opposed to FEP-ef61, but they don't plan to work on it.
Also, I don't recommend copying solutions from ATProto, their did:plc and did:web are not really "decentralized".
Comment on
Can we make federation less dependent on domain names?
Reply in thread
That's correct.
did: prefix is used to denote cryptographic identifiers, in theory one could even take a did:plc identifier from Bluesky and then use it as identity for an ActivityPub application:
Comment on
StormyCloud Joins the I2P Family
What This Means for I2P
Starting immediately, I2P will begin accepting donations through cryptocurrency, credit/debit cards, and bank transfers.
I don't understand why I2P needs StormyCloud for this.
And what "I2P" even means here? i2p-java? All I2P implementations?
Comment on
Fediverse enshittification
@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.
Comment on
Founders And CEO Of Cryptocurrency Mixing Service Samurai Wallet Arrested And Charged With Money Laundering
Comment on
How feasible would it be to host Mastodon, Pixelfed, Lemmy, Friendica, or Matrix over Tor/I2P?
Yes, it is feasible and such instances already exist.
For example, you can run a Mitra instance on Tor, I2P or Yggdrasil. It is a lightweight micro-blogging server similar to Mastodon:
https://codeberg.org/silverpill/mitra
Tor / I2P docs:
- https://codeberg.org/silverpill/mitra/src/branch/main/docs/onion.md
- https://codeberg.org/silverpill/mitra/src/branch/main/docs/i2p.md
Comment on
I think the fediverse needs Android like hardware packaging
If the goal is normie-friendly social media with full ownership, it would be better to work on peer-to-peer Fediverse applications.
You can get to a point where you just install an app on your phone and it's yours forever. The foundation for this is already being built: https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md
Self-hosting is nice but it requires an always-online, publicly accessible server and a domain name.
Comment on
Automated changelog generation
@fhoekstra Such tools are worse than useless. Every time I see an automated changelog it's mix of dependabot commits, "fix CI" and other meaningless messages.
Not having a changelog is better, because then you just go straight to a commit history and don't waste your time trying to parse machine-generated slop.
Comment on
Haveno Decentralised Exchange Dispute resolution (Fiat -> XMR)
@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
Comment on
Is the Fediverse KYC'd in the UK with the new law?
Fediverse is very good at censorship resistance, much better than alternatives.
If internet is restricted in your country, use a VPN. If you're an admin, move your server to a different country.
If internet is not restricted, then there is nothing to worry about.