William Oldham (@binary_overload) header
William Oldham (@binary_overload) profile picture

Follow me on @bluesky at @ williamoldham . co . uk

Joined December 2015
Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)Photo by William Oldham (@binary_overload)
William Oldham retweeted
5
411
11
3,152
43,275
I don’t know why but the NWS breaking the professionalism is so hilarious to me😭😭 #wxtwitter
10
141
1
2,960
75,686
William Oldham retweeted
can you unblock this pr real quick?
14
333
48
3,256
207,688
weDontNeedElectricityWeAreElectricity redd.it/1go1px0
1
106
8
1,133
49,074
Early signals this museum is for me:
34
238
12
4,937
171,065
William Oldham retweeted
modern = weak
2
2
1
143
9,406
William Oldham retweeted
github built the final boss of dashboards
155
449
54
9,471
1,106,693
William Oldham retweeted
psql
11
197
14
3,467
136,428
William Oldham retweeted
92
825
113
11,282
358,516
15
278
23
3,449
146,410
William Oldham retweeted
43
1,415
44
14,788
353,753
William Oldham retweeted
#Caturday shenanigans
8
496
8
16,163
744,996
William Oldham retweeted
9
21
1
200
19,491
William Oldham retweeted
i have very severe adhd (hyper focus) so my girlfriend and i started using a traffic light (red/yellow/green) system
226
3,920
1,218
137,798
4,558,574
William Oldham retweeted
it’s all libc
8
223
18
2,923
149,072
William Oldham retweeted
I’m finding it very difficult to muster an argument against this.
1,335
3,778
180
83,652
4,904,813
William Oldham retweeted
cloud was a mistake
12
460
38
7,697
367,103
William Oldham retweeted
Replying to @D322Mw
20
125
6
2,525
19,074
There has to be some illegality here with this code in place and now knowing that @photomatt openly misrepresented the .org domain to be owned by the Foundation for YEARS. Now we know it is owned by him, an individual, who is facetiously collecting information on EVERY WordPress website, even local dev environments, private environments, and possibly top secret government environments if they pull updates from .org Sounds like a lawsuit waiting to happen.
So I was trying to figure out how Automattic knows the WP Engine websites. If you actually look at the payload to the WordPress.org API to get the list of plugins, WordPress is adding the URL on the user-agent. There's absolutely no technical reason to do this, it's just to obtain more data. They could just as easily leave the URL out and leave in WordPress/6.6.2. So with each call, WordPress.org is getting the WordPress version number, the website it's installed on, and the IP address it's installed on. All they have to do is check when that IP address changes and they'd know that the hosting provider changed. This is actually pretty intrusive. The API call in this case was api.wordpress.org/plugins/in…. You can inspect this yourself using the HTTP Requests Manager plugin.
4
13
1
59
7,689