I would recommend people not do that unless they know they need to and again, if you know you need to you’re not asking on lemmy.

Hosting your own secrets not only puts the burden of protecting, providing access to and preserving the secrets entirely on you, but puts a very unique set of hosting goals squarely on you as well.

Even a skilled administrator with significant resources at hand would often be better served by simply using bitwarden instead of hosting vaultwarden.

An example I used in another thread about password managers was a disaster. When your local server is inoperable or destroyed and general local network failure makes your cloud accessible backup unreachable, can you access your secrets safely from a public computer at the fire department, church or refugee center?

Bitwarden works well from public computers and there’s a whole guide for doing it as safely as possible on their website.

Privacy from whom?

I ask because the easiest way to do what you’re asking is to have your local record store sell you shit and pay in cash (that you’ve laundered so the serial numbers don’t match the atm). You can even be like “I’m trying to get away from computers man, can you order me this off eBay?” And guaranteed if you spent a hundred bucks or so on used releases they’ll say “absolutely!”

Of course, you’ll stick out like a sore thumb and have a lie to keep up with, so you’ll not have any real measure of anonymity.

I don’t think the ends are those of the cia, and I didn’t say that the means were either, only that they were similar to those in a famous mid century guide for those trying to halt or hijack organizations.

I don’t think the rust devs are a cia opp, before you ask. I think some rust devs and even proponents of rust who only cheer from the sidelines are sometimes behaving in ways that raise red flags. I think it’s natural and laudable that the existing devs and maintainers are alarmed by that same behavior. It’s their job.

I also think Linus position on rust has been stretched to the point of breaking and I personally find it hard to take positions seriously that distill the complex process of integrating new languages into a very old very large codebase with many full time developers into “Linus said I could”.

My understanding is that the rust code in question implemented parts of the c dma interface so that rust programs could use that instead of the c dma interface.

I’m out in the world, not sitting in front of a computer with the source open so that guess will have to do for now.

The most immediate problem with having two different dma interfaces is that now you have two maintainers and an extra step at best when making any changes.

https://lore.kernel.org/lkml/20250108122825.136021-1-abdiel.janulgue@gmail.com/

Here’s the whole thread if you wanna read for yourself.

My take away is that rust people are generally fine and try to abide by the norms of the kernel development process but Martin acts like a jerk and it would be okay if he didn’t come back.

See the comment far, far down in the thread implying that he’s somehow a more serious commenter or developer because he’s funded by donations as opposed to a company.

I wish rust ppl would listen to the maintainers of the 30+ year old c project.

They have decades of experience maintaining and patching contributions made by people who are no longer active and the small request that those contributions be in the language of the project isn’t something to fight against.

It’s really a bummer when skilled developers fall back on stuff like “if shaming on social media doesn’t work, what am I supposed to do?”

Keeping sealed iodine patches and band aids inside my leather wristbands.

Staying on the edge of the pit to catch anyone who falls or takes a hit.

🧷 safetycore 🧷

You can’t use xscreensaver on wayland.

Go get involved and you’ll see pretty quick how people generally handle organizing. They’ll be some kind of low stakes event like a reading or art gallery or concert or something and people will say “come out to this protest tomorrow”.

If there’s a signal or something it’s not usually a necessary link.

All that is to say: don’t use computers to organize. If you want to use social media to raise awareness of an event that’s a different thing altogether.

Please forgive me, as a Debian user I’m prone to senior moments and will soon have my driving license legally revoked.

No social media is decent on privacy.

They’re not private. They’re public. You don’t have the expectation of privacy in public. That’s why people might dress differently walking to the store than they do in their bedrooms.

Social media is an osint treasure trove. It’s lowkey why the idea of osint exists. Don’t expect to have privacy in public spaces like social media and you’ll never be surprised.

This may come as a surprise to you, but lemmy is social media.

小红书 is not private. It’s social media and if what another user said is true then the app version uses plaintext http to transfer data. It’s up to you to determine if that’s a problem for you.

Use a vpn in or around China and your performance might be better. I get a lot of hangs with mullvad us servers.

It’s a nice experience. Check it out if you like.

It went dark after the judicial review process found that the law was constitutional.

The important thing to recognize is that the site stopped operating in the us (which it said it would do in reaction to this decision) after it was clear that it would definitely be violating a law with explicit consequences if it continued.

One unremarked-upon aspect of the events between Saturday and Sunday was the arson of a representative’s office in retribution for the ban.

Combined with the crappy algorithm after the shutdown (indicates they gotta actually rebuild all the recommendations), it’s likely that the company shut the site down to be in compliance, intending to go back up if possible once the law was reversed or the new administration was in power, and was offered assurances against legal action and protection against the law after the representatives office was set on fire.