US states. If I have more than 50 different host names to manage, I should re-evaluate my hobbies. And then lazily move on to US state capitals.
US states. If I have more than 50 different host names to manage, I should re-evaluate my hobbies. And then lazily move on to US state capitals.
I see this on my instance with an age of 6 minutes
Lemmy’s allowlist feature is generally recommended against. It limits federation to only that list, which makes discoverability harder than it already is.
For a self-serving instance, it’s more tenable to use a blocklist and federate normally.
A contrived metaphor: if an unleashed dog bites a person, is the dog owner no longer responsible for the incident?
You could say that it’s up to the car owner to install a steering wheel, like how a dog owner should use a leash. But this would be a gap between when the person receives the car and when they could install the steering wheel (assuming the wheel installation can be performed).
In 2016, the first known fatality linked to a self-driving car took place when a Tesla Model S failed to stop and crashed into a semitrailer truck.
Ah, this one is hard to forget. I remember this one vividly because it sparked all sorts of philosophical discussions around the use of self-driving cars. Hypothetical scenarios like “Between a family of 5 with children, should the car choose to kill the driver to save the family” and the different variations of the trolley problem.
Determining the responsible party was always a puzzle to me. The current state of auto-pilot requires hands-on attention from the driver, so the accountable party is arguably the driver. But with a fully autonomous vehicle, where the steering wheel isn’t installed, is the car manufacturer accountable for deaths and accidents?
The skux life chooses you.
Can’t afford the new minimum wage, but they can afford the lawyers and the lawsuit.
Most likely kbin.
If we’re talking about a timeline where the Fediverse was never created, then I’d probably just be on Twitch for socializing and RSS feeds for news.
Ah that’s good to know. I suppose this is a reasonable limit to what I gain by living on the bleeding edge.
Upgraded the UI to 0.18.0-rc1
and the backend to a few commits ahead of 0.18.0-rc1
. I haven’t seen this issue so far today.
And I just got a 14 day-old post. So it seems like the issue is still there.
I own this.
I’m guessing the author doesn’t have this issue, but the model sold in the US has a volume
limiterlimit on them. My daily headphones aren’t easy to drive, so this was a concern I have that many other people might not care about.I ended up having to import mine to get a device that doesn’t have this enforced.
Edit: Sorry I was clumsy with my words. It’s a limit on volume, since it’s an option for high gain.