SnotFlickerman

Oh look at that, another reason why I don't want to be forced to use the same Public Ledger of Credentials as everyone else. I want to use a PLC where these motherfuckers don't get to have an account.

Get more decentralized, Bluesky and AT protocol, or get fucked.

It's not even worth talking about how all the Republican party stands for anymore is triggering others while acting like they're not actively trying to trigger others. It's the adult equivalent of someone waving their hands in your face and invading your personal space while going "I'm not touching you!"

What needs to be discussed is how to kick them to fucking curb and force them to stay on the fucking curb instead of letting them bring their childish fucking behavior to every service under the sun just so they can harass other people.

She says that if I can’t even have the courage to “go outside often and be a ‘normal’ human being”, I wouldn’t be able to handle/manage the assets/investments they have. (Small bussiness, won’t go into detail about it)

Your mother is a giant fucking asshole. Neither of those things have anything to do with one another. Nerds have created whole businesses online while barely seeing the light of day and have become millionaires and billionaires from it while barely seeing the light of day.

Secondly, if she really think their "small business" is going to survive the purposeful collapse the wealthy are going to put us through, she's not just an asshole, she's also a certified fucking moron.

I ran into the same issue and after some digging around found this nasty looking hack that seems to work at preventing the auto-formatting of links in markdown (still looks a bit wonky on mobile like Jerboa tho):

https[]()://noai.duckduckgo.com/?q=%s

appears as:

https://noai.duckduckgo.com/?q=%s

For Firefox on Android (which TenBlueLinks doesn't have listed) add a new search engine and use these settings:

Name: Google Web

Search string URL: https://www.google.com/search?q=%s&udm=14

~~as @Saltarello@lemmy.world learned before I did, strip the number 25 from the string above so it looks more like this:~~

~~www .google.com/search?q=%s&udm=14~~

~~Edit: Lemmy/Voyager formats this string with 25 at the end. Remove the 25 & save it as a browser search engine~~

~~EDIT: There's got to a Markdown option for disabling markdwon auto-formatting links, right?? The escape backslash seems to not be working for this specifically.~~

EDIT II: Found a nasty hack that does the trick!

https[]()://www.example.com/search?q=%s

appears as:

https://www.example.com/search?q=%s

As stupid as it is: Faith is what keeps bubbles afloat. Faith can go a long way towards forcing reality to what you want it to be, and if you have the wealth, you can play nearly endless money-games to make it seem like you're ahead when you're actually losing your shorts.

The reason there is so much faith is because this is a make it or break it moment for late stage capitalism. The businesses (including non-AI businesses) viscerally need it to work so they can get rid of human workers. If they can't make humans slaves, they will make digital slaves. This may be a last gasp for the old order if it fails because so many entrenched companies from automobile makers like GM and Ford to airframe makers like Boeing to general electronics like General Electric have finances that are literally upside down because they have been using stock buybacks to fake growth for the better part of two decades now absolutely need it to happen to stay afloat.

It is difficult to get a man to understand something, when his salary depends on his not understanding it.

This quote by Upton Sinclair is usually used to describe lower level employees who don't understand how unionization could be good for them, but it applies here as well. The faith persists because this is their "salaries" that depend on this working so the bottom doesn't fall out from under them. They have to believe it will work and as such will keep dumping money into it as long as humanly possible.

AI is like Theranos but bigger and affecting numerous industries who are all betting the future of their companies on this all working out. For their livelihoods and their plan to continue ignoring all the little people in the world, there is no losing state they can or will accept until they are on the edge and about to leap from the top of their buildings to avoid the consequences.

Once the faith breaks, it will be like a dam breaking and flooding out too fast to escape.

The patch is for Windows 10, Windows 11, and Server 2008 up to Server 2025.

Further, there's companies that make custom-built modern machines that support classic PCI and modern operating systems and classic operating systems.

It's conceivable that legacy systems are using modern OSes with virtualization running a legacy OS and legacy PCI cards, for example. It's not beyond the realm of possibility.

https://nixsys.com/legacy-computers/pci-slot-computers

Right, it was referenced in one of the articles that a bunch of legacy industrial machines likely still use this hardware, so the people using those old machines are probably going to have to go dig up PCI modems from that era without the Agere/Lucent chipset.

I'm sure you're right and there's lots of stuff they've missed like this over the years that they sort of kept on for compatibility but that opens exploits due to how old they are.

Other articles make more clear why that is.

https://cyberpress.org/windows-agere-modem-driver-0-day-flaws/

Rather than issuing a traditional patch for each vulnerability, Microsoft’s October cumulative update completely removes the ltmdm64.sys driver from affected systems.

As a result, all fax modem hardware relying on the Agere Modem driver will cease to function. While mail and messaging over IP have largely supplanted analog modems, some industrial and legacy applications still depend on fax modems.

Organizations must therefore audit their environments for any remaining modem dependencies and either migrate to supported alternatives or implement workarounds where available.

Microsoft’s advisory explicitly recommends that customers eliminate any reliance on the deprecated hardware to avoid service disruptions.

So maybe not all the way back to the original release, but back to the first release that included this specific telephony modem driver, ltmdm64.sys. If I recall correctly, Windows 3.1 brought networking capabilities.

However, another article claims it has only been shipped with every version of Windows since 2006.

https://www.thestack.technology/windows-users-hacked-due-to-legacy-fax-modem-driver/

CVE-2025-24990 was credited to a security researcher going by the handle @shitsecure who told The Stack by DM “it’s a driver from 2006, never changed… I think it was historically shipped with everything, although that doesn’t make sense at all.”

Which honestly makes a lot more sense, since the "64" part of the driver name implies it's for 64 bit systems, which were first introduced in 2003.

Some more extraneous info on this driver/hardware:

https://www.sysnative.com/forums/drivers/1216/driver

https://theretroweb.com/chips/10725

https://en.wikipedia.org/wiki/Agere_Systems

Perhaps, either that or they made a very quick fix making updates to address them the day before this patch release.

To anyone misreading this, these exploits were patched yesterday and thus were included as the final patch for Windows 10 before the extended security updates requirements kick in.

Known exploits are always reported to the company first to give them time to patch it before releasing info on the exploits.

All Windows 10 users will continue to have access to the patches in this final freely available patch Tuesday for Windows 10. They just can't get new updates without joining the ESU program.

I hate Microsoft too and only use Linux, but let's stop the circlejerk of false claims here please and thank you.

The patch has already been released, that's literally my point. It was part of their final patches released for Windows 10 yesterday.

This is from the CVE page for the exploits discussed in the srticle.