Skip Navigation

Posts
1
Comments
140
Joined
4 yr. ago

  • 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?

  • There is a self-hosted subscription service that supports Monero: https://codeberg.org/silverpill/mitra

    Automatic recurrent Monero payments are not really possible, but Mitra generates a notification when subscription expires so you know when to renew.

    Also, it's federated -- I am publishing this comment from my own node.

  • @julian Fedilinks website lists 3 MastoAPI clients, but the list is incomplete. I saw Fedilinks being mentioned in changelogs of other clients too.

    There was also an Akkoma PR, it was closed by the author: https://akkoma.dev/AkkomaGang/akkoma/pulls/589. I don't quite understand the reasoning, perhaps @smitten could clarify.

  • ActivityPub messages are not encrypted, but they could be signed. Signing doesn't prevent edits and deletes.

    Yes, if someone has unsubscribed they are unlikely to be notified about the deletion.

  • As I understand it ActivityPub uses a combination of push notifications at time of publishing and pull notifications at time of subscription/query for objects?

    It's a mix of pushing and pulling. When something happens, the server pushes a notification ("activity") to other servers. But recipients often need to pull additional data, such as user profiles or related posts.

    Duration of caching is set by the instance admin I take it?

    Yes, and it also depends on the software. Some applications may keep cached objects forever and only prune cached media (because objects don't require much space).

    Regarding Authorship, if there wasn't an issue then ATProtocol devs wouldn't have made it the cornerstone feature of their network

    Moving in ActivityPub world is difficult because authorship is tied to a specific server. We can solve this problem by using cryptographic identities and signing everything, like ATProto and Nostr do.

    I'd like to know how delete requests propagate, when the "Object" is deleted does a request to clear cache go out to all federating instances?

    Deletes and edits are usually sent to followers of a user or a community. Delivering them to all known instances is not practical.

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

  • This is a sensible proposal. Leverage existing trust to solve the problem.

    I think a more advanced version of this that doesn't depend on DNS might even be a good long-term solution. A Proof-of-Authority consensus, perhaps? Qubic have demonstrated that algorithms can easily be gamed, but humans are more complicated.

  • I think Solid had some interesting ideas, but was ruined by Linked Data.ActivityPub has a chance of evolving into something like Solid, but better.

    Actually, I am already using a single account for interacting with most Fediverse apps. Aren't you on Mbin? I thought it also can interact with blogs, forums and everything in between

  • I would like to use a single account for everything, rather than separate accounts for different kinds of content. A server that works like super-app.

  • Recent context collection news, in case you've missed:

    Mastodon: PR open Lemmy: PR merged

  • 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".

  • Deleted

    Permanently Deleted

    Jump
  • Mastodon enforces character limit for its own posts, but not for posts coming through federation. Most Fediverse platforms work in the same way, so differing character limits is not a problem.

    I don't know about Bluesky, it may truncate long posts because it uses a different protocol.

  • Deleted

    Permanently Deleted

    Jump
  • ActivityPub is supposed to be a solution to this problem.

    As far as I know, Mastodon and Pixelfed are already interoperable, and shouldn't need a cross poster. Bluesky users can be reached through BridgyFed. Lemmy is only partially interoperable with Mastodon, but this is a result of developers' choices and not a limitation of the protocol. I can post to all four services, for example.

  • 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

  • @julian Was there a meeting? Could you provide a short summary?

    I am particularly interested in cross posting.