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

🔧 Devlog: FediBuzz relay returned 400 errors.

Technical Discussion
1 1 0

Gli ultimi otto messaggi ricevuti dalla Federazione
  • 🔧 Devlog: FediBuzz relay returned 400 errors. Root cause: nginx 1.18 + HTTP/2 + hyper/reqwest sent duplicate Host/:authority headers. Fixed by upgrading to nginx 1.29.4 which handles HTTP/2 headers correctly (fix from Aug 2025).
    read more

  • Thanks, I hadn't read that ... but I wasn't thinking about any one particular incident, I've heard similar things from a lot of people.

    I know where I am on this, but still curious to see the results of the poll!

    @onepict

    read more

  • @reiver nope. I have been cleaning up sloppy "vibe coding" for a month straight on a contract. Security, scalability, and code clarity are impacted by this approach.

    read more

  • @reiver
    Your poll is biased.

    You're asking people to explain why they do NOT want to use such (immoral and energy-intensive) tools.

    But you're NOT asking for reasons why people WANT to use such (immoral and energy-intensive) tools.

    Nice try! 😎

    read more

  • @reiver @dansup
    We should embrace any tools that respect creators privacy and produce safe code and that can enable new creative “minimal viable products” apps to ship even if they are likely to need to mature using more traditional programming later.

    read more

  • @julian @reiver @fedicat @johannab

    Need only look at Palantir porting the operations of the US government to AI systems, and similar corporations (entire supply lines), to see this worrying trend.

    read more

  • @julian @reiver @fedicat @johannab

    Furthermore I guess the killer app for AI is "Autoritarianism". Allow a small group of bad actors to control entire populations, by letting AI wade through the wealth of information collected via surveillance capitalism, weeding out patterns of resistance well before it becomes any serious threat. And a dictator doesn't care about that 5% error margin, where the AI got it wrong.

    read more

  • @julian @reiver @fedicat @johannab

    > The problem is that some people use AI as a shortcut to no longer think.

    The issue is bigger than that, I think. One needs expertise to work with AI responsibly, and recognize where it goes off the rails. In our own expert areas we invested the time to be able to correct AI output.

    In all other areas, where we'll have to use hastily-introduced AI, we too are unable to detect its flaws. While AI poses as expert on anything, and is integrated everywhere.

    read more
Post suggeriti
  • 0 Votes
    2 Posts
    6 Views
    @vftdanTor: here is a list https://fedilist.com/instance?q=&ip=&software=&registrations=&onion=onlyI2P: http://mastodon.i2p is currently onlineYggdrasil: there was a few, but I can't find them now
  • 0 Votes
    1 Posts
    6 Views
    I've gone live!Fireside Fedi - Episode 64 - Jo Blakely - Artist (Oil, Acrylic, Digital)#owncast #streaming #interview #fediverse #fedi #people #show #firesidefedi #FsFhttps://stream.firesidefedi.live
  • 0 Votes
    13 Posts
    69 Views
    silverpill@mitra.social I have been reflecting on the use of Remove/Move vs Update and I am thinking that Update isn't explicit enough. If I am removing a topic from a category, I'd be sending an Update with the group actor removed from the audience property. However recipients wouldn't know which audience was removed, merely the new state of that context's audience.
  • 0 Votes
    1 Posts
    15 Views
    Apologies in advance if I misrepresented anybody or missed any crucial bits of information. Jesse Karmani (jesseplusplus@mastodon.social), Ted Thibodeau Jr. (tallted@mastodon.social, and Julian Lam (julian@activitypub.space) in attendance Julian provided an update on adoption of FEP 7888 Both Piefed and Lemmy have adopted 7888, and will begin publishing resolvable context collections in their next release Jesse opened a PR to Mastodon, which received preliminary approval from Gargron@mastodon.social (ed. it was later merged, rolled back, updated, a new PR opened, which was then merged) This PR is the first of two planned pull requests. The first generates the outgoing context (the same as what Lemmy/Piefed have done recently) The seconds handles incoming contexts and backfills Jesse was asked whether it would conflict with existing reply-tree crawling methods, but the two are complementary. She expects additional discussion before the PR is opened. Julian noted that it would be helpful if statistics/analytics were gathered by the Mastodon team to see how conversation contexts and backfill works at scale; admits that existing implementations and testing has been small scale and may not reflect real-world usage. Julian noted that Lemmy's implementation (nutomic@lemmy.ml) does not paginate their resolvable context implementation. All objects are listed in one OrderedCollection Jesse noted that she followed Mastodon's pagination convention for collections. Context inheritance Julian asked for opinions on whether contexts were inherited in existing implementations. Notes that NodeBB inherits parent context, but checks further up the known parent chain for further contexts Julian admits that not everybody can and should do this, is also not sure anymore whether NodeBB actually does this. Julian notes the ideal implementation would be every object referencing their immediate parent, which would lead to the entire collection referring to the same context collection. Jesse: Decodon inherits immediate parent context only Ted: notes that this is a reinvention of inReplyTo Julian and Jesse note that there are marked differences between crawling the reply chain. A short discussion about how netnews and usenet handled reply chains was had. Julian notes that Lemmy will not inherit context. Every object will point back to its own server's context collection. This was a conscious decision by Nutomic as each instance is meant to consider its own representation of remote content as the canonical representation ActivityPub.Space Julian made a short shout-out to a new site called ActivityPub.Space, meant to be a hub for AP development discussions ("A federated space for ActivityPub discussions so that they don’t just get lost in ephemeral replies") A short double-back to NNTP and how they approach "eventual consistency" Ted: “Cloud of NNTP servers are all hosts of articles and replies.” Strictly speaking it’s not a reply tree as replies can be inReplyTo multiple parents