I know you already found something that fulfills your needs, but the mullvad doh servers can do blocking and then you’re doing dns over https with dnssec and a few blocklist options.

debian and rhel.

if you can do it on debian you can do it on one of the derivatives and same for rhel.

its amazing how many people still don’t know that you can run a handful of rhel machines for free.

Pretty happy. Debian works good. Rhel works good too.

The Toyota Camry and Lexus 300 of distros.

Yeah stuff like pokemon cartridges needs a 3v supply.

Now we just need open source directx and direct draw so all the visualizations work and we’re in business.

Because most oss maintainers are more afraid of their work disappearing due to service shutdowns than they are being profiled by data miners.

Everyone has seen some example of a tool or resource hosted on a persons private server end up taken down because they couldn’t afford it, the isp or university stopped offering hosting or because they simply couldn’t keep doing it due to death or old age.

That’s what people who create software are afraid of. The loss of that creation, not the loss of the privacy of people who contribute to it or download it.

if you want to preserve the clock memory then use an ungrounded soldering iron. Usualy the cheaper ones are ungrounded and the midlevel ones are grounded. expensive or micro stations will sometimes have a ground lift switch. if you use a grounded one it’ll run a chance of getting into a fight with your bench supply over weather 3v gets to be at the node youre soldering.

Good luck. if you find that the through holes are too small to get good heat transfer, don’t be afraid to leave a 3/8" or so bit of the old leads sticking out and solder your replacement onto them. covered with heat shrink they’ll be fine.

they make low acid or non corrosive or whatever hot glue to attach that little toilet lookin’ doohickey for just these applications.

The eos on that 1802 was 2018. They stopped selling batteries for it a year before it stopped being supported. They claimed in that bulletin it was because of the shipping restrictions on batteries (which I believe!) too, so that might have had something to do with the series of decisions that led to soldered in batteries.

I didn’t even think of shipping restrictions making it prohibitively expensive to ship replacement batteries. That’s a good one.

Since you’re the op, how do you handle soldered in batteries? As you might expect from my replies, I just unsolder em (with a bench supply tacked in to keep power going to the circuit) and put in a replacement. Usually I don’t even put in battery holders, just another soldered in cell of the same type.

First things first: it is replaceable. I outlined how to replace it.

Second, the battery doesn’t define the lifespan of the equipment. The upgrade cycle it’s designed around defines the lifespan of the equipment.

But let’s say it didn’t. Let’s figure out how to make an rtc battery field replaceable:

It will need an access panel and a battery holder. We’ll need to limit out selection of battery chemistry to those that don’t corrode around the contacts. We gotta standardize the location and type of battery so that means standardizing the type of rtc circuit and since the whole point of choosing a replaceable battery is to lengthen the life of the equipment, we need to pick a rtc circuit with a long design life too and integrate that choice into all our future designs. I say that because most of the time nowadays there’s so much stuff on any given board that you gotta go out of your way to get a pcb that doesn’t already have some kind of rtc integrated into some kind of chip you picked for a different reason somewhere.

Now let’s put our battery door on. Wait a minute, this things 1u. The front panels all the way out because it’s taken up by 48 Ethernet jacks, six leds, two usbs, two fcs, two more ethernets, a serial port, a button and somehow a corporate logo around the edge. Okay let’s turn it around: crud, all taken up by two huge bus connectors, two power supplies and their vents, two power inlets, the quick release tabs for the power supplies and bus connectors, the mandated visible ul/health and safety sticker and another fan grille.

Guess we’ll have to put it on the other sides. No big deal, just isolate the place on the pcb that the battery holder sits on so its standards compliant, add a few plasma cuts and a dimple to the machining steps for that panel and add a little plastic door (captive with a screw or hinge so it can’t be lost) and we’re done!

Except we just made it worse.

Imagine going to replace that battery. It’s field replaceable, right? So what’s that process? Oh it’s real straightforward, you just bring down or reroute the systems reliant on the unit, unplug 48 Ethernet jacks, two usbs, two fcs, two more ethernets, a serial port, two bus connectors from the back, and two power inlets from the back, pull it out of the rack, unscrew the battery door, replace the battery, put it back in the rack, plug in 48 Ethernet jacks, two usbs, two fcs, two more ethernets, a serial port, two bus connectors into the back, and two power inlets into the back, turn it on, securely set the rtc (this is incredibly important!) and reroute systems back to it or bring them back up.

And if nothing goes wrong, if we didn’t damage a connector or receptacle, drop something or catch an esd event then we just doubled the lifespan of our device!

