ryannathans

joined 2 years ago
[–] ryannathans@aussie.zone 1 points 1 hour ago

There are 25 rail passenger casualties for every 100 collisions with a heavy vehicle at a crossing, of which there are 14609 collisions with trucks in the US database over a ten year period to 2021

[–] ryannathans@aussie.zone 1 points 3 hours ago

Do you have a source this is how it works in america? Isn't it based on census data where people choose how they identify?

[–] ryannathans@aussie.zone 6 points 6 hours ago

Fuck that's crazy, its lethal dose by mouth is LSD's standard dose by mouth 😂

[–] ryannathans@aussie.zone 0 points 6 hours ago (2 children)

Over an 8 year period there were 49 90 degree rail accidents with trucks at crossings in Australia

[–] ryannathans@aussie.zone 2 points 23 hours ago (14 children)

These models tested are so old they're from the era where they couldn't pass a math test or count letters in words

[–] ryannathans@aussie.zone -5 points 1 day ago* (last edited 1 day ago)

At the same time there's a whole bunch of idiots running around thinking they know everything just because they paid the university tax and got a piece of paper

Imagine someone of average intelligence, then 50% of people are dumber than that and maybe 10% are functionally equivalently intelligent. Maybe 40% of the population are switched on, now throw in some politics and wildly different upbringing and life experience

[–] ryannathans@aussie.zone 1 points 1 day ago (4 children)

Interesting how they're unacceptable for cars but the norm for trains and they don't even have seatbelts

[–] ryannathans@aussie.zone 0 points 1 day ago (9 children)

How do bench seats kill people?

[–] ryannathans@aussie.zone 0 points 2 days ago

For an LLM comparison, this is what I get from haiku

sudo is older, more complex, and feature-rich, while doas is newer, simpler, and security-focused.

Core distinctions:

Code size & complexity: doas has roughly 700 lines of code versus sudo's 100,000+ lines, making doas easier to audit and maintain.

Configuration: sudo uses the complex sudoers file with intricate syntax; doas uses a simpler doas.conf file that's more straightforward to read and write.

Security philosophy: doas was designed with security-first principles, minimizing potential attack surface. sudo accumulated features over decades, increasing complexity and potential vulnerabilities.

Feature set: sudo has advanced features like session recording, plugins, authentication caching, and detailed logging. doas is minimalist—it handles the essential privilege escalation task without extras.

Adoption: sudo is ubiquitous across Linux and Unix systems. doas is less common but gaining traction, particularly on OpenBSD (where it originated) and among security-conscious users.

Performance: doas is faster and lighter, while sudo carries more overhead.

In practice, doas works well for straightforward privilege escalation needs, while sudo is better if you need advanced features or broader compatibility.

[–] ryannathans@aussie.zone 3 points 3 days ago

Is it chlorinated? Peroxide would break down the chloramine

 

The eSafety commissioner’s office has said the age-assurance trial report found geolocation technology and other signals could be used to detect if users are trying to use a VPN. The report itself suggests VPN users should not be blocked, but checked with age verification. That could mean that, if implemented, anyone using a VPN anywhere in the world to access the sites would have to verify their age, despite not being in Australia.

 

Been out of the game for about a decade, just wondering what platform everyone uses to share digital albums/event photography with friends and family?

Back in the day imgur, Picasa, 500px and flickr were viable options for the hobbiest but it seems they either no longer exist or are now very, very expensive for low volume nonprofessional sharing

 

I've been trying to create a new cpuset to run some programs with a reduced set of cpu cores, but I seem to be fighting with something my system is already doing because the instructions from the kernel manual don't work. I find cpuset is already mounted, but when I create a directory in /sys/fs/cgroup/cpuset it does not end up with cpuset.cpus in it. It seems cpusets are aleady being used by something else, so not sure how I'd go about this?

Manual with step by step tutorial: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html

 
view more: next ›