• 0 Posts
  • 21 Comments
Joined 11 months ago
cake
Cake day: August 14th, 2023

help-circle




  • I think my personal resource consumption, if scaled up to the world population, would be devastating. That’s what I mean by categorizing myself in the “rich.” I might not be a billionaire, but I’m far, far above the global average, and still significantly above the national average for my nation.


  • Yeah, having kids probably reduced my household resource consumption, compared to the dual income no kid lifestyle that my wife and I had before kids.

    Population growth is so far disconnected from resource consumption, because people’s resource consumption does not resemble a bell curve. A private jet produces more CO2 in an hour (about 2 tonnes) than the average Indian produces in a year (about 1.9 tonnes).

    The poor people having children aren’t destroying the planet. Rich people, childless or not, are. (And yes, I acknowledge that I fall under the “rich” category here.)




  • Yeah, timestamps should always be stored in UTC, but actual planning of anything needs to be conscious of local time zones, including daylight savings. Coming up with a description of when a place is open in local time might be simple when described in local time but clunkier in UTC when accounting for daylight savings, local holidays, etc.


  • booly@sh.itjust.worksto196@lemmy.blahaj.zonerule
    link
    fedilink
    arrow-up
    9
    ·
    13 days ago

    Self deprecation comes off wrong when it seems like the thing you’re criticizing is actually important, and that you actually believe it.

    So it’s funny when the audience knows you don’t believe it’s important, either because everyone agrees it’s not important (“I can’t sing on tune to save my life”) or if it’s a particular example that doesn’t matter (“I’m such a bad mom because [something inconsequential]),” or if it’s a topic that people can see isn’t important to you (jokes about being socially awkward, bad at your job, etc.).

    If you’re in one of those lanes, you can go pretty hard on yourself before it seems to go too far.


  • Wasteful of what, though?

    If a particular farm can produce 1000 kg of meat and 500kg of bones/other waste in a year by raising female meat chickens, would it be a waste to devote that farm to raising 500 kg of meat and 400 kg of bones from male egg chickens? In a sense, that’s a waste of the farm to produce half as much meat as it can produce through killing chicks.

    It’s a philosophical difference on what weight to assign to the lives of chicks, adult chickens, other resources including human labor, etc. The lazy shortcut is to maximize return on dollar investment with no regard for any of those moral, ethical, and philosophical considerations, and that’s what most of the industry does today, but even if you shift to a new moral framework you’ll need to decide how to weight those things.


  • Dual purpose breeds for both egg laying and meat production are poorly optimized at either. So the industry has moved onto specialized breeds that are best at doing one of them.

    Plus raising roosters together is much more logistically challenging than raising hens. So they’d need much more space and much more oversight/labor. So rather than devote some resources to raising males of breeds that are good for laying eggs, they’d rather devote those same resources to raising much more meat from females of meat breeds.





  • Things might be different by now, but when I was researching this I decided on the Yale x Nest.

    It’s more secure than a keyed lock in the following ways:

    • Can’t be picked (no physical keyhole).
    • Codes can be revoked or time-gated (for example, you can set the dog walker’s code to work only at the time of day they’re expected to come by).
    • Guest codes can be set to provide real-time notifications when used.
    • The lock keeps a detailed log of every time it’s used.
    • The lock can be set to automatically lock the door after a certain amount of time.

    It’s less secure than a physical traditional lock in the following ways:

    • Compromise of a keycode isn’t as obvious as losing a key, so you might not change a compromised keycode the same way you might change a lost key.
    • People can theoretically see a code being punched in, or intercept compromised communications to use it.
    • Compromised app or login could be used to assign new codes or remotely unlock

    It’s basically the same level of security in the following ways:

    • The deadbolt can still be defeated with the same physical weaknesses that a typical deadbolt has: blunt force, cutting with a saw, etc.
    • The windows and doors are probably just generally weak around your house, to where a determined burglar can get in no matter what lock you use.
    • Works like normal without power or network connection (just can’t be remotely unlocked or reprogrammed to add/revoke codes if not online)

    Overall, I’d say it’s more secure against real-world risk, where the weakest link tends to be the people you share your keys with.


  • The instance I’m logged into doesn’t forward my user agent, IP address, or CSS/script support (or other fingerprinting techniques) to the other instance. Everything I do in a community hosted on another instance is forwarded through my instance server as a middleman, and I never directly connect to the other instance server.

    The admins of an instance (or reddit) might be able to analyze server logs of different users on their own instance to be able to determine those things, but can’t apply that analysis to accounts from other instances, whose interaction with the server doesn’t actually include a login or any direct connections to the server they administer. All they have to go on is the ActivityPub logs, which won’t include that fingerprinting information.


  • Reddit does have vote manipulation, but reddit admins can easily see much stronger indicators of the same person behind multiple user accounts: Server logs of user agent, IP address, interface/API key, script support and activity that tends to give away browser type and history, etc.

    Most of that information is only available to instance admins, so admins of one instance can’t see when external votes are coming in from the same users who already voted using accounts on your instance.



  • Fundamentally, though, how can it be stopped? The two instance administrators can only see part of what’s happening, and can’t directly determine that the votes are coming from two alts of the same user. Maybe over enough times, the patterns can be guessed at with heuristics, but this kind of vote manipulation is going to be a problem for federated communities. Especially if we don’t get better moderation tools developed.