Max Inden

@mxinden
144 Followers
147 Following
130 Posts
Network engineer working on #Firefox, focusing on HTTP/3 and #QUIC
GitHubhttps://github.com/mxinden/
Homepagehttps://max-inden.de/
Worth a read: Prompt Injection as Role Confusion https://role-confusion.github.io
#LLM #AI #PromptInjection
Prompt Injection as Role Confusion

LLMs can't tell who's speaking. We show they identify roles by writing style, not tags, and exploit this with CoT Forgery, injecting fake reasoning that models mistake for their own thoughts.

Oh cool, the Firefox Roadmap is public and includes some experimental & upcoming features that people can play with RIGHT NOW.

https://www.firefox.com/en-US/whatsnext/

See what's next for Firefox

See and shape what’s next for Firefox.

Firefox
curl.se now advertises HTTP/3 and HTTP/2 support in DNS so you should be able to read the curl documentation several milliseconds faster than before

Do you obsessively care about web performance?
You can save one whole RTT by putting HTTPS (and H2/H3) support right in your DNS. Also gives you a bit more privacy (sometimes, it depends. Terms & Conditions apply)

See https://savearoundtrip.com/ for more. (HT @mxinden)

savearoundtrip

Publish an HTTPS DNS record. Let browsers reach HTTP/3 on the first connection instead of wasting a round trip.

savearoundtrip: publish an HTTPS DNS record, skip a round trip https://lobste.rs/s/wlm6dv #networking #web
https://savearoundtrip.com/
savearoundtrip: publish an HTTPS DNS record, skip a round trip

0 comments

Lobsters
cloudflare.com advertises HTTP/3 in its HTTPS DNS record, so browsers can use HTTP/3 on the first connection. https://savearoundtrip.com/?d=cloudflare.com#check
savearoundtrip

Publish an HTTPS DNS record. Let browsers reach HTTP/3 on the first connection instead of wasting a round trip.

If your content is served over HTTP/3, make sure your DNS record advertises it, otherwise you're missing out on free performance.

Check your site here: https://savearoundtrip.com/

savearoundtrip

Publish an HTTPS DNS record. Let browsers reach HTTP/3 on the first connection instead of wasting a round trip.

So, uh, yeah...

I am leaving mozilla

It was the best place I ever worked, along with some of the smartest, kindest people who I will miss dearly, but there comes a time when you have to leave.

Leaving Mozilla

> On burn-out and bull-headedness

I'm leaving #Google: https://www.mayrhofer.eu.org/post/leaving-google/

While I believe that I have been able to do some good with my continuing (part-time) engagement in the Android security and privacy team since returning to Austria a couple of years ago, the deal with the US #DoW is completely misaligned with my personal ethical principles. I will, therefore, no longer be able to act as a contact point to Google-internal teams and discussions, but will continue our research on private digital identity, end-to-end secure communication and storage, network privacy, (embedded/mobile) operating system security, supply chain transparency, etc. from a purely academic point of view. Android - and in particular AOSP - will remain a research interest, so please feel free to reach out on any of those topics for potential collaborations or discussions on the academic side.

Why I’m Forced to Say Farewell: Google Management Has Lost Its Moral Compass | René Mayrhofer

I am forced to leave Google with 2026-08-31 because of the deal with the US Department of War, which is incompatible with my ethical principles.

René Mayrhofer

TIL that there are DNS HTTPS records you can use to signal that your webserver supports HTTP/3 (and ECH).

If the browser sees a HTTPS record indicating HTTP/3 support it can use that on the first connection, speeding up the load.

@mxinden built a great website for it where you can also test if that record is set for your site: https://savearoundtrip.com

savearoundtrip

Publish an HTTPS DNS record. Let browsers reach HTTP/3 on the first connection instead of wasting a round trip.