Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categories
  3. Uncategorized
  4. Less than a week till @fediforum's Growing the Social Web unworkshop!

Less than a week till @fediforum's Growing the Social Web unworkshop!

Uncategorized
1 1 0
Log in to reply

Feed RSS
Less than a week till @fediforum's Growing the Social Web unworkshop!

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • sl007@digitalcourage.socialundefined

    @hugh @ink

    Moved Uncategorized wikidata wikipedia activitypub
    1
    0 Votes
    1 Posts
    10 Views
    sl007@digitalcourage.socialundefined
    @hugh @ink hm, wow – probably I am the "almost" in "And yet, as successful as the model is, it’s almost never replicated." ;)If anyone is interested in federating wikidata and thus the whole wikibase, please let me know. We are working fulltime on this (on a very small funding) …#wikidata #wikipedia #activitypub/ https://codeberg.org/Menschys/fedi-codebase
  • julian@activitypub.spaceundefined

    Minutes from 6 November 2025 WG Meeting

    Uncategorized forumwg swicg activitypub socialcg
    15
    0 Votes
    15 Posts
    51 Views
    julian@activitypub.spaceundefined
    trwnh@mastodon.social Yes, you're right. There are nuances and situations where you would explicitly not want to inherit the root object's context. I am dealing with the typical day-to-day use case of replying to an object with the expectation that is be part of the same existing context. However I am more than happy to make this clear in the FEP and spell out alternative situations where context inheritance would not apply. The situation I found myself in was one where anybody can (and does) include whatever context they want. In that case, it's difficult to determine whether disparate contexts are actually referring to a common set of the same objects, or whether they were disparate on purpose (i.e. a fork.) To that end, it meant that as a receiver there was no guarantee that any contexts I'd be sent would map to any contexts I know. Strict root-level inheritance for the common use-case would at least disambiguate a lot of this.
  • evan@cosocial.caundefined

    #ActivityPub project idea - Note-ify server that turns any activity into a Create/Note.

    General Discussion activitypub
    1
    0 Votes
    1 Posts
    17 Views
    evan@cosocial.caundefined
    #ActivityPub project idea - Note-ify server that turns any activity into a Create/Note. So you can follow username%40domain.example@noteify.example and any activities that username@domain.example creates are converted to Note objects and passed along.
  • box464@mastodon.socialundefined

    First time I’ve heard of Gush!, an activitypub based platform for sharing topical interests for video games.

    General Discussion activitypub
    3
    0 Votes
    3 Posts
    36 Views
    silverpill@mitra.socialundefined
    @julian @box464 It is developed by @Tak