Salta al contenuto

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Looking for federated NodeBB instances

Fediverso
2 2 2

Gli ultimi otto messaggi ricevuti dalla Federazione
  • There are comparatively few instances that federate, since we are new to the activitypub game.

    I made the decision that if you upgrade to v4, AP is turned off. Install a new instance of NodeBB, and ActivityPub is enabled out of the box.

    Side effect of that would be all instances running prior to v4 won't be federating, but at least there will be no surprises!

    Here's a list, but it's not listed by topic or genre.

    https://nodebb.fediverse.observer/list

    per saperne di più

  • I recently discovered NodeBB can federate and started hunting for interesting instances. I’m into tech, literature, and indie games but haven’t found an instance that fits. Could anyone recommend NodeBB instances with active communities focused on those topics? Thanks!

    per saperne di più

  • @mcc It is both a PDS and an app view. I'll be publishing a piece about this later today after getting more info. Nothing from Rudy though

    per saperne di più

  • @mattsheffield I do not think, in the context of the post you have made here, shatteredsky is "a PDS". I think we are using terminology differently and this is making it difficult for me to follow the conversation.

    per saperne di più

  • @mcc It's possible that Rudy has an independent app view because that can be part of a PDS, but he is not deploying it because his users wouldn't be able to use a mobile app to interface with.

    They tout the ability to log in via the Bluesky app into Blacksky PDS, and possibly this is why that traffic is happening.

    I have seen Link's account on another PDS, which does suggest that the app view and labeler are both live issues, as you're surmising. https://social.shatteredsky.net/profile/did:plc:63hvnyjvqi2nzzcsjgnry5we

    per saperne di più

  • @mattsheffield In the screenshot, you see two headers: atproto-accept-labelers, which shows two labelers i assume to be bluesky and blacksky, and atproto-proxy, which indicates which appview is to be used (source: bryan newbold from bluesky), and shows only api.bluesky. So I believe both issues are live. But I am more worried about the appview/atproto-proxy issue, because out of the two, I assume it to be the more difficult issue to fix.

    per saperne di più

  • @mcc I think I did see it, the one referencing the network traffic from bsky.app? I think that's because the labeling instructions are pulled from there and assembled by the client. So it appears to be an app view issue but is actually a labeling one.

    But you're right that only Rudy can clarify this

    per saperne di più

  • @mattsheffield *sighs*

    I feel like I'm having a lot of repetitive conversations. The thing you are claiming was my conclusion as of last night, but then I was shown an additional piece of evidence, which makes me conclude something different. This was documented in one of the threads I link above, but I link a lot of things above, so I assume you didn't see it. I can explain it, but it would make more sense to just wait for Rudy (who I've asked for an explanation) to explain.

    per saperne di più
Post suggeriti