Fediverse

The IP is getting listed too

Finding out which vendors read my toots again!

Somebody fix Cassandra at Microsoft.

"Adform has informed affected clients through dedicated communications and provided them with relevant information and recommended actions." <- this only happened after I went public with it.

To clarify a few things:

"Based on our investigation to date, we have found no evidence that the malicious code transmitted users’ IP addresses or information about the websites they visited to an external party. Technical analysis indicates that such transmission may have been possible, and this aspect remains under investigation." <- It did. The code for it is in my blog.

Admore have finally admitted they were hacked:

https://site.adform.com/resources/newsroom/security-incident-company-update/

@blogdiva @bit @nwbt I just came here to say that!

@ethinethin yeah, you’re golden!

@nwbt @LappenjammerDieZweite and yet the answer usually is still "Linux"

:blobcatpeek:

Please submit a PR! Each provider unfortunately has their own convoluted data sets. So needs a fair bit. But an agent should be able to do it quickly.

@ethinethin what kind of cooktop do you have? Induction compatible ones are kinda hard to find (and more expensive).

Omarchy Quattro will automatically detect if you're using Claude or Codex subscriptions, and then make an agent panel available to track limits and usage.

@AdrianVovk @spanezz
From my understanding (& experience), the only situation in #GNOME where a closed lid won't suspend a laptop computer is when the laptop is connected to a keyboard + external monitor (i.e. the "docking station" scenario). As soon as I remove my closed-lid laptop from a docking station, it suspends.

The exception I can think of: laptops BIOSes that only do "Modern Standby" (S0ix) instead of real S3, as LTT found out on Windows 3 years ago: https://youtube.com/watch?v=OHKKcd3sx2c

#ACPI

Haha it’s all good! I’m glad the whole local file/self-hosted thing is catching back on. I’m just having a think on the whole thing.

@nekohayo @spanezz Actually #systemd completely ignores suspend inhibitors when the lid is closed (unless configured otherwise). This is done specifically to avoid this issue. #gnome follows and treats suspend inhibitors as inherently weak (i.e. can be ignored at will)

So that leaves either firmware or kernel bugs. Or a local configuration that messes with systemd's ability to suspend the system, or a local configuration that opts out of the special treatment given to the laptop lid.

@nekohayo @purpleidea @swick @Valentin And @verdre, who originally built these hacks!

@purpleidea
I hear there is A New Hope™ to strike back against the #Linux OoM conditions, thanks to @swick & @verdre, @AdrianVovk and @Valentin : https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/4863

If I am not mistaken, this is the solution for https://gitlab.gnome.org/GNOME/gnome-build-meta/-/work_items/896 🤞