Welllllll this isn't great.

Google Just Patented The End Of Your Website

"...a system that evaluates your company’s landing page in real time and, if it decides the page won’t perform well enough for a specific user, replaces it with an AI-generated version assembled on the fly. The user never sees what your team built, they see what Google's machine learning model thinks they should see instead."

https://www.forbes.com/sites/joetoscano1/2026/03/06/google-just-patented-the-end-of-your-website

#SEO #Google #AI #enshittification

It's clear that AI assisted coding is dividing developers (welcome to the culture wars!). I've seen a few blog posts now that talk about how some people just "love the craft", "delight in making something just right, like knitting", etc, as opposed to people who just "want to make it work". As if that explains the divide.

How about this, some people resent the notion of being a babysitter to a stochastic token machine, hastening their own cognitive decline. Some people resent paying rent to a handful of US companies, all coming directly out of the TESCREAL human extinction cult, to be able to write software. Some people resent the "worse is better" steady decline of software quality over the past two decades, now supercharged. Some people resent that the hegemonic computing ecosystem is entirely shaped by the logic of venture capital. Some people hate that the digital commons is walled off and sold back to us. Oh and I guess some people also don't like the thought of making coding several orders of magnitude more energy intensive during a climate emergency.

But sure, no, it's really because we mourn the loss of our hobby.

Yes. tmpfs filesystems should be creatable by unprivileged users and mediated by file descriptors.

It should be possible to mount them (through both mount mechanisms and directly or indirectly via FUSE) and to pass them through pipes (by descriptor).

It should be possible, with an open filesystem fd to get dirfd streams and do whatever operations one feels like through openat & friends (here comes the indirect FUSE support path).

This would be a sensible way of finally solving the main problem of UNIX pipes & structured data interchange.

Reminder: AI "generated" code is 100% plagiarized. You must not accept code of unknown provenance into your code base. Doing so opens you up to potential copyright infringement lawsuits. Nobody needs a repeat of the SCO vs IBM lawsuit over ownership of Unix.

Accepting AI-assisted code is just legally untenable. That's black and white, there's nothing to debate. Projects that accept it are idiots and should be shunned.

https://mastodon.social/@hyc/114777864519941643

In preparation for daily driving #MobileLinux I've been thinking a lot about what must be done for reliable and power-efficient push notifications.

Spoiler alert: while UnifiedPush may be a relevant service for some apps, it's not where platform dev focus should be. We want a future full of p2p apps that reject permanently-addressable "servers" entirely, after all! And centralization is not where the bulk of the power-saving magic is anyway. The "magic" is in the fact that the SoC can be in deep sleep and the modem will still wake it up with an interrupt when data arrives on an open connection. It should be fine to have apps' own service processes listen for notifications!

My rough sketch of a to-do list would be:

• making sure wakeups don't turn the display on xD
• research into what's needed to set up filtering on the modem for which sockets can wake the SoC up (but initially, fine to just rely on "nothing else has open sockets anyway, only the background services waiting for pushes" maybe?)
• easy API for establishing the push connection specifically over mobile data if available (since only modem supports wakeup well rn)
• support for robust background services: unlike what the Background portal offers now, let #Flatpak apps install systemd-user services, which would have metadata connecting them to the .desktop entry, making them introspectable and accountable via settings GUIs (not via control center popups! they shouldn't show up as "annoying left-over in-process thing possibly eating battery"! they're a different thing, expected to run permanently!)
• actually getting apps to separate push notification listeners into background services

#postmarketOS #linuxmobile #freedesktop