Yes, seems you are right. Not sure where I got the impression.

Unrelated, when I researched this I saw that acme.sh, zerossl, and a bunch of other acme clients are owned by the same entity, “Stack Holdings”/“apilayer.com”. According to this, zerossl also has some limitations over letsencrypt in account requirements and limits on free certificates.

By using ZeroSSL’s ACME feature, you will be able to generate an unlimited amount of 90-day SSL certificates at no charge, also supporting multi-domain certificates and wildcards. Each certificate you create will be stored in your ZeroSSL account.

It is suspicious that they impose so many restrictions then waive most on the acme api, where they presumably could not compete otherwise. On their gui they allow only 3 certificates and don’t allow multi-domain at all. Then even in the acme client they somehow push an account into the process.

[…] for using our ACME service you have to create and use EAB (External Account Binding) credentials within your ZeroSSL dashboard.

EAB credentials are limited to a maximum per user/per day. [This might be for creating them, not uses per credential, unsure how to interpret this.]

This all does make me slightly worry this block around apilayer.com will fall before letsencrypt does.

Other than letsencrypt and zerossl, this page also lists no other full equivalents for what letsencrypt does.

They don’t offer wildcard certs, but otherwise I think they are.
I wanna say acme.sh defaults to them.

What for? What did they do?

Unrealistic

᠎

per minute watched

Per started minute

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?

The new page has a clear section for north korea, and lists wars newer than the ugandan bush war for it.
To me it seems more like someone noticed the original page was severely behind and decided to therefore merge it into the korea article, since apparently noone was maintaining it otherwise.

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

There is a sub for sanity checking mod actions, aita-style.
If you keep in mind it is for active unconfirmed situations, and that votes there are not meant to mark the cases of mod abuse, I think it can fill that niche.

!yepowertrippinbastards@lemmy.dbzer0.com

Two half-size batteries for the price of three full-size phones coming right up

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.