>so much saner than Linux firewalls it's not even close.
This is a big one for me. I've run openBSD and Linux custom boxes as SoHo routers and I just cannot stand Linux firewalls, I've never liked them and IPTables is just terrible. Yes I know there are wrappers around it now but it's still the default everywhere and still used by lots of other software like Docker. I'm using OPNSense now which is FreeBSD based instead of completely rolling my own but I love that it is still BSD under the hood.
One differing opinion I will offer is that I find NixOS to be the Linux distro most in the openBSD spirit despite it being very different from a UX and config management perspective. Alpine is interesting, but it has its own security and compatibility issues, especially around MUSL libc which I have had cause many strange downstream issues over the years, I just hit one recently in JVM GC caused by its memory allocation implementation. I've stopped using alpine altogether because of them.
Feel the same way about COVID. It damaged the social fabric in ways that have not recovered. I think a lot of people realized that maybe they never really liked socializing as much as they thought they did. I also think it just kind of reset people's expectations around socializing. The other big one to me, that it also unleashed, was inflation. Dining out, sporting events, concerts etc are all way more expensive than they used to be. Places are still busy and games are still packed but the prices are way higher, more evidence of the K shaped economy where only the top stratas are spending. Also, and this is subjective, it feels a bit more performative, as in people are going because it signals they have the means (edit: and the general instagram-ification of our culture.)
The damaged social fabric - for me - didn't consist of spendy stuff. Just backyard BBQ's, pool parties, (hosted) brunch or dinner invitations, that sort of thing. You keep doing it because habit. But then a 2 year interruption because of COVID, habit broken and before you know it you haven't talked to some people for 5 years and now it would be awkward to call them up again...
Restaurants realized they were leaving a lot of money on the table pre-Covid. Post-Covid has seen restaurants raising prices more aggressively, cutting staff, cutting condiments, replacing menus with QR menus, cutting employee and business hours, etc.
The post-Covid real estate/tech/AI /white-collar job/quant boom has led to inflated salaries, wealth inflation and higher prices to match, and then combined with various supply chain shortages and disruptions, e.g. (many tariffs, Israel v Iran v Russia v Ukraine wars and tensions, etc.).
If I paste something from an AI into chat, I always identify it as such by saying something like "my claude instance says this:". I also don't blindly copy paste from it, I always read it first and usually edit it for brevity or tone. Feel like this should be the absolute minimum for sending AI content to a person.
Even that is pretty useless because we have no idea what context "your Claude instance" has. All you're doing is dressing up some bullshit to look authoritative.
When I started my PhD I was already really good at typesetting with LaTeX. I started to bring in fully typeset works in progress for my supervisor to read through. These proofs often had fatal flaws. He asked me to stop typesetting until after the work had been verified because it looked too convincingly correct due to being typeset.
That was about 15 years ago but I've never forgotten it. Drafts should look like drafts. Scrappy work and proofs of concept should look as such. Stop fucking with people by making your bullshit, scrappy ideas look legit. Progress is a cooperative effort. It's not about trying to make people say yes.
Can confirm. I saw some fresh out of college colleagues do this in text docs. Al nice markup, but the text content was very drafty. I always sent them back to keep the format concept-y if you are tuning the text first.
Extremely debatable. They still have never fully implemented health checks and auto healing. I have had compose itself behave in unexpected ways, weird things like not realizing the tag of an image it is running is actually in use, and letting prune commands yank it out from under the system. Other things I can't remember. I'd rather use something like Nomad or for simpler systems maybe plain systemd. But realistically kubernetes is a superior orchestrator in just about every way, and installing k3s is simple and k3s is actually production ready. I don't like kubernetes all that much as cluster tech, but as a container orchestrator it has a lot of nice features.
I'm totally onboard with k3s/k8s being better in a lot of cases.
But docker compose can actually be very sufficient for what many projects actually need.
Granted I am a guy pushing for compose based localdevs and such but going further you often just cannot beat the simplicity of doing update QA or other CI/CD workloads in compose based projects. I have had dozens of projects where we replaced flaky slow and maintenance heavy pipelines with just docker compose up --build --wait in the past years. How come you say health checks are still broken?
I do use compose for some things, smaller one off type setups, and I’ve done the compose up --build CI/CD approach before. I’m generally not a fan of building on the production node outside of very small deployments. It can work, I just think it tends to blur the line between build and runtime more than I’m comfortable with.
Some of my concerns with compose aren’t purely technical. It makes it easier to lean on local state like volumes, bind mounts, and large .env files. Similar mechanisms exist in kubernetes, but the additional setup tends to force a bit more thought about whether they’re actually needed or just a shortcut.
On the health check side, they exist, but compose doesn’t fully act on them, that's the part that is missing. There’s no built in remediation or orchestration behavior tied to health status, which is why things like
https://github.com/willfarrell/docker-autoheal exist. It’s something that was never fully carried through in Docker itself.
> Extremely debatable. They still have never fully implemented health checks and auto healing.
Agree.
Plus there's the monitoring of the host that is always overlooked in articles. I've ended up chucking Monit on there to monitor disk usage et al, and also used it for monitoring compose too and restarting containers.
And then there's Healthchecks.io, and external uptime monitoring... the list goes on. Properly monitoring systems, even single server systems, is not simple.
I'm a fan of the monorepo in general, even before LLMs. If using git it leverages git's best feature IMO, the commit as a snapshot of the entire repo. I've worked on so many projects where tightly coupled things are split across repos because it's thought of as a best practice, and it just makes it more difficult to figure out what code you are running.
>CalDAV, CardDAV, and SMB are baked into iOS, whereas these are onerous to set up on Android
I can only speak to SMB but it is not hard on Android. I use a longtime third party app so not sure what the state of native support is but it works just fine for me, including over VPN
No, we don't. This is big tech shifting liability off themselves with the added bonus of full de-anonymization. Take a look at who is lobbying for this.
Not a great trend. Installing a OS that makes me tie provably verifiable identity directly to a install or session will be a pretty stupid liability for anyone to agree to. Feel bad for all the non techs that will just accept this lying down. Especially when the solution is so easy to solve with existing tech. Got a internet connection? Block the domains at the router level. Then we need the cell phone providers to allow parents to do similar things at the network level with cell internet. Done. Let the parents do it.
This is one of those situation where both things can be true at the same time.
Social media companies have shown that they do not give a shit about the mental health of their users, quite the opposite seems to be true. Yes, parents are responsible for teaching their children about the reality of modern social media, but they can only do so within the limits of their abilities and understanding. It's similar to smoking. Yes parents are responsible for teaching their children about the dangers of smoking and encourage them not to, but no one thinks removing the age restriction from tobacco is a sane idea.
One one side you have big companies paying huge amounts of money to super smart people to get teens hooked on their products.
On the other side you have parents who on average dont understand how social media algorithm works or in some (too many cases) they cannot follow the logic to a second order effect.
Even here we have comments saying something like "be smarter and teach your kid to be smarter than big social media companies" not understanding that addiction cannot always be defended by improved IQ. Geniuses can have addictions too.
Why stop at removing restrictions on social media, why have laws at all, they're just mindless paternalism! why should we have seatbelts? why have laws against murder? Mindless paternalism is all those laws are!
Not all laws are are meant to protect people from themselves, most laws aren't.
Murder isn't illegal because we want to protect people from the results of their actions, it's illegal because we want to protect people from the actions of others. (Or, failing to do that, punish the aggressors in response) Surely you see the difference?
Basically, the argument is that people's liberty should only be restricted up to the point of defending the liberty and rights of others. If an action hurts no one other than its actor, the state has no right to restrict them. People should be free to live in line with their wishes and conscience up to the point of not violating the rights of others.
With regard to seatbelt laws, I would ask the same question, as I do think that the seatbelt laws are also paternalism and morally wrong.
But no one, including the government, is omniscient. This turns all agency into "exploitation", and the only logical conclusion is that all decisions for all people should be made by the most informed. Surely you don't argue that would be a good thing?
The mindless paternalism is the point! People like this want a Nanny State to enforce their own ideals, as they arbitrarily believe themselves to be morally superior.
That’s why these laws happen to begin with. It starts as “Think of the children”, and ends with the death of the anonymized internet.
Governments crave that, and scared, hapless citizens who refuse to learn how to raise a child want Daddy Gubament to do it for them, and so push these laws into existence.
"Almost every state has some sort of parental responsibility law that holds parents or legal guardians responsible for property damage, personal injury, theft, shoplifting,
and/or vandalism resulting from intentional or willful acts of their un-emancipated children."
"Parental responsibility laws are one vehicle by which parents are held accountable for at least a
minimal amount of damage caused by their children as a result of intentional acts or vandalism"
Using social media is not a crime. I think what we’re talking about here is child welfare or child protection laws (which all 50 states probably also have).
if disallowing social media use below the age of 16 becomes a law (like the article's proposed bill), and a kid breaks that law, this seems like a perfect example of holding the parents liable?
but also yes, child welfare laws and such are also pretty fitting examples. i dont think the person asking for an example was really asking in good faith, anyhow.
My understanding in this case the social media company is liable for allowing a child to access social media. So is not a crime for a child to use social media.
> Children cannot be left with the responsibility for staying away from platforms they are not allowed to use. That responsibility rests with the companies providing these services. They must implement effective age verification and comply with the law from day one
sure, that sounds right for how it is currently. my parenthesis above is probably wrong.
but the whole point of my example was showing that its absolutely possible to hold parents accountable for their childs actions. there are dozens of laws that do so already. so there is no excuse why a social media ban could not be written in the same fashion as those laws, rather than moving parental responsibility onto tech companies.
Laws hold parents accountable for their childrens' crimes, not their noncriminal actions. Nothing about this is saying that accessing social media is a crime -- that would be more similar to drug possession laws, firearms licensing, etc.
If your child is drinking: they are violating the alcohol possession age limit themselves; you are liable for their crime plus child endangerment if you gave them the alcohol; and whoever sold or supplied them the alcohol is violating a separate law. Sounds like we're trying to apply the same structure to social media, except (so far) with no possession/usage law.
I don't really see how that is relevant? Isn't that law making a parent responsible for actions their child commits that hurt others? Child protection laws like preventing child labour, not selling alcohol/cigarettes, etc aren't this.
its an example of holding the parent responsible when the child breaks a law.
if accessing social media below 16 becomes illegal, this is a literal perfect example of holding parents accountable for their kids illegal activity. you can't possibly get more relevant.
there is no reason to shift parental responsibility onto tech companies. we have existing laws that can be used as templates for social media bans.
Correct me if the US is different, but in the country I live in the onus is on the bar or liquor store if they sell alcohol to a child, not on the parent. Why would it be different for a social media ban?
Oh man where I'm from they'd probably just laugh and put them to bed. jkjk
To be honest I did some brief searching and couldn't find anything! The parent will be liable if someone at your home drinks and drives home drunk, but I couldn't find anything specific about children consuming alcohol alone. It is only illegal to sell alcohol to minor, underage alcohol consumption is explicitly legal if supplied and supervised by an adult.
Now I'm sure if the child were to be young enough other child abuse laws could come into play, but it looks to be exceedingly rare.
okay, so we now have: parent/homeowner responsible if someone drives home drunk, parent responsible if child gets drunk via abuse/neglect laws, and parent responsible for other crimes and damages caused by a child via dozens of individual laws.
is that enough examples to satisfy your initial request?
(which was a request for examples of the extremely broad statement: "We used to hold parents liable.")
So I asked for examples because there is a large difference between "We used to hold parents liable" meaning "we used to, socially, hold parents accountable for raising well adjusted humans" (which I would mostly disagree with) vs. "we used to persecute parents for normative laws" (which I mostly agree with).
I know your point is talking about point 2, but I believe OPs comment was about point 1. But I also still don't know what the "used to" means in the original, do we not anymore?
This is a big one for me. I've run openBSD and Linux custom boxes as SoHo routers and I just cannot stand Linux firewalls, I've never liked them and IPTables is just terrible. Yes I know there are wrappers around it now but it's still the default everywhere and still used by lots of other software like Docker. I'm using OPNSense now which is FreeBSD based instead of completely rolling my own but I love that it is still BSD under the hood.
One differing opinion I will offer is that I find NixOS to be the Linux distro most in the openBSD spirit despite it being very different from a UX and config management perspective. Alpine is interesting, but it has its own security and compatibility issues, especially around MUSL libc which I have had cause many strange downstream issues over the years, I just hit one recently in JVM GC caused by its memory allocation implementation. I've stopped using alpine altogether because of them.
reply