MentalEdge

• Matrix - federated chat server
• Vaultwarden - password vault
• Fireshare - share video clips
• Broadcast-box - host low latency streams

Technically, if you stop updating arch when it’s in a functional state it’ll never break.

I don’t have a static IP, and I just make sure to never ever let my DHCP lease expire. My ISP provides the same IP to the same MAC when renewing the lease. My longest streak on the same IP was three years.

As long as I always turn my router off by cutting the power, it won’t release the lease, so I keep my IP even through reboots. My last one didn’t release the lease at all, so it only ever got a new IP if it was off for over a day, or if I set a new MAC.

When my IP does change, I’ve configured my DNS record to only last an hour. So updating the domain to point to a new IP only takes an hour to update.

Having ideas is generally not enough.

Volunteers don’t take requests. They take suggestions. They only act on the ones they want to.

If you want something to actually get implemented, offering a monetary reward, hiring a dev to contribute, or contributing yourself, is the best way to go.

I’ve gotten several features I wanted into software I use, by adding them myself.

The USs social media user count is at 73% of population, to Germany’s 77%. Smaller difference that I expected, but I did remember correctly, that the US has lower penetration.

USA does have higher time spent online per person though.

It’s pretty much just that there are a lot of Germans.

The population of Germany is about 80 million.

All else being equal, there are 16 times more Germans online than us finns, for example.

Next to the USs 300 million people, that’s still one German about every 5 people. Add to that that Germans are definitely online more than americans, and yeah…

A lot of Germans.

That’s handled by nginx, which strips out the menu items when serving to external IP. Basically serving an html file that doesn’t contain them to begin with.

Yes I did.

I just wrote my own.

It’s a single html file with links to all my services, served at the root of my nginx server.

This is like v12, I’ve edited it over the years as what I host has changed. Adding the embedded searxng bar, as well as links to uptime kuma and openspeedtest.

I’d be happy to let you copy it, provided you know how to edit it for your needs.

Thank fuck.

For now.

I’d like you to realize that “the USA who is the least likely country to implement these laws” is literally the opposite of current reality.

They are making some of the greatest efforts to make legally mandated user and age tracking a thing, as well as legally mandated user identity based content-gating.

…

So this is not a concern to you?

The fact that there are people in leadership positions that want this, and have reasons why they want this, is below note. And not worth opposing?

This will lead to infrastructure, that should not exist, existing.

That it can be avoided is not a solution. It should not be built in the first place.

Is your argument really “this won’t affect linux, so it doesn’t matter” ? At the very least, FOSS development by anyone in California will be a problem, as the law quite literally names “persons” as potentially liable.

The reality remains, the US is the most thirsty for this kind of thing. Not the least.

And they are already working on an even more overreaching version that will close loopholes in the current legalese.

Windows, and any other OS will be illegal in California unless it implements this.

Apple, for one, is headquartered in California.

So, the OS wont work until the user verifies their age somehow.

Moreover, even if an OS somehow could know the users age - that doesn’t automatically mean all other software that exists automatically reads it and responds to it as necessary. Does the law compel anyone making software to recognise this?

Did you not read my comment? Anyone writing software for an OS that implements this, can be sued (in California) if their application ignores the API signals from the OS and allows access to age-restricted content.

Or is your argument really “this won’t affect linux, so it doesn’t matter” ? At the very least, FOSS development by anyone in California will be a problem, as the law quite literally names “persons” as potentially liable.

The reality remains, the US is the most thirsty for this kind of thing. Not the least.

You may want to look into what the legal requirements actually are, and how it changes who is liable. It is outright draconian.

Essentially, it requires the OS to find out the age of the user, and then inform ALL software that is run by API. Any software that theoretically could use the data, and still allows a child to see something they should not have, will be liable.

You claimed that the US was the least likely to do this sort of thing…

Instead, despite the incompetence, they are clearly spearheading this globally along with the UK. Making it most decidedly the first place that will have to deal with this crap.

Not the last.

Not even two weeks later, California is making OS level age verification a thing.

Nice ragebait.

If you genuinely still think that was my point in its entirety, you are truly obtuse.

No.

I’m saying 99.999999999999999999999999999999999999999999999999999999% ≠ 100%

For some people that’s close enough. For some of us it’s not.

Prove otherwise. I dare you. I’m done putting in effort explaining the obvius to you. Your turn.

…

4

Explain to me how they couldn’t. Without simply stating “it’s encrypted”.

On the B2 plan you can use open source solutions like Kopia, and literally look at the code, to KNOW that data is encrypted on your system with keys only you have, before Backblaze ever sees it.

Explain to me, how the personal plan using their closed source application achieves the same.

Linking to a page where they say “it’s secure” is not sufficient. Elaborate. In detail. To at least an equal extent I already have.

…

Sure they can. How else do they enable providing access to the content without the user password?

The data is secured against unauthorized access, but unlike zero-knowledge setups where the chain of custody is fully within user control, the user is not the only one authorized. And even if you are supposed to be, you cannot ensure that you actually are.

OF-FUCKING-COURSE the physical drives, and network traffic are encrypted. That’s how you prevent unauthorized physical access or sniffing of data in-flight. That’s nothing special.

But encryption is not some kind of magic thing that just automatically means anyone who shouldn’t have access to the data, doesn’t.

For that to actually be the case, you need solid opsec and known chain of custody. Ways of doing things that means the data stays encrypted end-to-end.

The personal backup plan doesn’t have that.