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

Fediverse & AI Coding Tools & Vibe Coding


Gli ultimi otto messaggi ricevuti dalla Federazione
  • definitely not a fan of this. tbh, there should just not be a global feed that new accounts see, because they see a lot of stuff they don't understand or know the community norms for, and that leads to bad engagement.

    read more

  • There is the Web Share API, and the future Web Share Targets API, but I think we could also align Web Share with FedCM and be able to say "I want to share to this type of application"

    read more

  • @reiver i think the disjunction between Object and Link was actually unnecessary. https://github.com/w3c/activitystreams/issues/666

    i also think there's too much emphasis on types when there really shouldn't be -- it's the *properties* that you end up using almost all of the time. pretty much the only types that actually matter are the Activity types (because you can't infer those).

    read more

  • @haitchfive

    I don't think it was me, but — it seems interesting.

    https://github.com/ha1tch/quertfy

    .

    read more

  • @reiver Did you and I discuss queryfy a while ago, or was it one of my other projects?

    Just wondering whether I owe you a heads up since queryfy has been bumped up to v0.3.0

    read more

  • With ActivityPub / ActivityStreams...

    To me, it feels like there should have been something that is a common parent of both 'Object' and 'Link'.

    That just had the "name", "nameMap", and "preview" fields (along with "id" and "type, of course) — since that is what 'Object' and 'Link' share in common.

    I'll just call this common parent: 'Entity'.

    ...

    It could have even been an opportunity to talk about how to handle unknown types.

    read more

  • @soapdog@toot.cafe hmm... just thinking aloud here.

    You posit in another post that the network effects inflate exponentially:

    > Push models are resource hogs that approach exponential growth in a large network like the fediverse

    That's not true. If you post a message then it sends a copy to each follower. That's linear growth. If you collapse recipients via shared inboxes you can reduce that further.

    If you're referring to the torrent of requests that happen if your post is shared (the "thundering herd" problem) then that's actually a PULL happening from those requesting instances!

    Secondly, in a pull model of AP, you would need to continually poll servers of all your followers so as to approach a real-time effect. You'd be polling servers over and over again, and many of them would have nothing new, with so much wasted traffic.

    If your expectations include semi real-time updates, the push model is much more performant, in my humble opinion.

    read more

  • @evan @mariusor @silverpill i think we probably need to revisit the user story of creating multiple objects at once, or more accurately, the user story of minting and binding multiple identifiers at once.

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    7 Views
    It’s #Sunday, where are you scrolling #Mastodon from today? #Fediverse #FediHelp #Laptop #Desktop #Phone #Tablet #Poll
  • 0 Votes
    1 Posts
    10 Views
    There are two big features in release v3.1.3 of Ktistec: auto-approve followers and a new image viewer.Auto-approve followers is conceptually simple ("the server automatically sends an Accept activity when it receives a Follow activity") but it required extensive changes to some of the oldest code in the codebase: the inboxes and outboxes controllers. I refactored inbox and outbox side-effect processing into independent services, which made it possible to support side-effects like auto-approve follow (and also auto-follow back), without having to go through the controllers.A more significant change for me personally was replacing the lightGallery image gallery (an external dependency) with my own implementation. It's not as slick, and not as full of features—I wrote it in two days—but it is fully free software, and that's important to me.AddedAdd admin page for managing OAuth access tokens.Add support for auto-approve followers. (fixes #26)Add support for auto-follow back.FixedPrevent triggering actor refresh when user is anonymous.ChangedReplace "lightgallery" dependency with custom image viewer.Set OAuth access token expiry to 30 days (previously expired after 24 hours).Refactor inbox and outbox processing into dedicated processor services.The OAuth changes set the groundwork for better support of the Mastodon API and the Fediverse clients that depend on it. Stay tuned!#ktistec #fediverse #activitypub #crystallang
  • 0 Votes
    4 Posts
    18 Views
    @giacomo @informapirata @beachcomber @alephoto85 Snac2 is great. The only thing that got me back at hosting a full mastodon instance was because I wanted to use a mastodon mobile app fully. So it depend how you intend to use it :)But like I just said; a mastodon app. Snac2 is not Mastodon. It has, howerver, a "compatibility" mastodon API. It was just not enough for me personally.But beside that; Snac2 is really a game changer. Stable, reliable and low on memory/cpu usage.
  • 0 Votes
    12 Posts
    64 Views
    It's a good approach, it's exactly how NodeBB operates as well. We have a FOSS software and we sell managed services for those who don't have the technical know-how. Win-win.