Ofc, no problem.
Since this thread was initially about beginner friendly distros, I wanted to ensure I wasn’t going around recommending an inferior or problematic distro to new users as their first experience.

Wayland and GPU stuff should be very good in endeavor, better than most systems I have seen, better than openSUSE leap and mint certainly. I don’t know fedora however.

Endeavor has its own base repo, but also the regular arch stuff like aur. The AUR is probably the best source for all those programs that are usually missing in your repo, and since the base stuff is stable in endeavor there is no problem if some random program needs a special version or a manual install sometimes, it won’t affect anything else.
The AUR is not the main package source for endeavor.
I don’t know your hardware, but the combination of up to date system components, endeavors focus on just working, and all the shit in the aur (to my understanding flatpak is currently quite useless for drivers) sound like it should just accept any hardware at least as well as other linux distros.

On a sidenote for flatpaks. There is this long running conflict between stability, portability, and security. The old-school package systems are designed to allow updating libraries systemwide, switching-in abi compatible replacements containing fixes. On the other hand, you have appimage, flatpak, …, which bring their own everything and will therefore keep running on old unsafe libraries sometimes for years before the developers of all those specific projects update their projects’ versions of all those libraries.

I see. I have heard a lot of mad things about Manjaro.
In my experience Endeavor is great for less experienced users, and doesn’t really have anything to do with Manjaro.

I’d recommend you give it a try

I think our mistake here was not being alcoholics

Ullr Nordic Libation Peppermint Cinnamon Schnapps Liqueur

Apparently a tool to transport serial connections over the internet, to allow you to run programs making use of them on a separate machine to the one(s) you plugged the serial into.

What is your take on endeavour?

Out of interest, after alsa it was pulse and now it’s turning to pipewire?
What was the standard before ESD?

Yeah that seems about right.

I don’t know how the versioning works for the Android versions here…

Android has the same versions as desktop here, which is why there is no differentiation. The main chunk of firefox is platform independent (and even used in thunderbird too).

So any firefox android app and fork thereof needs that version 131.0.3+ too (unless it is esr which is 128 currently).

173? What happened to firefox versions? We just started the 130s

The offline version is on izzyondroid.
The design is worse, yes.

I don’t think it matters much because most of the time you only see the autofill thing, not the app.
When you do go to the app, it is to select between multiple credentials, which is still a split second action.

On mobile I have my 2fa in a different more convenient app (aegis), though k2a does allow to copy 2fa codes

It doesn’t.
Both DX and K2A-O open a local keepass file.
They are capable of reloading the file when it is changed, and can be set to immediately write out changes to the file.
Then you take whichever file sync tool you like and sync it with all other devices using it. As long as the sync tool can sync files in your internal storage, it will work.

I use syncthing, with a dedicated keepass folder containing only the database file. Then I simply add all my devices to the share and it’ll sync any changes to all other devices. I also have version history enabled for the share.

Keepass2Android Offline also works very well. It has a somewhat different feature set compared to DX.
I found it to be more stable at remaining permanentl unlocked, and DX dropped the 3rd domain level for password matching on either websites or apps, I don’t remember.
On the other hand DX works better for adding new credentials or making changes. Since I usually do that on desktop it doesn’t matter much for me.

They were doing the same on other repos for months.
Both their npm module and android client.
On android they tried to get people to add their own fdroid repo because the official fdroid has not had updates for 3 months due to the license changes.

Edit: Looking at it now compared to 4 days ago, they apparently got frdoid to remove bitwarden entirely from the repo. To me this looks like they are sweeping it under the rug, hiding the change pretending it has always been on their own repo they control.

Next time they try this the mobile app won’t run into issues, the exact issues that this time raised awareness and caused the outcry on the desktop app, which similarly is present in repos with license requirements.

If they were giving up on their plan, wouldn’t they “fix” the android license issue and resume updating fdroid, instead of burning all bridges and dropping it from the repo entirely, still pushing their own ustom repo? Where is the npm license revert?

Also important to note is that they are creating the same license problems in other places.

They broke f-droid builds 3 months ago and try to navigate users to their own repo now. Their own repo ofc not applying foss requirements, because the android app is no longer foss as of 3 months ago. Now the f-droid version is slowly going out of date, which creates a nice security risk for no reason other than their greed.

Apparently they also closed-sourced their “convenient” npm Bitwarden module 2 months ago, using some hard to follow reference to a license file. Previously it was marked GPL3.

It means previous versions remain open, but ownership trumps any license restrictions.
They don’t license the code to themselves, they just have it. And if they want to close source it they can.

GPLv3 and copyleft only work to protect against non-owners doing that. CLA means a project is not strongly open source, the company doing that CLA can rugpull at any time.

The fact a project even has a CLA should be extremely suspect, because this is exactly what you would use that for. To ensure you can harvest contributions and none of those contributers will stand in your way when you later burn the bridges and enshittify.

You could just copy others signed codes, so you would also need some sort of totp system.
Then you could still place some camera capturing and streaming plates of parked cars in real time, so you’d either need 2 way communication with the license plates, where the cameraa tell them to show a code for some specific nonce, and which you could then potentially still stream so would also need severe latency checks, or you would have to get way more reliable gps and make that part of the totp.

which also references an effort to use the media to quietly disseminate Google’s point of view about unionized tech workplaces.

Bogas’ order references an effort by Google executives, including corporate counsel Christina Latta, to “find a ‘respected voice to publish an op-ed outlining what a unionized tech workplace would look like,” and urging employees of Facebook, Microsoft, Amazon, and Google not to unionize.

in an internal message Google human resources director Kara Silverstein told Latta that she liked the idea, “but that it should be done so that there ‘would be no fingerprints and not Google specific.’”

From the article posted by 100_kg_90_de_belin.

Google seemingly does care about their internal image, so they will only make their actions obvious when they fire you for bogus reasons after wanting to join a union.
Quite nasty in that they give you no hints about how extreme their efforts on this are. They monitor internal employee tools like they are cosplaying the NSA, but you wouldn’t know before you are fired out of the blue.

You can compare total better than per user at these scales.
Lemmy needs a certain amount of performance to keep up with federation, but once you have all the images and posts and comments you don’t need second versions until you scale to a size that mandates multiple machines. Which I would guess is more in the 6+ digit user range, where you start averaging requests per second not minute.

In some sense, every lemmy user is a user of your instance via federation. You need to pay the performance for all 100k of us whether your instance has 10 or 10k of those. Local users are just a bit extra demanding on your hosting resources.

I suspect the bias we see here with larger instances paying a bit more (50-ish instead of 10-ish) is more due to reliability and snappyness than actual performance needs too. You tend to get optional smaller-gains pricier perks you might not go for for a smaller instance.

Link is detected without the emoji in my app. You might wanna hardcode the link as https://en.wikipedia.org/wiki/😂
[https://en.wikipedia.org/wiki/😂](https://en.wikipedia.org/wiki/😂)

If you rename a file only changing the casing it doesn’t update properly, you need to rename it to something else and back.
This is so userfriendly I have been stumped by it multiple times.

On the other hand in using Linux I have had a number of problems with the casing of files: The number is 0