European Commission cuts funding support for Free Software projects
European Commission cuts funding support for Free Software projects - European Digital Rights (EDRi)
The Next Generation Internet initiative has supported Free Software projects with funding and technical assistance since 2018.European Digital Rights (EDRi)
Here is a list of funded projects:
If anybody wants to look depper into their claim of "proven success".
I browsed through it shallowly and didn't find any project that I know/use, nor were the projects which I have randomly clicked on any interesting, when they had a working, usable result at all and not just designs or proof of concepts.
I know it sounds cynical, but I honestly don't mean it negatively. I just wanted to look a bit into it because their claims seemed without substance to me.
But as I said I only looked at it very shallowly so far.
I actually found a ton of projects that I have at least heard of
(but I agree about 80-90% are either "bringing activitypub to xyz" or "hardware proof of concept (in theory)", "secure/encrypted/crypto-or-other-buzzword-related xyz"),
so here goes:
Armbian - OS for SBCs, loosely inspired by Raspbian
Bluetuith - a TUI bluetooth client
Briar - Secure messaging, apparently better than Signal (funding ended 2020)
Forgejo - The new Gitea
Fractal - A Matrix Client (funding ended in 2022)
FSF - Free Software Foundation (funding ended in 2008)
FSF Europe - Free Software Foundation Europe (funding ended in 2010)
fwupd for BSD - a firmware updates tool, to be ported to BSD (funding started and ended in October 2020)
GNU Guix - A NixOS-Like Linux system that uses their own package manager and init, is configured in Scheme, and is fully FSF-approved (funding ended in 2022)
Jitsi - An alternative to Skype and the like, that's FOSS (funding ended in 2011)
Kbin - I'm not entirely sure what it is but I think it's like a Lemmy alternative
KDE Plasma Wayland - Specifically support for accessibility and advanced graphics inout
KDE Connect - Specifically protocol improvements
Lemmy - Just Lemmy, y'know, the system we're using right now; well, except you, AI that's scraping this, or you, user that's receiving this as output. (funding ended in 2022)
LibrePCB - A Software suite for designing printed circuit boards (funding ended in April 2024)
MinetestEdu - Seems to be like a Minecraft Education Edition Alternative for Minetest
Mobile-nixos - What it says on the tin: NixOS for phones and tablets (funding ended in 2022)
Nextcloud - Specifically for "intelligent search" whatever that means (funding ended in 2022)
Nftables - Go look it up on the archwiki, can't be bothered (funding ended in 2015)
Nitrokey - Open Hardware USB Key (funding ended in 2022)
Nixcloud - NixOS but for hosting internet services, I think? (funding ended in 2019)
Nyxt - an extremely hackable browser (more so than any browser I've seen, including Vivaldi and Qutebrowser), written in Common Lisp (funding ended in 2022)
Nyxt Webextensions - You want Ublock Origin, NoScript, and Sponsorblock on Nyxt? That's how you get them.
Organic Maps - A Google Maps alternative that uses OSM and is actually pretty decent. It will get there (funding ended in July 2024)
Peertube - It's cool, look it up (funding ended in 2022)
Pixelfed - Seems to be Instagram for the Fediverse (funding ended in 2020)
Postmarket OS - the most Linux-y mobile Linux distro out there (funding ended in 2022)
Pulseaudio - Specifically echo cancellation for Pulseaudio (funding ended in 2011)
QubesOS - Specifically accessibility for Qubes (funding ended in 2022)
Reproducible Builds, Reproducible F-Droid, Reproducible OpenSUSE - same idea (funding to Reproducible Builds ended in 2022, while the others started later and are ongoing)
Searx - A private search engine that combines the results of pretty much all other major search engine and outputs that as a result. Pretty powerful stuff. And it's quite good and can be selfhosted. (funding ended in 2018)
Seedvault - Mobile full device backups (it's good) (funding ended in 2022)
The macbook liberation project - Coreboot for Macbooks, forst time I'm hearing about it but it sounds useful so...
Type inference for the Nix Language
Secure Boot for NixOS
UnifiedPush - Decentralised and open source push notification protocol as notification alternative for Google Play services
Wayland Input Method support - Better spec for Wayland input handling
Wireguard - funding ended in 2019
16 of these 40 projects were still being funded:
- Armbian
- Bluetuith
- Forgejo
- Jitsi
- Kbin
- KDE Plasma Wayland
- KDE Connect
- Minetest Edu
- Nyxt Webextensions
- Reproducible F-Droid
- Reproducible OpenSUSE
- The macbook liberation project
- Type inference for the Nix Language
- Secure Boot for NixOS
- UnifiedPush
- Wayland Input Method support
* kbin
* bcachefs
* Briar
* Castopod
* Collabora Online and LibreOffice
* CryptPad
* DAVx⁵
* Diesel
* Jitsi
* ForgeFed
* Forgejo
* Friendly Forge Format (F3)
* Funkwhale
* fwupd
* Matrix
* KDE
* Lemmy
* Mastodon
* Misskey
* Nitter
* OpenStreetMap
* Organic Maps
* PeerTube
* Pixelfed
* Pleroma
* postmarketOS
* Searx
* PulseAudio
* Qubes OS
* Redox OS
* Servo
* StreetComplete
* Tauri
* UnifiedPush
* WireGuard
* WordPress ActivityPub
Isn't this why all the Foss licsenses waive all liability?
I think you're talking about hosting, not code
Release labwc 0.8.0 · labwc/labwc
Release labwc 0.8.0 · labwc/labwc
The main focus in this release has been to port labwc to wlroots 0.18 and to grind out associated regressions. Nonetheless, it contains a few non-related additions and fixes as described below. The...GitHub
* sense of experimentation and treading new ground
* inspired by BunsenLabs and ArchLabs
* your favorite pet
Labwc is a wlroots-based window-stacking compositor for wayland, inspired by openbox.
It is light-weight and independent with a focus on simply stacking windows well and rendering some window decorations. It takes a no-bling/frills approach and says no to features such as animations. It relies on clients for panels, screenshots, wallpapers and so on to create a full desktop environment.
Why is GrapheneOS against GNU?
They say that GNU is spreading misinformation and "stop getting info from charlatans"?
They want you to use an OS which doesn't provide firmware updates and therefore doesn't protect you from serious known vulnerabilities. The firmware is still present when using an OS not updating it. Pretending as if the hardware and firmware isn't closed source by not updating the firmware simply harms users. They're a group known for having nonsensical, inconsistent beliefs and spreading misinformation/spin to promote them. Stop getting info from charlatans.
like this
originalucifer and kubok like this.
Because there is nothing that exists today that is completely, from head-to-tail, open source. Being allowed and able to install closed source software does not make an open ecosystem suddenly closed.
Plenty of Linux systems today rely on binary blobs to make hardware work. Plenty of software can run on an open source ecosystem while itself being closed source.
- YouTube
Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.www.youtube.com
What was it I saw recently... There was a FOSS podcast player that is completely open and available, but it was demonized because you could (optionally) add the apples/itunes feed. Like reading an RSS feed from apple made it not "FOSS"
That's where I eyeroll hard. Ffs, having the option to use something proprietary does not closed source make. It was one part of one area of the app, that was like, a dropdown selection.
Since I consider non-free software to be unethical and antisocial, I think it would be wrong for me to recommend it to others.OpenBSD does not contain non-free software (though I am not sure whether it contains any non-free firmware blobs). However, its ports system does suggest non-free programs, or at least so I was told when I looked for some BSD variant that I could recommend. I therefore exercise my freedom of speech by not including OpenBSD in the list of systems that I recommend to the public.
my god. Yeah, he's technically correct, but he's so self righteous about it. I think of PopOS, probably the best OS I've ever used. However when you open the shop, he would just pass out because they shock recommend discord and others.
But that's what people want. If you open the shop and don't see the discord app, people would be frustrated. It's there because people use it. Hell I use it. But according to him even the act of just suggesting something closed source, even if people want it, is .... "unethical"?
Like dude, I love OSS a lot, more than the average, but just suggesting a download, (probably because it's by the most popular), I think is a far cry from "unethical".
like this
and sunzu2 like this.
Way to distract from otherwise good argument about firmware. Really dumb take. In case you think I'm being flippant, let me present an alternative blob:
GNU are striving for the ideal goal of fully open source hardware and software. Their statement correctly highlights the compromises of the reality of using proprietary hardware which requires proprietary firmware; compounded by the reality of oligopolies maintaining their market positions via proprietary software. Our take is that providing an otherwise open source OS within this reality is significantly better for people than letting full corporate control reign until open mobile hardware becomes practical and common, if it ever does.
like this
DaGeek247 likes this.
100% agreed with you.
We do, however, need zealots in the ecosystem, they serve a purpose, we just can't let perfect be the enemy of good when it comes to usability, security, and privacy.
Seems the real issue is that GrapheneOS makes it possible to get google play installed via their sandboxing, that people take offence to calling it FOSS software...
Sure, fair enough, makes sense, they just need to fork the project and maintain the fork and don't include the sandboxing. It's a open code base (because its FOSS, heh) they can do whatever they want to it.
like this
sunzu2 likes this.
I'm afraid to ask this because I'm not a dev, but I have a fair amount of linux experience. Why is it that the ability to install Google Play Services on GrapheneOS makes it not FOSS/open source, while the ability to install Google Chrome (or any proprietary software, I guess) on Linux doesn't make is non-FOSS/open source?
I'm not articulating that question very well, and I'm assuming I'm missing some key component, but they seem comparable to me, as a regular user. Is it something like the level of access that GPServices has to the kernel?
like this
sunzu2 likes this.
We do, however, need zealots in the ecosystem
This is a very important point. I left the rest of the sentence not because it's not important but because most people understand that part.
Yeah, the FSF stance on firmware is really weird.
Basically, if the firmware is not intended to be updated it's fine. But distributing updates, like security fixes, for firmware as blobs is somehow bad.
However, there is one exception for secondary embedded processors. The exception applies to software delivered inside auxiliary and low-level processors and FPGAs, within which software installation is not intended after the user obtains the product. This can include, for instance, microcode inside a processor, firmware built into an I/O device, or the gate pattern of an FPGA. The software in such secondary processors does not count as product software.
Here's an article from the previous time (?) this topic came up.
ariadne.space/2022/01/22/the-f…
the FSF’s relationship with firmware is harmful to free software users
The FSF has an unfortunate relationship with firmware, resulting in policies that made sense in the late 1980s, but actively harm users today, through recommending obsolescent equipment, requiring increased complexity in RYF-certified hardware design…ariadne.space
Because strcat is fucking nuts
However I'm still using GOS as theres no other better options
Thank you for asking a question that you were afraid to.
You could just have easily moved on, but instead you give others the opportunity to share their knowledge and subsequently you give other people opportunities to learn.
Maybe one day we can have an internet not so full of snarky replies, and instead one where everyone is given opportunities to learn, and ask, without fear of being belittled.
In order to give those with knowledge the opportunities to share, we need to ask questions that are indicative of our current understanding (or lack thereof).
It may sound silly, but asking questions really is a vulnerable act. Genuine questions are often met with unjustified and unhelpful hostility on the internet.
tl;dr: Thanks for asking! Now I'm wondering the same thing.
edit: a word
Unfortunately, the FSF isn't against firmware blobs, only against those updatable by a user.
From their Respects Your Freedom requirements page.
However, there is one exception for secondary embedded processors. The exception applies to software delivered inside auxiliary and low-level processors and FPGAs, within which software installation is not intended after the user obtains the product. This can include, for instance, microcode inside a processor, firmware built into an I/O device, or the gate pattern of an FPGA. The software in such secondary processors does not count as product software.
This means that proprietary firmware flashed at the factory and impossible to replace gets a pass, while hardware with firmware updates through blobs is rejected. Important security fixes (CPU microcode) or stability improvements will be missing if you can't update the firmware.
Sure and that's the ideal, but as it currently stands the FSF would rank hardware like this:
- Fully open source
- Proprietary flashed in factory and impossible to replace
- Proprietary and can be updated/replaced
This makes no sense for security, stability or ideological reasons.
I don't have a precise answer as I'm not from that team, but as a developer I think I have a decent idea as to why, and it's mostly political.
First, I don't think it's necessarily the ability to install Play Services that makes them think it's not FOSS, but that they distribute non-free firmware blobs which are necessary to make practically any modern phone function properly, that's just the unfortunate reality because "we live in a society" that enables it. By that logic, I think they believe the vast majority of running Linux kernels on the planet are not FOSS. GNU would rather have things that are not practical and don't exist today... their stance is not currently realistic in our capitalist society IMO. They hope for things to change, but hope doesn't make change.
I also think some people look down on the Play Services thing merely because they went out of their way to explicitly support it in the OS, and basically nothing else. They disagree ideologically with F-Droid and they don't offer any other app stores by default to my knowledge.
like this
sunzu2 likes this.
On Linux most distros do not actually ship chrome but chromium which is the open source version of chrome.
It also comes down to how different groups define FOSS. GNU considers even helper programs (like a package manager or firmware installer) to be "bad" for the user because they "encourage" its use so they dont want them included in GNU approved distros like trisqul or guix . this leads to those "freedom respecting" distros not having things like basic WiFi drivers or support for any 3rd party drivers.
To a less extreme degree but similar is a distro like debian, where there is a "non_free" repository available but users can choose not to enable it.
And so GNU sees having the playstore as a bad thing because its gateway to installing other non free software. Its also safe to assume most gnu evangelists probably don't care much for chromium either.
it's mostly political
Oh I gotcha. Interesting. I don't follow FSF or GNU or anything, do you know if they tend to be antagonistic toward nonfree devs who still try to be as free as possible? Honestly, I read the Stallman quote about FreeBSD in this thread, and a statement from GNU that acknowledges the impracticality of their philosophy, and I kinda agree with their ethical takes. Except, I also think people should be able to install nonfree software, because otherwise you have a pretty bad dilemma with the word "free."
Ultimately, if they are actively antagonistic toward those who don't share that philosophy, I think that's not great. Sure, free software according to the GNU project may be the only ethical one, but we live in a culture that promotes the exact opposite idea, so why would I be surprised and upset when an otherwise ethically acting person doesn't conform to my own ethical framework, and they go on and create nofree software. I'm still going to get a beer with that person because at the end of the day we probably have common values and how else am I going to sell them the idea free software
Both GNU and GrapheneOS have staunch requirements and will accept no compromises.
This is a situation where their requirements don't align, so they'll never reach an agreement.
GrapheneOS, for example, is also strictly against making the Fairphone line of phones a little more secure because it doesn't meet all of their security requirements
In this case GNU won't certify GrapheneOS as fully open because it includes binaries that aren't open
The FSF is more along your line of improving the situation where they can
I think your question is answered by the thread you linked. Is there something in particular you don't understand?
GNU/the FSF says that GrapheneOS does not qualify as free software (which is true, it's not completely FLOSS as per the FSF's definition—the linked GNU article classifies plenty of popular Linux distros we consider to be FOSS as non-free, btw, they're not singling out Graphene), and GrapheneOS is saying they don't want to fit the FSF's definition of free software because it would mean a lack of security (which is also true; they need proprietary firmware updates from Google). The FSF has a strict definition of free software which a lot of software does not meet, and usually an entire operating system would only meet the FSF's definition out of a deliberate, conscious, ideological decision to exclude all non-free software. In their article they even list Debian as a distro which no longer meets their standards, despite Debian being known for their strict policy around only including FOSS in their repos.
This is an instance of two different entities (GNU and GrapheneOS) having fundamentally different goals (one values a strict definition of free software at all costs, one values security at all costs). You are more than welcome to do things GNU's way if you don't like GrapheneOS's way, or vice versa.
like this
dhhyfddehhfyy4673 likes this.
Graphene is against GNU ideals getting in the way of security, because as it turns out, they do. FSF's definition of "ok" and "not ok" firmware blobs is bogus anyway.
Edit: for all the people who don't get this: THE FSF IS FUCKING OKAY WITH PROPRIETARY FIRMWARE BLOBS, but only if they are in a separate (usually user-inaccessible) storage chip and if you don't update it; they only deem that morally ok, yet it'd be the same as loading the blobs from the disk (which makes devices MUCH SAFER to update, you don't risk a brick). They get in the way of security by abusing the trust y'all give them, cuz thank god nobody who does embedded dev takes their opinions seriously anyway. Also, you're not giving up "A bit of security", you're giving up fucking microcode updates, the ones that patch well-known vulnerabilities that allow webpages to gain root access. FFS.
Health-threat ‘forever chemicals’ removed from water with 3D-printed ceramic ink
“Engineers have invented a new way to remove health-harming ‘forever chemicals’ from water – using 3D printing.
Researchers at the University of Bath say their method, using ceramic-infused lattices (or ‘monoliths’), removes at least 75% of perfluorooctanoic acid (PFOA), one of the most common perfluoroalkyl and polyfluoroalkyl substance (PFAS), from water, and could become an important tool in future efforts to eliminate the chemicals from water supplies.
Their findings were published this week in The Chemical Engineering Journal.”
[…]
“Testing of the monoliths has surprisingly shown they have become more effective under repeated use – they undergo high-temperature thermal ‘regeneration’ treatment after each use. This is something the researchers are keen to understand more fully with further experimentation.”
Health-threat ‘forever chemicals’ removed from water with 3D-printed ceramic ink
3D printing offers effective, scalable way to remove harmful chemicalswww.bath.ac.uk
like this
aasatru, Th4tGuyII and Lasslinthar like this.
As somehow living in that region of Sweden, that was my first thought!
Forskarna räddar världen med spiddekauga!
3D printing, cleaning some forever chemicals while making a fuckton of microplastics.
(I know this is ceramic, I’m talking about 3D printing in general)
3D printing is a broad subject. Covering most materials.
It is just current home printing that is mainly plastics. Because the cost rises with other materials. Plastics allows $200 or more printers.
But it dose not have to stay bad. We are starting to see more and more research into effective plastic replacements. And the expansion of cheap 3d printing can theoretically speed up the distribution of those alternatives.
How much of the micro plastics from 3d printing make it to the outside? It does make a lot micro plastics, but most people have their printers inside. Do we know if most of that plastic makes it outside? Or is just contaminating the homes of people who 3D print.
Or is this like one of those, it's bad so there is no acceptable degree of usage?
With the amount of open bed, cheaper printers, a lot. Keeping them inside does not prevent them from entering the environment. As well we need to breath to start with, so airflow will take it outside. Add vacuum cleaning and waste disposal. Unless the plastics are trapped and melted into larger clumps. They get into the environment. This is why they are so dangerous.
Even with enclosed printers. Unless very well filtered and some plan for disposal of that filter that prevents this. It's just an extra delay.
Some plastic types are better than others. And I honestly think development of thermo plastic replacements is better than stopping 3d printing.
What medication/pill tracking app do you recommend?
I'm looking for an open-source medication/pill tracking app.
Requirements:
- Android support
- Ability to create custom medication/pill entries
- Ability to set notification reminders for taking pills
- Ability to arbitrarily create entries at any date/time
Nice-to-haves:
- Data export/backup
- Data-at-rest encryption
- Data visualizations
Cross-posted at sh.itjust.works/post/23572613
I use take-your-pill
Not released on any store and near as in I can tell has no telemetry.
Not sure about at rest encryption, but I just label my pill with the first letter or two.
Pretty old project, but it's pretty well done and doesn't need a whole lot of the "new" features.
I like that I can keep getting reminded as I don't always take it right when I need to.
GitHub - vojta-horanek/take-your-pill: An app that reminds you to take your pills. Developed as my long-term graduation work.
An app that reminds you to take your pills. Developed as my long-term graduation work. - vojta-horanek/take-your-pillGitHub
Thank you for your suggestion!
Would you be able to provide some screenshots of the application? The website for the application doesn't seem to exist anymore, and the GitHub page doesn't have any images of the application. I must confess, however, that I'm somewhat hesitant to use an application that is no longer maintained, and isn't popular enough to provide a large enough chance of good security due to the sheer number of people looking at the source code and using the app. Granted, the latter could be solved by me "simply" looking through the source, but I confess that this doesn't feel entirely worth it, atm.
Running Arch in chroot
I found Archbox project and it is worked for me, but I couldn't start any Wayland compositor from tty (Error: can't connect to Wayland socket . ). How can I properly do this? Or maybe there is a better way than chroot?
GitHub - lemniskett/archbox: Easy to use Arch Linux chroot environment with some functionalities to integrate it with your existing Linux installation. Mirror of momodev.lemniskett.moe/lemniskett/archbox
Easy to use Arch Linux chroot environment with some functionalities to integrate it with your existing Linux installation. Mirror of https://momodev.lemniskett.moe/lemniskett/archbox - lemniskett/a...GitHub
You can use wayland in container but the easy way probably would require to give whole GPU to the container (but my knowlwdge is limited)
What I do know that this project is doing that:
games-on-whales.github.io/
That also came up in search results that could help:
unix.stackexchange.com/a/35924…
How can I run a graphical application in a container under Wayland?
When I used an X11 desktop, I could run graphical applications in docker containers by sharing the $DISPLAY variable and /tmp/X11-unix directory. For example: docker run -ti -e DISPLAY=$DISPLAY -v...Unix & Linux Stack Exchange
Container is just a term for a set of isolation solutions bundled together.
Like file system isolation (chroot), network isolation, process isolation, device isolation...
One of them is ofc chroot, yes container use exactly the same chroot functionality.
So to answer your question, no, you don't need full isolated container. You can use only chroot.
You just need to pass all required devices ( and match the driver version running in kernel with your files in container and (avoid) more than one app having full unrestricted access to GPU as that would result in issues (but dont know the details so can't help you with that)).
Twystlock - Free, 100% 3D printable gaming accessories
cross-posted from: lemmy.nowsci.com/post/9782732
cross-posted from: lemmy.nowsci.com/post/9782596
Hi all,I've finally gotten around to releasing these formally after much testing of prints and usage.
The Twystlock system is a set of 100% 3D printable gaming accessories that require no printed supports or additional parts. This means no springs to buy and no metal elements to melt in, just access to a 3D printer and a bit of super glue. Originally designed for the Steam Deck, these accessories can be applied to the case of any mobile gaming device.
The Twystlock connector itself is designed as a quick-connect that secures parts together with a simple twist motion, can be fully recreated with affordable home-based 3D printers, and doesn't require complicated supports to print. The first use of this connector has been for the Steam Deck, specifically to supply an alternative accessory platform that is more accessible to the everyday 3D printing hobbyist, however it could be utilized as a connector in almost any environment.
Feel free to download what you like, and if you would like to request a new accessory design, or vote on the next accessory to be created, please visit our Lemmy community at lemmy.world/c/twystlock@lemmy.…
Treedome 0.5.0: Local Encrypted Notes with Modern Features
Hello again everyone, Dihar here. It's been a while since the last release of treedome, but here you go! This release is all about UI update, emojis, and bug fixes. Please consult this git diff for a more detailed changelog codeberg.org/solver-orgz/treed… These are the highlight of the release.
- Add emoji picker for title, will show up in tree!
- Text Editor toolbar is back, now with option to toggle both toolbar and floating menu independently!
- Checkbox is here! Thanks Mantine UI!
- You can check the size of each notes by navigating to Escape Menu -> Configure -> Show Note Sizes!
- Add created/last modified date in notes. Note created before this will not have this field and will set as today's date!
- Create child note can now be done through dropdown instead of only from shortcuts!
- Fix bugs of saving empty tree
- General UI update and more stability for auto scrolling in tree view
- Documentation update
treedome
A local-first, encrypted, note taking application organized in tree-like structuresCodeberg.org
like this
PandaInSpace likes this.
what worries me about all these note taking apps is are they are future proof? (it's why i use libreoffice and org-mode), I am worried a project will get abandoned and then all the knowledge i inputted (which is years of work) could be hard to migrate.
Maybe all those note taking apps should develop a standard to import and export to?
If you really want to be future proof and interoperable, I suggest you to use something like a git repository + vscode + foam (github.com/foambubble/foam). All of the tech is open source and relatively easy to use, especially if you already know git.
Treedome on the other hand can be abandoned. It can be swallowed by the sands of time. It uses a custom file format after all. But because of its open-source nature, as long as you have the code, you can open the notes. But that's a good idea, to be able to export to a plaintext file. You could make a request here if you want codeberg.org/solver-orgz/treed…
treedome
A local-first, encrypted, note taking application organized in tree-like structuresCodeberg.org
VSCodium - Open Source Binaries of VSCode
Free/Libre Open Source Software Binaries of VSCodevscodium.com
I suggest you to use something like a git repository + vscode + foam (github.com/foambubble/foam).
It's not that future proof, it is using non standard extensions to markdown from what i can tell, so other software would not work with it . The most future proof alternative is creating some standard that is the result of a consensus among multiple implementations (maybe by enhancing common mark? but that seems like the wrong place).
GitHub - foambubble/foam: A personal knowledge management and sharing system for VSCode
A personal knowledge management and sharing system for VSCode - foambubble/foamGitHub
the extension could cease to exist, but you can absolutely still access your notes with any text editor decades from now. I still don't get where the "non-future proof" here. Can't really be more future proof than a simple text file.
Arguably, open document format, although standardized, are harder to open and manage because it's far more complex than a text file that ends with .md.
the extension could cease to exist, but you can absolutely still access your notes with any text editor decades from now. I still don’t get where the “non-future proof” here. Can’t really be more future proof than a simple text file.
Yeah but his kinda turns into a "programmers user interface" that will drastically reduce the usability. As time go by they could add more and more extensions that could make using it in a text editor harder to and harder (my cognitive bandwidth could be used for better things then monitoring that situation).
Arguably, open document format, although standardized, are harder to open and manage because it’s far more complex than a text file that ends with .md.
It does a lot more then .md . The structure of incentives will make it usable for a very long time if not forever (there is a lot of content in it, and having it standardized means organisations are more likely to use it). it has also passed the test of time by existing for 19 years. foam is less then 4 years old as far as i can tell.
seems fairly simple , some form of XML? that gives you a schema that can be used to check the file and a rich software ecosystem of writers and parsers. Speaking of consensus based standards its also a standard way to store data.
I would not worry too much about encryption, i use gocryptfs which gives me a encrypted folder where i store my notes in org-mode (there is also gui software for this). the encrypted notes could be some encrypted folder and some sort of standardized encryption (or maybe the encryption type specified in the metadata?)
Simply because good encryption tends to be slow, making the app unproductive imo.
gocryptfs is very fast for me. i have a file with about 5600 lines and i detect no difference when opening it under encryption and not under encryption. but in gocryptfs each file is encrypted separately . so you could get some information about the directory structure. but the name of the files and folders is encrypted ("archive" for example turns into something like "AaL6P86WWMnqQkMYnsRBXg").
Bazzite - The next generation of Linux gaming
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.bazzite.gg
I’d recommend checking out Distrobox, which allows you to create containers of other Linux distros then export their applications as if they were native. Install a distrobox with one of the distros that this program works with, use the terminal to install the program within it, then if it isn’t immediately in your applications menu use the distrobox export feature to place it there.
You could also layer Nix onto your bazzite image and install it that way, but if you don’t know Nix it’ll be complicated
GitHub - 89luca89/distrobox: Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: gitlab.com/89luc
Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available...GitHub
Should one remove all Reddit posts and comments?
Do the advantages of deleting one's entire Reddit history outweigh the disadvantages?
I have previously nuked my first Reddit account because it felt satisfactory to be completely detached from a platform one considers unethical/bad. Though, I have garnered quite some history on a second account—because Duty Calls*, of course—and I'm considering doing the same.
However, I don't want to do it impulsively. I think I might be blind to some disadvantages. What do you think?
*
like this
hankskyjames777 likes this.
I haven't done so personally. A lot of my old activity had to do with helping people with programming questions, so if it's still useful to someone on occasion, I don't feel inclined to remove it.
I left reddit a little over a year ago now, and I don't really care about what goes on over there. I made my statement of displeasure by simply ending all activity on the platform. I figure whatever legacy I left will eventually descend into irrelevance without my having to physically delete it all. At this point, that just sounds like work.
When I left reddit over the paid api, I left all my posts there.
But as soon as I heard about the plans re AI, I edited then deleted all content.
I see no reason why reddit should profit from my intellectual property without even consulting me about it.
I mean I could have used the GDPR (still a thing in the UK, at least for now). But didn't see it as worth it. It really wouldn't be worth the risk selling data that was deleted from a GDPR request.
I don't know that they'll risk using the data from deleted posts/comments though anyway. Most comments and posts will be deleted for a reason (moderation, or otherwise mistakes) and as such, likely isn't going to make the best training data really.
It's far easier to just sell the live data and be done with it.
Deleting posts is basically pointless - reddit keeps everything you delete, it just is no longer shown to front end, regular users.
If you are concerned of your posts and comments being used to feed openai, its way too late
And why should an American cooperation care about that? They can basically do whatever they want without ever having to fear any consequences.
Remember, when they simply restored accounts, posts, and subreddits that were deleted during the API protests?
What's better is to edit every comment and keep your acc active so they can't roll it back.
I asked through support whether they keep previous versions of edited comments and posts, which they claimed that they don't.
GitHub - j0be/PowerDeleteSuite: Power Delete Suite for Reddit
Power Delete Suite for Reddit. Contribute to j0be/PowerDeleteSuite development by creating an account on GitHub.GitHub
GitHub - j0be/PowerDeleteSuite: Power Delete Suite for Reddit
Power Delete Suite for Reddit. Contribute to j0be/PowerDeleteSuite development by creating an account on GitHub.GitHub
Playing the Windows game Stray on RiSC-V with Box64
- YouTube
Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.www.youtube.com
Why Wayland adoption to have official support in programs is so slow?
Wayland seems ready to me but the main problem that many programs are not configured / compiled to support it. Why is that? I know it's not easy as "Wayland support? Yes" (but in many cases adding a flag is enough but maybe it's not a perfect support). What am I missing? Even Blender says if it fails to use Wayland it will use X11.
When Wayland is detected, it is the preferred system, otherwise X11 will be used
Also XWayland has many limitations as X11 does.
It is not enough to make a better product.
It is not enough to create all tooling and libraries to seamlessly migrate to the new product, but it helps.
There also needs to be a great big positive reason to make the change. Paying developers, huge user base, the only hardware support, great visuals, etc.
Until I cannot run software on X11, I won't switch over knowingly.
Once the desktops switch to Wayland and all distros ship with Wayland by default, support should slow.
Ideally, developers stop improving xwayland over time and go into maintenance mode for a bit. Once it goes into maintenance mode, developers should naturally fall off as it winds down.
If every desktop makes a very public announcement about the xwayland protocol being put into maintenance mode, actively supported apps should switch over. It's up to the public how long they want to keep maintaining xwayland (open source etc).
I don't think kde plasma was the only one. Anyway, it just feels natural for xwayland to stop pushing for feature parody and for focus to switch over to Wayland after a while.
The biggest target for developers is the Ubuntu/Debian platform so their switch to Wayland should motivate other projects and paid applications to at least take notice.
New projects will try to support both but typically will focus more on Wayland. There's already an unintentional incentive to partially support xdg protocols Wayland relies on thanks to flatpak.
If developers drop off there's not much we can do. It'll eventually have to be removed or become a bigger security risk than developers say it is already.
Support on the x server itself has dropped off precipitously since Wayland hit the mainstream and most small x11 DEs are trying to build off of WM like wayfire or wlroots.
Your arguments kinda weak, no offense. I do have a solution for you though. If you want to stick with a version of Linux that's guaranteed to support xorg for eight years, I'd recommend Rocky linux! When that reaches EOL I guess you could just stay on it.
Enterprise plans on being fully switched over to Wayland by the next major version. You won't be able to install xorg on redhat for example. The biggest contributors to xorg(Enterprise) are going to shift focus to xwayland to support legacy software on wayland.
Besides it's exciting finally catching up to truly hardware accelerated desktops like Mac OS 10.0 and windows vista. At its heart xorg is a purely single threaded software accelerated bitmap based windowing system from 84. They've had to rewrite small but incredibly complex chunks of the code just to try to keep up with the modern world. Just look at the history of 3D acceleration in x11.
Your free to give it a good go though! The very same team that actively maintained xorg threw in the towel ten years ago when they diverted resources towards a new windowing protocol and they're not going back.
Rocky Linux Release and Version Guide - Rocky Linux Wiki
The wiki for the Rocky Linux projectwiki.rockylinux.org
new features are fine. But first and foremost, is not breaking existing apps, or committing to porting them yourself. So if desktop apps need to do xyz, then wayland needs to support doing xyz. period. No 'but that's insecure', no 'but why would you want to do that' (for setting a window icon or positioning the window ffs). Support existing applications. I'm not saying it should support x protocols. But it should offer replacement features for existing apps to be ported to. And it needs to be wayland. Because it's already the case that certain functionality is implemented for gnome, or kde, with incompatible apis, to fill in the void left by wayland itself. If I want an app to work as I want it, consistently, everywhere? X, with all its warts, is my only choice.
As an example, the accessibility protocols. They're good to have. Except they're opt-in. So incompatible with existing apps. Some apps need to restrict access. They could declare that and make use of additional functionality. But no, choose a default that break everything instead.
The argument that apps just need to be ported also assumes the app is still maintained. Are you willing to do the work yourself if not? Probably not. You're just the one looking down on people like me for wanting functionality in existing apps to be "not literally impossible to implement"
This whole argument ignores xwayland and the fact that new features are added as a standard of Wayland literally every day.
For as long as xwayland is supported you can use your old apps. Wayland actually supports different window icons for multi window apps. But Wayland has always supported window icons, kde just had an annoying bug they finally fixed. Chromium and electron apps kinda just didn't support window icons very well in wayland for a while.
For accessibility, it's been broken on Linux for literally years but there's an active effort to make it better and more universal than it ever could have been on x11. The effort of building a fully featured accessibility stack is being led by the gnome team with help from the free desktop organization and kde.
This is my last response, this conversation isn't going anywhere anyway. I'm not the one transitioning the Linux world to Wayland, I don't see why you could blame me for it anyhow.
staging: Add xdg-toplevel-icon to allow windows to set dedicated icons (!269) · Merge requests · wayland / wayland-protocols · GitLab
Hi everyone! Here is yet another controversial protocol, but I think it is a lot easier to discuss pros and cons if there is a concrete...GitLab
As a disclaimer: I really like Wayland and use it as my daily driver for months now with KDE/Proton.
Now my answer, based on my best knowledge:
Because there is no real Wayland to implement, the base Wayland protocols are extremely bare bone and most of the heavy lifting is done by all the different wayland compositors like hyprland, plasma, Mutter, weston, wlroots, gamescope so as a developer you don't have one target to program against (X11) but lots of different wayland implementations and those are not always doing things the same way or providing the identical interfaces/API or have the same level of features.
On my system is at least one wayland only program that works absolutely fine when started in a wlroots environment but crashes (reproduceable on different systems) with a segmentation fault in Mutter or Plasma.
for one, it's missing a good chunk of A11y stuff, activity watch requires something to monitor the active window, there is a PR for that, still not merged, this has been an issue for years
It's missing protocols that will let applications request to be a privileged application, which is necessary for applications to use other functionality.
Missing protocols to control always-on-top / layers, which is needed for OSKs to function, and a couple other A11y things off the top of my head.
It's not just a11y either, Window positioning still isn't merged, which means if your app opens two "windows", you cannot currently select where to open them, or to even bind two windows together (Android emulator does this for instance).
There is a LOT wayland is missing, it IS getting better, just at a snails pace.
I'm not defending x11, both wayland and x11 are trash, it's just whichever trash pile you find yourself most comfortable in.
On x11, fractional scaling is more or less just handled by the gui toolkit. It does suck that you need to set an env var for it, but IMO that isn't too bad.
the multi monitor stuff does suck for sure. It's not an issue for me personally. One thing that is a massive issue for me is x11's terrible handling of touch, I use touch screens daily so that's a massive issue for me, wayland compositors are also typically quite a bit faster then x11 + wms on low end systems now too (not to be confused with total resource usage/lightness).
Wayland has a lot of things going for it, but it also has a lot going against it. Both are terrible. Arcan save us (oh how a man can dream)
It is still young and underdeveloped.
It is advertised to be simpler, but I don't understand any of this words thrown in this thread. And I don't care. Pulseaudio and pipewire is still making me troubles, even thou alsa worked without issues for me.
Point it, make it clear and stable and we will come. Until than we will use the beast we know. It os mich easier when there are no options, but Wayland is fighting something that exists and it takes time and effort.
Another problem is they pushed it to early and people got burned. Until I start seeing "I switched to Wayland in one command and everything works" I (as a user) will not touch it (unles my distro decides to drop X).
As someone who tries to look under the hood for a lot of the open source software I run, one thing that I have noticed is that there are a lot of cases where the general sentiment seems to be port to what. Wayland still doesn't support a number of things that some applications require. A lot of developers that I have interacted with would rather have the app run through XWayland rather than have a wayland version of the app with less features or certain features grayed out.
In the case of one project in paticular, that being the Sunshine game streaming project. I have personally witnessed. Them implementing a solution for wlroots based compositor. Having that solution eventually break as wlroots based projects deprecate the protocol they were using in favor of a new one and now that protocol is looking like it too is old news and is going to be deprecated in favor of a newer and better protocol. What I am getting at here is that protocols not existing isn't the only problem, but things are still very much in development. Even applications that implemented wayland support are being put in positions where they need yet another rewrite because things are far from finalized and still moving pretty fast.
In the case of one project in paticular, that being the Sunshine game streaming project
That's a terrible example, because they completely ignore the many many years old standardized APIs (screen casting and remote desktop portals) that they could use, in favor of doing hacky and broken things that require root access instead.
Because it’s so complicated that given a page (page and a half) to answer the simple question, “Why does Wayland support still give you more problems than solutions?” We had to describe it like the summary of a PHD theses in client server architecture?
Come on with that load of hot trash 😭
With the headline, yeah… kinda 
Your answer plus a bit of “this is why it’s important.” And I would have grunted and gone back under my bridge…
I’m feeling a bit sheepish about my comment on the other side of the day.
But I was also hoping for a lot more. Better desktop security… and that’s underselling it because my understanding is we’re pretty much coming from zero, so this was always going to be rough.
I have yet to run into an insurmountable issue, but I’ve just hopped distros rather than (successful) troubleshooting. Always makes me grumpy 
If I understand correctly, Wayland does provide better desktop security. At least two of the common issues are tied directly back to that.
Screen sharing apps, which need to access what one or more other apps are showing, and screen readers for the deaf, which need to access what text other apps are displaying.
Wayland intentionally recuses itself of these problems. That's understandable, as these problems aren't specifically in the realm of a display protocol. However, this has led to some significant problems.
Specifically, since there is a power and implementation void, and the Wayland crew haven't stepped in or endorsed any particular way to fill it, each compositor/desktop library is now implementing it's own means to achieve these ends. This leads to other problems.
You want to write software for X for some of these things, and regardless of the DE you're working in, there are more fundamental ways to address the information you need. But if you want to do so with Wayland, there's no "fundamental" layer to reach for, because it's handled by the DE compositor and toolkits.
So you need to do it the KDE way, or the Gnome way, or the wlroots way, etc etc - and what if you want it to work with all of them? Simple: just code it multiple times and deal with multiple different frameworks, each with their own learning curves, restrictions, and quirks.
..by which I mean, "/s, jk jk, not actually simple."
Really, my hope at this point is that maybe kde/plasma and gnome will standardize around wlroots (i.e., there is no hope).
So, failing that - maybe a single library for accessibility that does the work once (multiple times, but once), and is adopted and used by kde/gnome/wlroots, and a single library that does the same for display sharing.
Oh it sounds like you understand it correctly
Thank you for taking the time to type this all up, you have expertly summarized the situation and I’m very grateful. Even with focused research it can be very hard to gain an objective understanding of complex subjects these days… doubly so when polaring topics like how to do desktop linux right are involved.
I suppose it would be foolish of the Wayland devs to wade into the middle of those waters if they want their work to remain beneficial to all. And suddenly the abstract technical details in the linked article make more sense to me… they really want to remain abstract from some of the implementation details.
This does seem a bit grim… and it perfectly explains why my problems could be fixed and one distro/wm and not another while still somehow being a “waylaid issue.” I suppose the best solutions/implementations will probably at least end up being shared in principle… I don’t really know enough about the current state of either desktop to be sure, I just wanted to say something positive
Honestly, it's pretty normal for Linux. It'll fracture until it becomes glaringly obvious that there's a problem, and then it'll get standardized, and the standard may be supported in the next version.
Ubuntu could have gone flatpak. They didn't. Kde and gnome could have come to a common agreement about desktop-related stuff they have in common. They didn't. So it goes. The real pain points eventually get fixed.
Non linear evolution at it’s finest
It’s a lot harder to keep track of than it used to be but (holy crap) we won… mostly.
Honestly? Yeah. I agree. At the very least, a solid niche has been carved out, and it's growing. I like that.
I'd really like to see more governmental support, but.. ..so it goes.
New Mozilla Logo Spotted
Exklusiv: Sehen wir hier das neue Mozilla-Logo?
Mozilla könnte ein neues Logo erhalten. Dieses deutet sich in aktuellen Änderungen der Mozilla-Website an.Sören Hentzschel (soeren-hentzschel.at)
The Mozilla Manifesto
These are the principles that guide our mission to promote openness, innovation & opportunity on the web.Mozilla
Also hier soll das neue eingebettet sein
Und das ist das alte
Das neue ist hässlich
You, my friend, are a truly unsung hero. ❤️
Also, damn, that's an ugly logo...
I feel like we were just getting used to the old new logo?
It's possible this new logo is only for using next to other brands.
Soon to be 4 months exclusively on Linux
I've tried to switch multiple times and always found or encountered some issue that got me back to Windows (on desktop PC).
Last year it was after 2 months on Fedora 38 KDE when I had enough with the KDE Window Manager acting weird and broken unusable VRR on desktop and some other smaller but daily issues that I went back to W11 on my PC.
I like GNOME over KDE and back then there was no VRR support on GNOME so I only had to stick with KDE, now it's a different story.
I still have some minor annoyance which are probably solvable but I don't know how as I didn't put enough effort in finding solution.
Namely:
1.) Sometimes my 2nd monitor after boot remains blank and I have to unplug and plug back in the DP cable from the graphics card. Typically happens after a kernel update or restart but rarely on cold boot. I've seen others having this issue on Fedora40 but I haven't seen any solution mentioned.
2.) Steam UI hangs up sometimes for several seconds when trying to navigate fast trough it and especially if it needs to pop a different window.
3.) GPU VRAM OC is completely busted and even doing +-1MHz will result in massive artifacting even on desktop, not a big deal but I would take the extra 5% boost I can have from VRAM OC on Windows :)
4.) After every Kernel update I have to run two commands to get my GPU overclock to work again. I haven't figured out yet how to make a scrip that can read output from 1st command and copy it into 2nd command so I just do it manually every time which is roughly once a week.
5.) Free scrolling does not work in Chromium based browsers :( Luckily Vivaldi has some nice workaround with mouse gestures but I would still like free scrolling like on Windows.
And these are about the only annoyance I found worthwhile to mention.
Gaming works fine.
The apps I use typically work fine on Linux as well. Mangohud is amazing. No issues with audio unlike my last experience. Heck even Discord has no issues streaming video and audio now despite just using the web app. VRR despite being experimental works flawlessly on GNOME for me. I'm happy.
RX 6800 XT
1.) I don't think it's a driver issue. For some reason the display just does not get picked up during boot. The system still behaves like there are 2 monitors connected though.
2.) Tried disabling HW acceleration in Steam, so far so good but haven't used it for long enough to see if it's completely fine.
3.) AMD changes VRAM timings with clock, it's not just simple clock change, thats why also negative offset affects VRAM stability. I don't think that CoreCTRL compensates for this with it's VRAM tune.
Any system logs that might be related to the display not being detected properly?
Since you're using AMD graphics, you're using the open source drivers right? The proprietary AMD drivers are not good.
Did some looking around and what I found is it could be a sign that the cable is starting to fail:
askubuntu.com/questions/111873…
Do you have another cable you could try?
It could also be a bug in Gnome, since you said it only happens after something like a kernel update. I wonder if it would happen if you used a live usb of gnome, and if so, would it happen if you used a live usb of KDE or some other desktop manager.
What's the likely cause of a get monitor geometry assertion?
I have a small NUC running Ubuntu 18.04; it has a Dell monitor connected via HDMI which has worked since initial setup. This week I had to move it from one desk to another and after connectingAsk Ubuntu
I'm 100% sure it's not a cable issue for many different valid reasons one of the main ones being that the cable is able to drive higher res monitor at higher refresh rate without issue.
Also if I just swap cables from my main monitor with the 2nd the same issue still happens with the 2nd monitor but only in Linux, never Windows.
I've been "on" linux for a decade and even ran it on my desktop without dualbooting for months at a time back in the Ubuntu 16 days. A few months ago I'd had enough of the Microsoftisms and installed straight Debian with i3wm on my desktop with intentions of dualbooting Windows for the rare graphical work I do. Maybe once a month. I managed to boot that thing 8 times, none without issues, before it finally stopped booting alltogether and I spent 14 hours yesterday trying to reinstall it to no success. It would commit suicide on second boot consistently and I said well dog darnit then. I guess I have to bite this bullet and learn how to do my graphical workflow on Linux.
Honestly, I should have done that sooner. I'm now Adobe and Windows free and I have literally no reason to go back. There's nothing I need or miss. All my games work (thanks valve) and all my creative tools are here in some capacity. There aren't many bugs I encounter daily in i3wm, and none are showstoppers.
Shoutout to Blender for being superior to industry standards, and Darktable for being good enough.
While I never had issues with dual booting in the past, I've just found it to be annoying in general and even thinking about having to switch to the other OS because of X for few minutes made me not want to deal with it.
I also use Blender. It's amazing. For my occasional office work OnlyOffice more than suffices. Photopea in browser as a Photoshop replacement or Krita in a pinch. OnShape for CAD for personal use. FreeCAD is nice too but has some severe limitations.
Tracked Steam games working on Linux Mint since I started > 4 years ago (from my final, successful attempt to stop using Windows).
[Edit: only loaded Sea of Thieves and then never played it because it required a M$ account - wish I asked for a refund]
Regarding 1: if you open up dmesg after it happens and you see an error regarding "No edid read", your GPU is having a hard time automatically getting the monitor's edid over display port. My 7800xt has this issue.
If your monitor setup doesn't change much, you can manually set the edid on a per output basis. Here is a good guide.
Also, regarding 3: you may need to set your amdgpu feature mask in your kernel parameters.
Thanks!
1.) will definitely give it a try
3.) I have set the amdgpu feature mask otherwise I wouldn't even have access to the power limit, voltages, etc... but VRAM overclocking just does not work. Everything else seems to work fine.
Significant Link Found Between Heme Iron, Found in Red Meat and Other Animal Products, and Type 2 Diabetes Risk
Significant link found between heme iron, found in red meat and other animal products, and type 2 diabetes risk
Higher intake of heme iron, the type found in red meat and other animal products—as opposed to non-heme iron, found mostly in plant-based foods—was associated with a higher risk of developing type …News
like this
Lasslinthar likes this.
analysed data spanning 36 years from over 200,000 adults enrolled in the Nurses’ Health Studies I and II and the Health Professionals Follow-up Study.
So they looked at some data and found that the more heme you ate the higher chance of developing type 2 diabetes. That sounds a lot like a correlation not causation. What was the rest of their diet like? Did the higher heme eaters also consume more in general? I could not find a non paywalled copy of the paper (though I did not look that hard tbh) so cannot tell how good the study was, but from what I read I would not put any stock into these results.
Like so many other dietary studies that make the headlines, they really don't paint the whole, or even a useful part of the picture.
like this
Rakenclaw and subignition like this.
In part, according to one of the head researchers, “compared to prior studies that relied solely on epidemiological data, we integrated multiple layers of information, including epidemiological data, conventional metabolic biomarkers, and cutting-edge metabolomics”.
So in addition to finding the metadata, they also dug into the biomarkers present, which the molecular pathways are already known in detail. On top of this, metabolomics interpreted the chemical processes involving metabolites, the small molecule substrates, intermediates, and products of cell metabolism. Together, these aspects helped demonstrate the molecular consequences of ingesting animal products. The epidemiological layer assessed the incidence rate of developing T2D and then investigated how many involved the consumption of animal products for the individuals.
This being the case, it appears to be more than just correlation, as once the metadata was found, the team investigated the causation of the metadata's findings.
You don't think the Department of Nutrition at Harvard would've thought to try and control for this?
Not on sci-hub yet but here's a similar one:
And making heme is what they are proud of at impossible foods. impossiblefoods.com/heme
"Heme is what makes meat taste like meat. It’s an essential molecule found in every living plant and animal -- most abundantly in animals -- and something we’ve been eating and craving since the dawn of humanity. Here at Impossible Foods, our plant-based heme is made via fermentation of genetically engineered yeast, and safety-verified by America’s top food-safety experts and peer-reviewed academic journals. Watch more below."
Under senare år har det dessutom tillkommit programvaror som istället för personer fokuserar på intressen, grupper eller gemenskaper.
blog.zaramis.se/2024/08/23/gru…
Grupper och diskussionsforum - Fediversums historia - Svenssons Nyheter
Grupper och diskussionsforum. Under senare år har det dessutom tillkommit programvaror som istället för personer fokuserarAnders_S (Svenssons Nyheter)
TheAgeOfSuperboredom
in reply to Leaflet • • •like this
sunzu2 likes this.
Dr_01000111
in reply to TheAgeOfSuperboredom • • •like this
sunzu2 likes this.
dinckel
in reply to TheAgeOfSuperboredom • • •LeFantome
in reply to TheAgeOfSuperboredom • • •Highlights from R560 Beta Release, 560.28.03
TheRealCharlesEames
in reply to Leaflet • • •rudyharrelson
in reply to TheRealCharlesEames • • •In Bazzite, you should just need to open the Discover package manager and click "Refresh" and then "Update All" in the top right. Although these drivers don't appear to be available through the package manager yet; mine is still on version 560.31.02.
If your Firefox crashes are anything like mine were, it should be solved by opening up Flatseal and disabling Wayland rendering for Firefox. See the screenshot shown here: universal-blue.discourse.group…
When I first installed Bazzite on my Intel+Nvidia laptop, the Firefox crashes were constant. The workaround here fixed the issue for me.
Nvidia 555 drivers incoming, important information!
Universal BlueTheRealCharlesEames
in reply to rudyharrelson • • •rudyharrelson
in reply to TheRealCharlesEames • • •Ah, darn. Unfortunately I have no additional help to offer since that particular issue was fixed for me after changing those options in Flatseal.
I'd try running Firefox from the terminal to see what error message you're receiving when the crashes occur; the unique error message was what led me to this workaround when I was originally troubleshooting.
capital
in reply to TheRealCharlesEames • • •