Skip to content

Blogtastisch: 2. Blogs und das Fediverse

notizBlog
17 8 182

Diese Artikel könnten Dich auch interessieren.

  • 0 Stimmen
    11 Beiträge
    6 Aufrufe
    julian@community.nodebb.orgJ
    tchambers@indieweb.social this, in a nutshell. The fediverse vid AP can support both A and B, and we can wax poetic about how one is superior to the other but both are legitimate UX decisions by their respective software stacks. I prefer B myself, of course. cc tommi@pan.rent j12t@j12t.social
  • 0 Stimmen
    26 Beiträge
    32 Aufrufe
    julian@community.nodebb.orgJ
    trwnh@mastodon.social but as:Public is not a dereferenceable URL. Needs to be special cased anyway. End of the day nothing changes, it needs special handling for all the cases anyway. cc silverpill@mitra.social
  • 0 Stimmen
    6 Beiträge
    7 Aufrufe
    julian@community.nodebb.orgJ
    Very interesting article! I have immense respect for jerry@infosec.exchange, he was one of the first people I found on the fediverse, and it's no wonder why, he's revered quite highly by others as being a generous and kind admin. I do want to point out one thing, and that is that Mastodon has some design decisions that make it rather resource and storage intensive. There are oodles of lighter software out there, some with even more features than Mastodon, and some with less. For example, snac.bsd.cafe (https://snac.bsd.cafe/) runs on Snac, which is fast as hell. I am going to guess that a not insignificant portion of Jerry's bill is caching assets. Mastodon likes to save everything it encounters, videos, images, avatars, everything... forever (though I imagine this is customisable). Most likely the assets are viewed a handful of times in one day and never seen again... but you'll pay to store it forever!
  • Pixelfed Uptick in Monthly Active Users

    Uncategorized fediverse
    20
    1
    0 Stimmen
    20 Beiträge
    83 Aufrufe
    julian@community.nodebb.orgJ
    I would say that Pixelfed is closer to the microblog space than it is the threaded discussion space. It's essentially microblogging except with an image media focus (or video, in the case of Loops.) To each their own, some people communicate better using pictures, some better over short text, some better over long-form text. There's a space for them all
  • Fun with Federation: Lemmy edition

    ActivityPub nodebb lemmy activitypub
    5
    0 Stimmen
    5 Beiträge
    27 Aufrufe
    julian@community.nodebb.orgJ
    nutomic@lemmy.ml let me know if I got any of the details wrong. Much thanks to your team for the assist in debugging!
  • Unicode in handles

    ActivityPub unicode activitypub
    15
    0 Stimmen
    15 Beiträge
    122 Aufrufe
    julian@community.nodebb.orgJ
    לאצי the usernames work fine locally (that is, on the site itself). It's when interoperating with other sites not running NodeBB where there are issues, it seems
  • 0 Stimmen
    9 Beiträge
    64 Aufrufe
    julian@community.nodebb.orgJ
    I suppose you're right in a way. The context owner is not supposed to be set by someone other than the context owner. It's a fallback mechanism intended for better compatibility with Mastodon. When a group is addressed and it is one of the local NodeBB categories, it will assume control If it is another group that it knows about but isn't same origin to the author, then no category is assumed.
  • 0 Stimmen
    17 Beiträge
    149 Aufrufe
    julian@community.nodebb.orgJ
    Hey rimu@piefed.social thanks for responding (and sorry for the late reply!) I am not married to the Announce([Article|Note|Page]) approach, so I am definitely open to Create([Article|Note|Page]) with a back-reference. I think I went the former direction because there is a known fallback mechanism — the Announce is treated as a share/boost/repost as normal. However, sending the Create also is fine I think. However, do we need a backreference? In my limited research, it seems that Piefed, et al. picks the first Group actor and associates the post with that community. If I sent over a Create(Article) with two Group actors addressed, could Piefed associate the post with the first, and initiate a cross-post with the remaining Group actors? Secondly, is how to handle sync. 1b12 relies on communities having reciprocal followers in order for two-way synchronization to be established. On my end since I know it is cross-posted I will now send 1b12 activities to cross-posted communities, but can Piefed, et al. send 1b12 activities back as well, in the absence of followers? cc andrew_s@piefed.social nutomic@lemmy.ml melroy@kbin.melroy.org bentigorlich@gehirneimer.de