https://tools.sendmarc.com/ Is a good start. Listen back through the security now eps where he’s setting up his own email list with his own email server.

What?

You find out if the hardware can handle it by looking up its video decoding capabilities on Wikipedia and checking that it’s capable of the resolution and codec you want. If you’re buying new hardware then a chip from Intel or amd that support the resolution and codec you expect will do the job. It doesn’t need to be the latest and greatest thing.

If you can’t be content with 4k60 over hdmi then you either need to use proprietary drivers or a different cable. Your tv very well may have a displayport slot and that’ll sidestep the problem. I don’t have problems with proprietary drivers but you may.

Nvidias repositories work fine.

If you need the latest driver they have installation instructions that walk you through adding their repos to your package manager and installing that way.

I recommend you get right with using vim or its forks.

I tend to think 99 percent of linux users or prospective users would exchange the modicum of what could be considered lock in if you were to really give it the most uncharitable read in the history of computing for the extensive documentation and support.

I have nothing but hate in my heart and vitriol in my guts for red hat but their linux is owed more recommendations than it gets.

Because linux distribution recommendations are written by people who have nothing better to do than be hypnotized by the jangling keys of whatever’s new or hot for people who have nothing better to do than be hypnotized by the jangling keys of whatever’s new or hot.

It’s the same reason rhel doesn’t get recommended tbh.

The usual way to force a program or process to use a specific interface is called binding. It used to be something you really had to know your stuff to use correctly but nowadays there are a million tutorials out there.

With systemd you can use a pretty well tested and reliable section of the namespace implementation for just establishing a namespace and binding both the target interface and program to it, but you can also just use iptables with a user and mangling.

Nowadays you have nftables, but it does the same thing.

Cons:

It’s not gonna work

It’s not well documented

No one else does it so it’s hard to ask for help

You don’t even need a container for this, just use the routing table

Pros:

New project

No chance to be led astray by stackoverflow or reddit

Contributing to systemd development by testing new features

At no point have I leveled a critique of feature parity or the idea of selling support.

I am explaining in exhaustive (to me) detail how the phenomenal commercial backing that systemd had and still has makes it a ridiculous suggestion that someone could simply maintain sysv the same as people have maintained and developed systemd.

If I love sysv so much I can’t maintain it the same as systemd because I’m not a team of experts being paid to work on it full time!

The contribution of systemd back into the open source community can’t even be without ill outcome because it has replaced simple and easy to understand sysv in the very distribution whose goal is teaching!

As someone whose comprehension of how a computer goes from a complex collection of inert electronic components to a running, functional system comes from building lfs back in the day: that’s bad! No longer can we simply look at the tiny set of programs and simple scripts that take our computer online and gain understanding from that investigation, now we must trust the documentation and operation of an incredibly far reaching and powerful black box called systemd!

We were allowed to freely live within the castle walls and are anbout to lose the understanding of how to build thatched roof huts and split rail fences because of it.

If you want to see this process play out again, leaving you in the unenviable position of old man trying desperately to explain history to people who just charitably accept the present as a given, take note of wayland development, gnome decisions like tilting at middle click and see who is spearheading those changes and whomst they are paid by.

In ten years you’ll be using windows without a functional micro kernel wondering what happened.

Poettering famously began work on systemd while at red hat in order to solve red hats problems.

The people behind systemd didn’t find someone to pay them for their work, they were already employed working for a company in the enterprise linux market and created a software package explicitly aimed at solving enterprise linuxs’ problems because linux was looking bad in comparison to the very mature windows server administration environment.

It’s why systemd has insane feature creep and why back when it was announced literally everyone not on the payroll said “what, why the fuck would I want that? RH BTFO”

Systemd attracts the most people willing to work on init because those people are being paid to do so by companies that sell linux. The companies that sell linux want systemd because its the enterprise solution and if their software or hardware integrates well into the systemd process then they can make money by making lots of sales to people who either work out of or run gigantic datacenters.

This isn’t a case of the best solution with the most democratic support being funded by benevolent community focused businesses (who yes, do make a tidy sum but that’s how the cookie crumbles!), it’s a case of a system exactly like windows getting built by the employees of a company who wants it so it can advertise feature parity with windows in its products!

I feel insane having to type all this out.

If you’re interested, look up the celebrite leak images. They require a little googling of jargon but you might get a couple years on an android device with a locked bootloader and at least four or so on an up to date ios device.

