<unnamed>

Public Key

npub1laxpel7l93kdellz978n2z5xfrknhkqalck62eta84wy7xe654zswqh4f5

Profile Code

nprofile1qqs07nqull0jcmxull3zlre4p2ry3mfmmqwlutd9v47n6hz0rva223gpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpp4mhxue69uhkummn9ekx7mqtf0rx6

Publishing to

nostr.wine

relay.damus.io

nos.lol

Last Notes

2026-03-15 23:21:48 UTC

- reply

Follow the hashtag #retrocomputing (and I'm mentioning this given you didn't use it in your post, so it might be the case you've not checked it yet?), depending on your instance you might get a lot of interesting content.
I'm not following it on this instance; at social.sdf.org I'd get a lot of posts from that hashtag.

2026-03-07 09:12:24 UTC

- reply

Some forks and siblings do try to backport e.g. security fixes (and also features) from Mozilla's mozilla-* and comm-* repositories.
What I can imagine totally happening is that, if they are going full GenAI, they'll somehow touch the entire codebase with it. They've done reformattings and similar changes in the past. Browsing through the mercurial history becomes more fun, and, more importantly, patches won't apply cleanly as the code went through such modifications. So, now? I can totally see GenAI touching all the files for reformatting so that you can't just backport the reformatting commits.
(And this without considering the whole mess that is JS and HTML features being defined in unversioned, non-stable and backwards-incompatible "living standards". (fetch() comes to mind as an example of this, the defaults were changed, and sites relying on the new defaults broke where fetch() was available with the old defaults...; I didn't check well enough to know whether postMessage()'s new features are an example of this or not (it did break reCAPTCHA in SeaMonkey < 2.53.23)))

2025-01-08 12:45:19 UTC

- reply

I will have to investigate it a bit further. I think I recall seeing something weeks/months ago about authentication failure with another client, but that could be me misremembering, I have to see if I can find that thread.
Meanwhile I did find one other relevant (sub)thread [1], describing the same outcome with Brutaldon.
[1] https://moth.social/@TheVoidTLMB/113079754367119907

2025-01-07 19:30:37 UTC

- reply

I'm having trouble logging in with Brutaldon, the authorization page loads but says "Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method."
Do you happen to know what it might be, is this something I forgot to enable in the account settings? API issue? An issue with Brutaldon or Mastodon?
(I'm using https://brutaldon.org/ with SeaMonkey, I did try Firefox (same result); so far the only thing I've found online is [1] - no idea if that is relevant here.)
[1] https://github.com/mastodon/mastodon/issues/27740

2025-01-07 17:17:15 UTC

- reply

Thanks!