Yes, based on the diagrams on their blog, it looks like this only impacts Snaps.
From the Discourse Blog:
The Linux desktop provides XDG Desktop Portals as a standardised way for applications to access resources that are outside of the sandbox. Applications that have been updated to use XDG Desktop Portals will continue to use them. Prompting is not intended to replace XDG Desktop Portals but to complement them by providing the desktop an alternative way to ask the user for permission. Either when an application has not been updated to use XDG Desktop Portals, or when it makes access requests not covered by XDG Desktop Portals.
Since prompting works at the syscall level, it does not require an applicationâs awareness or cooperation to work and extends the set of applications that can be run inside of a sandbox, allowing for a safer desktop. It is designed to enable desktop applications to take full advantage of snap packaging that might otherwise require classic confinement.
So this looks like it complements and not replaces the XDG Desktop Portals, especially for applications that have not implemented the Portals. It allows you to still run those applications in confinement while providing some more granular access controls.
The reasons for this shift in budget away from funding Free Software and the NGI initiative seems to be an allocation of more funds for AI, leaving internet infrastructure by the wayside. Meanwhile, the EC has thus far declined to comment to share its official reasoning for striking this funding from its budget.
Sigh. It appears that they are chasing after the latest "shiny" thing instead of investing in existing infrastructure. Not surprising, but disappointing.
Not a bad list. Off the top of my head, I would say it is missing two things:
The "Introduction to Operating Systems" link no longer works (redirects to "Autonomous Systems" courses). Instead, I would recommend using Operating Systems: Three Easy Pieces, which is the textbook I use in my OS course.
Finally, something like The Missing Semester of Your CS Education would also be a nice extra.
And that's exactly what happened in your case David. Which is why I'm so happy (also because I fixed the tools from an author I like and already had the books at home :-P):
Really detailed and cool response from the kernel developer. I also found the use of the recent BPF feature to provide a workaround until a proper kernel fix lands really interesting.
Would to see them publish stable releases via this apt repository as well.
No word on how long it will get software support though. With everyone else going to 5 or 7 years of updates, Motorola's typical 2 year support cycle is a huge negative.
I wish they had a mastodon account... they have https://mozilla.social, but they don't have an account there... which is bizarre.
They do have an account for Firefox Nightly and Firefox Dev Tools account though.
Headline is a bit misleading... This is just Tails updating to the latest LTS kernel, which has the security fix (which many other distributions have done).
This update is a good thing, but the headline made it sound like the Tails project was contributing a fix to the kernel.
Anyway, thanks for sharing.
Currently self-hosting my own mastodon server and honestly the setup wasn't too bad (using docker)... much more straight-forward than I feared.
My main concerns, which Julia mentions, is that if you have a small instance, you are very much an island as the way federation work is not what you expect. For instance, as Julia notes, if you view a new person's profile on your own instance, it will look empty (as if they haven't posted anything). Lemmy also has this issue if you view a community you have not subscribed to yet for the first time.
Likewise, my "#explore" tab is basically always empty and discovering new tags or people is difficult if you are just looking on your own instance (I basically have to go to Fossotodon or another instance to find new things and then import them into my own instance). I've recently learned that you have to have a third party application basically seed your instance with posts... again, similar to the bot tricks use for seeding Lemmy with communities.
Overall, I think discovery is a big pain point for the fediverse and ActivityPub. It's great that we can have our own instances and control our own small communities, but it seems that we are lacking the ability to really connect across instances and form experiences that really bridge across multiple communities.
I wonder if it is because of the various outages on both instance and the new "dead instance" detection, lemmy.ml has temporarily stopped receiving updates?
The federation code now includes a check for dead instances which is used when sending activities. This helps to reduce the amount of outgoing POST requests, and also reduce server load.
Still using mutt after two decades (with isync for fetching).