In my experience all the ios stuff won’t pair bfu but some android stuff will. There’s just too much out there to say for sure about everything.

Organizing with people who also want it done, like the systemd people did at the behest of their employer to solve one of its many problems selling linux as a centrally manageable replacement for their competitors’ products.

At some point we have to acknowledge the elephant in the room using an elephant sized lathe and an army of paid workers to shape linux. The days when people could band together and make decisions about the future of this operating system have been over for over fifteen years now.

Surely you’re not serious.

My tiny pebble of help won’t hold back the tides of the desktop environments carving the myriad packages that make up linux into what they need at the behest of whoever keeps their maintainers in new shoes.

Even if it could, choosing the de over the init system in lfs shows where the priorities lie. To quote the linked mailing list message, the decision has to be made. Individual people who see that as a worse path can’t change a thing.

The distro whose goal is education and customization drops support for the easier to understand and lighter init system out of lack of maintainability in service of accommodating the new stuff big desktop environments are doing.

Welcome to the Year of the Linux Desktop. See you all on FreeBSD in 2027.

Of course you don’t. The point of my reply wasn’t to encourage you to rig your car to explode but to explain some of the reasons why it’s perfectly understandable to take every possible precaution about your phone if you think it’s possible cops will get it.

You suppose in your earlier reply that a persons unique actions must be the precursor to a level of paranoia around law enforcement that approaches destroying the phones contents. I was trying to illustrate that everyone should be extremely apprehensive about cops getting their phones, not just those who are engaged in some clandestine bullshit ala the old mad magazine marginalia.

Of course, just turning your phone off if you’ve sufficiently hardened the settings is enough for four or five years of safety on ios and at least a year or two on android.

It’s easier if you think of it like a car. Say you get arrested while in or around your car: doesn’t mean you did anything wrong or broke a law, just that you were arrested. Now there’s a million ways for cops to do the backflip jetpack gymnastics to get to search your car.

Once arrested, some stuff happens but importantly, a prosecutor starts building a case against you.

Maybe you took the recycling out and a crumpled up beer can is in the back seat, that’s an open container. Maybe you picked up some starting fluid for the cold mornings, they found it in the glove compartment in a paper bag, better do that blood test on you to rule out inhalant use, that would give them dwi. Got a significant amount of cash in the locked center console, that’s drug money. Maybe you keep the sporterized bring back hunting rifle your uncle gave you in the trunk, now you have an unregistered firearm in your possession, intent to menace? How will that allow upgrading the charges they’re already building against you? Who can say?

And remember, they’re going to use any method they can to deny you your property if you somehow end up beating the laundry list of charges. You’re losing the gun and cash no question. Civil asset forfeiture will see to that. If there’s anything wrong with your car that would keep it from passing inspection even if it had a valid inspection at the time of impound they can choose not to return it to you and instead sell it at auction for their own gain or just crush it.

Now what lines and spirals are drawn in the cloud chamber of your life when that cop particle strikes your phone instead of your car?

Again, speaking as a radio operator, for this users needs its tough to recommend a radio solution to the non-technical especially when it’s a mesh based hobbyist one the user will be relying on to communicate securely.

Radio also sticks out like sore thumb and it’s important to be able to look normal.

Cell phones have three states: unlocked, locked afu (after first unlock) and locked bfu (before first unlock). When in bfu the phone is much more difficult to attack because it won’t allow access to the pairing or anything really. It becomes even more restrictive with lockdown on.

Turning the phone off frequently accomplishes two things, it keeps the user from messing with it and makes sure if someone grabs you up in your home while you’re reading your newspaper smoking your pipe then they grab your phone while it’s turned off, in bfu lock when it’s powered up.

The duress inputs can do a lot with a little. You can lock the phone, turn it off, dial 911 etc.

iOS devices already have wipe after a number of failed pin attempts. I’m dubious of much more than that for this user. The threat model here is police picking you up and using a far reaching warrant and off the shelf technology to peer into your devices, not someone dead bugging your devices’ security chip. It’s only got to last as long as the cops are allowed to hold your shit, so the four or five years lead that leaks from various cybersecurity companies indicate that devices in bfu have over their opponents in intelligence seems perfect.

It’s common practice for law enforcement to go ahead and do the ten tries or whatever makes the device wipe itself before they give it back to you anyway, so it’s a double edged sword.

Debian/lxqt.