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. General Discussion
  4. @Gargron what a step!

@Gargron what a step!

General Discussion
1 1 12
Log in to reply

Feed RSS
@Gargron what a step!

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • fedifollows@social.growyourown.servicesundefined

    I've had requests for accounts to follow on here for specific countries/regions.

    Fediverso fediverse mastodon
    1
    0 Votes
    1 Posts
    11 Views
    fedifollows@social.growyourown.servicesundefined
    I've had requests for accounts to follow on here for specific countries/regions. There are many listed at:➡️ https://fedi.directory/local-and-regionalThis has accounts from most European countries, all US states, all Canadian provinces etc. (Some have fewer accounts than others though.)To follow an account listed on the site, copy-paste its Fediverse address into the search box in Mastodon, then click follow.To find out more about an account on the site, click its Fediverse address.#Fediverse #Mastodon
  • max@poliverso.orgundefined

    I think this is really important.

    Fediverso mastodon fediverse
    1
    0 Votes
    1 Posts
    12 Views
    max@poliverso.orgundefined
    I think this is really important.#fediverse#mastodonRE: social.growyourown.services/us…
  • julian@activitypub.spaceundefined

    Minutes from 6 November 2025 WG Meeting

    Uncategorized forumwg swicg activitypub socialcg
    15
    0 Votes
    15 Posts
    50 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.
  • wjmaggos@liberal.cityundefined

    Thanks for speaking up Rudy (even though he did throw a dig at #ActivityPub in the thread).

    General Discussion activitypub xitter atproto bluesky
    5
    0 Votes
    5 Posts
    24 Views
    mastodonmigration@mastodon.onlineundefined
    @wjmaggos Yeah, but feel bad for the guy. What's happening is that there is an adversarial relationship developing and Bluesky holds all the cards. This is not going to end well for Blacksky.This has always been the problem with corporate sponsored standards. If the technology host company is not fully and completely committed to open competition with their standard clients it can never work.