adding a little more chaos to the world by trying to browse with a UA that calls itself

Mozilla/9.0 (Windows NT 17.2; Win128; x192) Firefox/230.0

and makes all requests using HTTP 5.0 before falling back to HTTP 2.0 when your poor server doesn't support my future tech

I'm just trying to make the webserver logfiles of the world a little bit weirder
back when I was in the Aggressive Archival business I had a system making two gigabytes a day of requests with the useragent "MSIE LOL"
@foone oh that's more subtle than welhen i drive traffic to websites im responsible for with utm_medium=urmom
@foone reminds me of when i got a request from a ua reporting to be chrome 44 on netbsd i386. or some random sony ericsson phone
@aqua @foone oh look the user agent was carved into magnetic physical media by some old ass neckbeard

@aqua @foone I patched my Mumble client to report it's running on MS-DOS on a Philips HD2581/00 (a toaster). 🤪

I could've just disabled the OS reporting mechanism, but where's the fun in that.

@foone I have an even more future one, webkit larps as Firefox/Chrome 300 when it needs to lie in the User-Agent.
@foone
In a similar vein, after getting tired of Telegram asking me to add my birthday to my account, I set it to the day just before the Unix epoch. I doubt they save it in a way it would be a negative number, but I still think it's funny

@chocobo13 ooh, that's a good idea.

though I guess "people over 56" aren't rare enough that anyone would be silly enough with their site to have that be a problem. It's still a fun idea.

@jkerhin @foone @chocobo13 Isn’t Verizon a former baby bell? Could conceivably have an old AT&T account kicking around in their DBs lol.
@austincnunn @foone @chocobo13 they started as Bell Atlantic in 1983, over a decade after the unix epoch. I think it wound up being my ad blocker suppressing one of their trackers, with this being the JavaScript fallback.
@jkerhin @austincnunn @foone @chocobo13 Yes so at this time there were already customers...

@chocobo13 @foone
What's funny about that? That's literally how unix timestamps are supposed to work.

Next time, try 1901-12-12.

Also, some systems don't care at all. When Steam wants me to verify my age, I always use February 31st.

@leeloo
The spec actually does allow for storing it as a signed number? I didn't realize. Though it makes sense. Would 1901 be far enough back that it would be like the 2038 problem on the early end of the date range?
@foone

@chocobo13 @foone
Of course it uses signed numbers, it was designed in the 1970'es (or late 60'es), how do you think they stored things that occurred in the past? Also, if it used unsigned, 2038 would be the middle, not the upper limit.

The lower limit is 1901-12-13, so the 12th is just outside the limit.

@chocobo13 @foone
68 years and a few days on either side of midnight, January 1st, 1970.
@foone Of course you should fall back incrementally - if 5.0 isn't supported, try 4.1, then 4.0, etc...
@foone I have been known to visit corporate phishing “training” sites using my favourite web browser: NCSA Mosaic 0.9 running on Solaris 2.5.1. It fetches the phishing training link once a minute for a week or two, using HTTP/2.0 over TLS/1.3, because security.
@jpm "oi is joel up to his shenanigans again?" #lang_en
@ellenor2000 I want to see the report from the phishing training provider that says there were more clicks on the training link than employees in the company.
@foone my firefox occasionally uses undefined as the HTTP version which causes so many problems, i had to use chromium for the first time in a while
@foone reminds me of the people who learn about unreleased apple products from browser data. You could really mess with them with a big enough cluster
@foone
I always thought it would be fun to embed photos in the payload of jumbo ICMP packets.
@foone Okay, finally some real humor on Mastodon. 🤣
@lisamelton @foone writing a plugin for Caddy that checks HTTP version and returns "Very funny Foone, now make a real request."
@foone remember to try and negotiate that future encryption on https
@foone Back in the day I did web log analysis on my site, and there were always some weirdoes running or claiming to run BSD, SunOS, or IRIX, in addition to my own hits. I had a client-side hack to annoy MSIE users but didn't have an easy way to praise the weirdoes.
@mdhughes @foone Even IE users on HP-UX or Solaris? :)
@foone how's that expressed in ALPN
@foone "(unlike Gecko)"
@foone you assume the NT kernel version will ever get incremented ever again
@Rairii @foone 10.0.137250.2195
@jernej__s @foone build number is currently limited to 16 bits. they already ran into hilarity when they hit the previous 14-bit limit https://betawiki.net/wiki/Windows_10_build_17000
Windows 10 build 17000 - BetaWiki

An open encyclopedia of software history

BetaWiki
@Rairii @foone I remember the 14-bit limit, and wanted to say something along "hopefully having builds beyond 65k didn't cause too many problems" :)

@foone excuse me can you not please, this hurts my soul

or.. like.. at least use a four-digit firefox version and start reporting bugs, so that whoever poor soul does my job in 2091 has something to start off when firefox 1000 ships

@foone you should identify it as „Microsoft Mozilla - a Product by Meta“
@foone Pffft there's no way Firefox/230 supports anything below TLS 7.3, webmasters will know what's up right away!
@foone LHTML, Like Chameleon
@foone I'm always thinking about what I'd have to do if I time travelled to not stick out in logs