JP

@froztbyte
311 Followers
923 Following
7.5K Posts
Digital shamanism, communes with machine spirits. Knower of arcana. Beardwielder even before lockdown beards. Perpetually overloaded atm.

Something vexing:

I've got a lot of ideas for improving things, but they're mostly infrastructure / ecosystem projects.

It's very difficult to connect any of them directly to the things people insist they need today.

For example:

  • Key Transparency for the Fediverse
    • E2EE for ActivityPub can leverage this
    • AuxData is useful for other protocols

It's difficult to get most people to know or care about this!

But if you want a federated Discord replacement that can be easily self-hosted without making the host a juicy target for privacy invasions, and you don't want to require users to manually verify keys, this work is essential.

RE: https://mastodon.social/@Annacats/116101519744925445

rip to my blep, 4mo gone now :<

them: as a senior engineer, i expect you to discuss tradeoffs in your technical solutions

me: cool, let’s talk about the externalities of LLMs

them: wait not like that

Today we had a fire alarm in the office. A colleague wrote to a Slack channel 'Fire alarm in the office building', to start a thread if somebody knows any details. We have AI assistant Glean integrated into the Slack, and it answered privately to her: "today's siren is just a scheduled test and you do not need to leave your workplace". It was not a test or a drill, it was a real fire alarm. Someday, AI will kill us.

this one has been sitting in my head ever since i first saw the generator.

https://marshdeer.github.io/xkcd2501-generator/

The upcoming #letsencrypt DNS-PERSIST-01 will make it easier to have LE certificates for internal services.

https://letsencrypt.org/2026/02/18/dns-persist-01

Personally I've used HTTP validation with split-DNS rather than DNS-01 for internal services, but I will likely switch to DNS-PERSIST-01 once it is deployed and supported by certbot.

DNS-PERSIST-01: A New Model for DNS-based Challenge Validation

When you request a certificate from Let’s Encrypt, our servers validate that you control the hostnames in that certificate using ACME challenges. For subscribers who need wildcard certificates or who prefer not to expose infrastructure to the public Internet, the DNS-01 challenge type has long been the only choice. DNS-01 works well. It is widely supported and battle-tested, but it comes with operational costs: DNS propagation delays, recurring DNS updates at renewal time, and automation that often requires distributing DNS credentials throughout your infrastructure.

@xabean @static a fun game I like to introduce people to: make a blind guess how many (currently active and applicable) DNS RFCs there are, don’t look it up. done it? okay write your number down, and *now* go look

can do the same for TLD zones, too

(few people tend to even be in the ballpark of the right numbers, even among generally better tech clue. talking sub-20%, ime to date)

Guy with neurolink cut me off in traffic, pulled out my flipper zero and gave him gender dysphoria