I kind of expected LLM Labs to do a little more capture before stage 4 enshittification. That was faster than i expected. Maybe they captured more B2B than B2C. I wonder if this is going to spike GPU prices again :/

:)

Lock down your cPannel access sysadmins! I used to manage quite a few of these.

theregister

Critical cPanel exploited:

: Exploitation was underway before patches landed, at least one victim reports ransomware demand

It's only a matter of time till they hit your control panel, make sure you are using your tools and firewalls to limit access.

This my opportunity to share that in 2019 somewhere, which took effect in 2023 California told diesel vehicle owners that they would not be able to register or renew their vehicles if they did not meet CARB emissions board standards which were adjusted to a minimum of 2016 CARB standards (which are the most strict in the US). Which meant that your older vehicle was almost certainly not able to pass the emissions testing. If you didn't know, you can't just buy an egr, dpf, and scr system and slap it into your vehicle. Swapping in a 2016+ powertrain with a healthy emissions system into your 1996 pickup would set you back something like 25-35k not including the fab work. Point is, it's not practical and, in reality, what happened was that the state refused re-registration so owner I worked with are driving them without government approval, or had to sell them off an purchase new, expensive headaches. Here is the exact bill.

Bill Text - SB-210 Heavy-Duty Vehicle Inspection and Maintenance Program.

SB 210 Heavy-Duty Vehicle Inspection and Maintenance Program.

CA is not the only state to flirt with these laws, working with the fed EPA to punish owners in some states. Id be happy to talk about CARB and cali's emissions standards. Virginia can force emissions tests and impound vehicles that police suspect have not been maintained or tampered, the can pull you over, and in some cases detain you. You can spend your whole life running from the government, they will eventually come for you. View quoted note →

Noscrypt has some changes staged for library updates, these changes remove all of the unused source code of the vendored copy of libsecp256k1, most was already removed, but trimmed further. I also removed headers of unused modules. Noscrypt symbols are unchanged, and the only symbol change to the libsecp256k1 ABI would be disabling the musig module. If, for whatever reason, you depended on noscrypt for those libsecp256k1 symbols, they will be gone in v0.1.14. Same goes if you relied on those headers for whatever reason (the modules were never enabled, so linking would have failed anyway).

GitHub

Comparing develop...feature/no-ref/update-libsecp · VnUgE/noscrypt

A nostr specific cryptography library written in C - Comparing develop...feature/no-ref/update-libsecp · VnUgE/noscrypt

A reminder to review the assembly of your compiled code on the target arch. You never know what you might find.

nostr devs gonna be mad when HTTP and SSE takes over.