Salta al contenuto
Citiverse è uno spazio aperto a tutte le comunità. Se vuoi aprire un gruppo locale o una sezione per la tua organizzazione, puoi contattare gli amministratori: pagina dei contatti.

FEP-c0d0: Context Locking

Technical Discussion
28 8 86
  • 0 Votazioni
    1 Post
    5 Visualizzazioni
    Nessuno ha risposto
  • 0 Votazioni
    1 Post
    24 Visualizzazioni
    Nessuno ha risposto
  • webfinger package for NodeJS

    Social Web Foundation activitypub code nodejs webfinger
    2
    0 Votazioni
    2 Post
    33 Visualizzazioni
    julian@activitypub.spaceJ
    @evanprodromou@socialwebfoundation.org I was curious what your package does that mine doesn't, so I threw qwen at it. I've cut out much of the fluff, but the gist (feel free to skip it): > ## What the package does that NodeBB doesn't > > - rel query parameter — passes rel to the server for server-side link filtering (NodeBB always fetches all links and filters client-side). > - First-class aliases and properties accessors (NodeBB buries them in _raw). > - link(rel, type) selector with exact media-type matching (NodeBB filters inline with assertAccept substring matching). > - Frozen/immutable result objects. > - Zero dependencies, native fetch. > > ## What NodeBB does that the package doesn't > > - Caching (positive 24h, negative 10min) + split-domain cache-bypass under strict. > - 5s timeout. > - Content-type validation with an application/octet-stream → JSON.parse fallback for non-compliant servers (package just calls res.json() and throws). > - Subject handling: fixes missing acct:/did: scheme, extracts subjectHostname, computes splitDomain. > - strict mode (rejects cross-domain subjects). > - actorUri extraction (rel=self filtered by accepted ActivityPub types) and publicKey extraction. > - false-on-failure semantics (callers do result || {...}). > - Hostname round-trip validation (new URL('https://'+host)/ check) and cache-key normalization. > > ## Latent bug in the package > > It uses static URL.parse() for URL inputs — deprecated since Node 10 and slated for removal. It still works on this Node 23 build, but it's a ticking time-bomb on the Node versions it targets (22/24/26). It reads like NodeBB's webfinger parsing is more battle-tested because I've had to handle funky webfinger responses from slightly out-of-spec servers. There's potential for me to use your package as a low-level fetcher though.
  • 1 Votazioni
    5 Post
    52 Visualizzazioni
    django@social.coopD
    @dansup @nuages
  • 0 Votazioni
    14 Post
    32 Visualizzazioni
    silverpill@mitra.socialS
    @elgg Not underestimating, I am just trying to understand how it works. Judging by outbox contents, it is not a FEP-1b12 group. Looks like an announce-bot to me, but then, how do you achieve privacy? Private Announces?
  • 1 Votazioni
    3 Post
    220 Visualizzazioni
    macfrancM
    @team@blog.purewebhosting.nz @gwilymgj@mastodon.social Standardising Public Information Publishing I think you should discuss this with the @swf@socialwebfoundation.org group. The issue of standardization is one of the most delicate in the relationship between the fediverse and the mastosphere, and will likely be resolved in different ways based on the so-called "doocracy." It will be important for it to adhere as closely as possible to W3C standards and be conceived in simple terms. Some platforms like Friendica have already solved the formatting of georeferencing and event data. (cc @heluecht@pirati.ca is right?) Should an entity run it’s own presence much like they run their own website or email? It depends a lot on the type of organization. A nonprofit organization could simply choose to be hosted by a federated social network in its own country. A public institution could do the same, but first consider opening a proprietary instance, since, depending on the institution's importance, the traffic flow could become problematic. A private company, on the other hand, has the obligation to create its own instance. If I were to manage an organization's faith migration, I would make these assessments by evaluating the TOSs of the instances in my country and, if I found one suitable, I would agree on my inclusion in advance with the instance administrators. I also remember that careful management of a federated WordPress or Ghost server is already an interesting solution, just as a federated NodeBB forum allows you to wonderfully control the moderation of your audience of interested users. Possible disadvantages Here we must be realistic: using commercial social media for your organization's communication is NEVER perceived as a problem! It will be difficult to obtain the exact costs of managing a social media account, and the employees (or vendors) who manage an organization's social media account are resistant to change. My advice is to find out in advance whether the organization already uses automated publishing systems, whether these systems include at least the Mastodon API, and whether these systems include engagement measurement systems; If they don't use automatic publishing, you can find a system that helps them manage everything more easily. I may be unpopular, but an organization shouldn't be forced to do without commercial social media! Any organization's social media strategy should have three ethical obligations: Maintain a presence on the most popular commercial social media platforms that are consistent with its audience, to ensure maximum reach. Maintain a presence on an open-source social network that allows users to follow the organization and interact with it without being tracked, profiled, or having their data transferred to problematic countries, because this is a guarantee for its customers/users. Prioritize communication on the open social network, publishing content on the federated account earlier and more carefully, and possibly attempting to move communication to the federated account.
  • 0 Votazioni
    1 Post
    27 Visualizzazioni
    Nessuno ha risposto
  • 0 Votazioni
    2 Post
    51 Visualizzazioni
    reiver@mastodon.socialR
    @wjmaggos CBOR is more difficult than JSON-LD.(AT-Protocol uses CBOR where ActivityPub uses JSON-LD.)

Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy

Il server utilizzato è quello di Webdock, in Danimarca. Se volete provarlo potete ottenere il 20% di sconto con questo link e noi riceveremo un aiuto sotto forma di credito da usare proprio per mantenere Citiverse.