Phantasm

@phnt@fluffytail.org · Joined ⁨Jun⁩ ⁨2023⁩

Professional thread derailer.
Bad posts ahead.

Alts when my instance is broken: @phnt@pl.borked.technology @phnt@annihilation.social

pfp and banner shamelessly stolen from Alessandra Maria

76 69 84 39 83 32 65 76 76 32 76 79 86 69 32 76 65 73 78
Public XMPP (Almost never checked)
phnt [at] 404 dot city
An attempt at a blog
https://evilmaid.net verified

Replying to @⁨silverpill@mitra.social⁩

@silverpill @technical-discussion @benpate If you are going through the trouble of using your own vocabulary, why not at least make it so that namespace conflicts don't ever happen again, similarly like they do with semantics using AS Vocab now.

If you implement OfferEndorsement and I want to use it as well, but for something incompatible with your thing. Then I guess I need to invent a new less descriptive name for my thing like: NewAPServerOfferEndorsement, if you effectively reserve that name for your thing and depend on that name being unique for handling.

So I think, something like below is a better solution to the same problem, while admittedly looking worse:

  • fep-3447:OfferEndorsement
  • fep-3447:AcceptEndorsement
  • fep-3447:RejectEndorsement
  • fep-3447:UndoEndorsement

Or

  • fep-3447:Offer
  • fep-3447:Accept
  • fep-3447:Reject
  • fep-3447:Undo
>Here's a well written post why using LLMs to scan your code for issues is actually a good idea, especially now and in the future.
<Yeah, but LLM code quality sucks though. And you shouldn't use them for fixes anyway, as that introduces more issues.

How is it possible that infosec people are like that. Present them with the most agreeable and factual stance, and they will turn the argument into a "yeah, but actually no!"

Replying to @⁨lain@lain.com⁩

@lain My suspicion mostly comes from the fact that the project was almost dead and now there's a new release like every two weeks and 3 major versions with breaking changes in less than 6 months. It's either lack of care and just pushing things in a move fast, break things mentality, vibe coding, or the project is sponsored behind the scenes by someone with certain goals/features they want. Could be all three honestly.

Anything newer than Hackney 1.20 is such a broken mess. Probably being vibecoded with how things are changing quickly and releases getting pushed.

First checkout timeouts break, then happy eyeballs causes connection to be stuck for 5+ seconds on start and now pooling is completely different (worse) and proxying is barely functional.