boothin

How exactly does that prevent spam, vs just using other existing established verification methods like email validation? If the only goal is preventing spam, its overkill, and other web sites who also have to contend with spam don’t use it.

It’s trivial to create new accounts and emails to verify those accounts. It is not trivial to get a new phone number since virtual numbers are blocked by the verification process.

Neither have sauce in them, they are more akin to a calzone

That’s not what the definition said, realise is just the British spelling. If you re-read the definition in your screenshot, it says both realizes and realises are 3rd person present

there’s an entire wikipedia article for this that makes it super easy https://en.wikipedia.org/wiki/Pirated_movie_release_types

Is it just me or does that “comparison” make no sense for this thread. It’s mostly comparing vaultwarden to the cloud version of bitwarden, not the self hosted version. It only mentions the self hosted version in passing. It doesn’t do anything to help someone choose between vaultwarden and self hosted bitwarden

You didn’t keep your 2fa backup codes like they tell you to do?

kbin and lemmy are different softwares, but they are both used for link aggregation and the 2 softwares use a common protocol, so they can talk to each other. So there are kbin servers and lemmy servers, and they are all interconnected.

So now we can take this post as an example:

You are a user on kbin.social

You posted this question on /m/nostupidquestions@lemmy.world - this means the community you posted on is actually hosted on lemmy.world

lemmy.world then tells other instances that its federated with that someone just made a post on /c/nostupidquestions on its instance. what kbin calls magazines are called communities on lemmy, hence the /c/ instead of the /m/.

kbin.social and all the other instances will then also show this post, even though it originally was created on a different instance

Look into NUT, Network UPS Tools. It runs in a server/client type of set up. You’d install the server onto the device that has the UPS data connected to it. It then monitors the UPS status and can tell all the clients to shutdown when the UPS is running low.