Except we didn’t. The battery had a ten year service life in this environment, and we replaced it at nine to be safe. Cisco though, stopped releasing security patches too, so now our router has ten new years of being unavoidably owned by every sk the world over.

Well, if we just went through all that work, probably the firmware policy would be updated and the support window lengthened to match, right? So now they’re pushing security patches for 20 years! Certainly that cost won’t be borne by the customer and we’ll be rewarded for our good design work!

On a gigabit router. For the rack mount environment.

And we also have a standard rtc and battery type to integrate into all future designs, training material and equipment.

I didn’t just waste thirty minutes of a day off writing that up to make fun of you, but to illustrate how the conditions under which specifically telecommunications equipment operates, is designed and managed dictate what decisions the designer makes about stuff like rtc backup batteries, which are a security feature btw.

If we had say, a planned economy, we could expect devices like these to be designed with a longer lifespan and an extant recycling process in mind. Under our current system that’s just not possible.

When the time comes to replace soldered in batteries, (optional) snip off the leads, remove the remaining leads with a soldering iron and replace with whatever is handy.

Speaking from the experience of replacing lots of soldered in batteries in devices with high downtime and understanding the design and function of rtc backup batteries in telecom equipment and specifically spending months cleaning and refurbishing old telecom equipment for resale, Nintendo cartridges need replacement batteries, not switches.

The battery is only backing up the rtc when the power is off. Telecommunications equipment is high uptime and shouldn’t ever even see an outage as long as Pokémon emerald.

This isn’t asshole design. This is good design.

The lockout I see most often isn’t from people forgetting a password or key, but from motherboard failure with a key stored in the motherboards tpm or cpu.

What matters is that the backups are done at the appropriate intervals and verified to be readable.

You can figure out what interval is appropriate. Some people have to make sure every picture is saved, some people are fine losing a month of stuff.

Verifying the backup is valid equally important. You don’t wanna find out it was misconfigured and didn’t get your user directories when you try to restore. Just open one up and look to see every once in a while.

At least fifteen years ago you could set up windows backups through the control panel > backup or something menu. Now on 10 it’s settings > updates and security > backups.

You can click add drive from there and designate a usb or something as your backup drive.

Then set an alarm to make sure you remember to do it at the designated interval.

With android the easiest thing is to sync it to a computer that gets backed up.

You can use cloud services instead of a hard drive too, but often simple and easy to understand is the best place to start.

Do you know why it’s important to have backups before using full disc encryption?

What are you actually gonna be doing? Not 10 virtual machines or whatever you said, what actual services are you gonna be running?

pen and paper.

i have a graph paper notebook for “real” stuff like designs and plans and a little top spiral notebook that lives in my back pocket for quick reminders, notes and ideas.

periodically throughout the day i’ll look at the little notebook and knock out stuff on it or move them to the big one.

the “rite in the rain” brand has waterproof notebooks you can use for when you need to write shit down in tech-averse climates.

do not do anything in this post until you have backups that you know run and work.

device encryption is fantastic.

Your just mad no one can uncuted your foreskin

What the hell? This was all reasonable stuff to discuss in newsgroups thirty years ago and every time the equivalent of xz happened but somehow now it indicates someone doesn’t understand open source?

And before someone makes the absurd claim that the limits and constraints of open source were settled back then, a state funded targeted attack on an open source project is as good a catalyst as any to uhh… revisit the priors that the “community” holds dear.

I swear to god you can take the redditors out of Reddit but you can’t take the Reddit out of the redditors.

that’s nice, but the whole reason recapcha and other ai training capchas exist is that it costs money to host and maintain those services and they’re able to recoup those costs by harvesting and monetizing user data.

capchas literally do have to be boring dystopian bullshit because no one will pay for the alternative.

My comment really applies more to vi than vim but everyone’s using them interchangeably nowadays. When implementing systems where internet connection or excess install size aren’t possible or recommended, you gotta be able to work with the tools at hand.

Of course, the comparison is custom cabinetry to ikea. Your local meth head needs to understand how to use hand tools because he or she may need to use them for myriad reasons ranging from “I don’t have the power version of this” to “it’s faster” to “the cut is cleaner” to “they pay me more to use this”. The person designing hudfł needs to be concerned first and foremost with how to shave a sixteenth off every panel so his accounting department doesn’t have to pay to reforest an extra hundred acres this year.

Perhaps someone working entirely in programming has good reason to not know vim, but I still cling to the antiquated notion that the person designing furniture out of manufactured materials ought to be able to build a box you’d feel comfortable with company seeing.

lol if you can’t use vim.

Who cares that you can cut a perfect miter joint with a jig and a table saw when you can’t cut a butt joint with a hand saw.