Skip Navigation

silverpill

@ silverpill @mitra.social

Posts
1
Comments
140
Joined
4 yr. ago

  • Minutes from 4 December 2025 WG Meeting

    Jump

  • I think this is too complicated. Also, Move is meant to be used when origin and target are collections, but in the FEP they are both actors.

    Why not Update?

    Or, if you want to be explicit, consider introducing a new activity? For example, UpdateAudience:

     
        
{
    "id": "https://example.social/update-audience"
    "type": "UpdateAudience",
    "actor": "https://example.social/uid/1",
    "to": ["https://www.w3.org/ns/activitystreams#Public"],
    "cc": [
        "https://example.social/audience/1/followers",
        "https://example.social/audience/2/followers",
    ],
    "object": "https://example.social/context/1",
    "prevAudience": ["https://example.social/audience/1"],
    "nextAudience": ["https://example.social/audience/2"],
}

  • Emoji reactions in the PieFed API

    Jump

  • @rimu I sent two reactions, one unicode and one with a custom emoji. The unicode one worked as expected, but the second one with :catjam: is not rendered properly. Also it seems to have replaced the unicode reaction.

  • Would blockchain work better for the Fediverse, instead of Email Style Instances?

    Jump

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

  • How feasible would it be to host Mastodon, Pixelfed, Lemmy, Friendica, or Matrix over Tor/I2P?

    Jump

  • Why ActivityPub over Nostr? - function only

    Jump

  • Why ActivityPub over Nostr? - function only

    Jump

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

  • Fediverse Enhancement Proposals

    Jump

  • Fediverse Enhancement Proposals

    Jump

  • Currently it's hard to read, there is no single document. No single source of truth.

    We can make it happen.

    I am currently working on this: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md. It's a guide for developers, but in the future it may be used as a base for a more formal specification.

  • Minutes from 4 December 2025 WG Meeting

    Jump

  • Collections are dynamic objects because they can be paginated and filtered. It's not possible to sign a dynamic object, because some of its properties are constantly changing (items, totalItems and others). This means collections need to be always server-managed. Therefore, clients shouldn't be allowed to directly create, update or delete them.

    I think the proposed Move activity is an obfuscated Update because it changes the collection directly.

  • Minutes from 4 December 2025 WG Meeting

    Jump

  • the assumption is already there

    Where, in Lemmy? Even if some implementations don't support cross-posting I don't see a reason to block it at the protocol level.

    And Update is simpler, that's one activity instead of two (Move and Remove).

  • Minutes from 4 December 2025 WG Meeting

    Jump

  • @julian

    FEP-f15d: Context Relocation and Removal

    I have two objections to this proposal. We discussed them before in Moving topics/contexts between communities:

    1. It assumes that a context always belongs to one group.

    As I suggested in the aforementioned thread, an Update activity is a better solution because it works when relationship between a context and a group is many-to-many. It is also semantically cleaner: "update collection audience" instead of "move collection from actor 1 to actor 2" and "remove collection from actor" (at least if ActivityStreams terminology is used).

    1. Treating collections (dynamic views) as static objects that can be moved, deleted etc is not compatible with client-side signing.

    One possible solution is to separate context (an object) and its contents (a collection).

    @jesseplusplus @rimu @nutomic @melroy @BentiGorlich

  • Monero community

    Jump

  • Community mention spam from Microblogs

    Jump

  • Sucks, right, because on the theadiverse, you're not actually able to do that so easily.

    Sounds like an unnecessary limitation of threadiverse software. Why limit a post to only one community? That doesn't make any sense.

    The person who made the post with multiple mentions clearly did it intentionally, and I would do the same because for every topic I am interested in there are 4-5 groups on different servers.

    Every mentioned person gets addressed

    In most cases, this is what a user wants. Some platforms support silent mentions, though (Friendica, if I remember correctly).

    hashtag / community tag soup

    I think this should be viewed as a moderation problem, not a protocol problem. If you don't want to see mention soup, just limit the number of mentions per post on your instance.

  • GitHub - MaddyUnderStars/shoot: ActivityPub federated instant messaging server

    Jump

  • It federates, I was told that it uses FEP-1b12. However, I haven't yet gotten past the actor discovery because there is always some bug that prevents further interactions 😅

  • I think the fediverse needs Android like hardware packaging

    Jump

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

  • monero.town being phased out, /c/monero thrives on lemmy.cafe now!

    Jump

  • Hi @Illecors, do you know why subscribing to lemmy.cafe communities may not work?I tried to subscribe to this community, and several others, but the server never accepts my requests. This doesn't happen with other Lemmy servers.

    As far as I can tell, my server is not blocked. Upvotes and (hopefully) comments do go through.

  • Automated changelog generation

    Jump

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

  • Minutes from 6 November 2025 WG Meeting

    Jump

  • [Announcement] Migrating away from lemmy.

    Jump

  • Does it need to look like Reddit?I am working on an ActivityPub client that doesn't depend on a single server. Groups are planned, but the interface will be different from Reddit/Lemmy.

  • [Announcement] Migrating away from lemmy.

    Jump
  • Article Interop WG @lemmy.ml
    silverpill @mitra.social

    Article Interop WG: How to represent titles?