Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)OT
Posts
0
Comments
322
Joined
2 yr. ago

  • The other one is just comparing volume.

    This post is just basing it on heat capacity.

    There's another saying 34 equating it to a tank less heater.

    The original question is too vague - there's no one to one mapping between keurigs and water heaters. If you're just trying to heat your houses hot water, any of those answers are valid. So is "1", but it'd be slow and you'd only get a half gallon before refilling it, and at that point the last batch is cold, but it's still heating water... . It's just a question of what you REALLY want and what your constraints are.

  • The guy who owns the company knows what it means for the long term stock price: a plummet. He knows that'll come eventually if these changes go through.

    Investors may react positively to the news, but when they see the damage it actually does, they'll pull out too.

    The guy running the company has shares that are valued way higher than when he earned them, he is sitting so high right now it's far worth selling here instead of gambling on the response to the news. It's just simple "quit while you're ahead".

  • This is an entirely different context - most of the talk here is about LLMs, health data is entirely different, health regulations and legalities are entirely different, people don't publicly post their health data to begin with, health data isn't obtained without consent and already has tons of red tape around it. It would be much easier to obtain "well sourced" medical data than thebroad swaths of stuff LLMs are sifting through.

    But the point still stands - if you want to train a model on private data, there are different ways to do it.

  • Yeah, I agree. They've made slight shifts over the years, but I feel like this looks enough like a different maps app.

    I also feel lots of pieces of it include bits of the apple design that make their maps harder to read.

    Google doesn't need to change their color pallete, they just need to stop tossing 400 advertising pins everywhere you look.

  • Yes, but if you host an image, and my client prefetches it, it's going to exposed my IP to your image server. And if you have clauses saying you're collecting IPs...

    Meta basically invented this shit. They'll do it again. It's what they do.

  • Yes, but many clients are going to go look up images manually. If it's a Threads post, it's likely hosted by Meta servers, and they can easily see your IP when doing that. And they're saying they might collect IPs from you even if you're not using their service directly.

  • Meta says, for Threads to federate, they access the same data any instance does when it federates.

    Okay, but like, I don't want Meta consuming that data? At least if they wanted to scrape through reddit to put that together, they'd be going out of their way. This data is now just coming through the same API "for free".

    If I didn't mind Meta scraping through all this, why wouldn't I just use Threads?

    This is exactly the kind of shit that pushed me here - I don't want Meta sifting through all my shit. Its unlikely that some other instance host is going to start building psychological advertising profiles on me and sell it to the highest bidder. But you bet your ass Meta will try.

  • No, they probably abandoned it because they only said they would do it because they thought it would increase their public appearance. Once they got the boost from saying they'd do it, if they just silently back out, it's unlikely that people notice and/or care anymore.... That's just how advertising works.

    They probably never had any intention of actually following through to begin with.

  • It's more like the law is saying you must draw seven red lines, all of them strictly perpendicular, some with green ink and some with transparent ink.

    No, it's more like the law is saying you have to draw seven red lines and you're saying, "well I can't do that with indigo, because indigo creates purple ink, therefore the law must change!" No, you just can't use indigo. Find a different resource.

    It's not "virtually" impossible, it's literally impossible. If the law requires that it be possible then it's the law that must change.

    There's nothing that says AI has to exist in a form created from harvesting massive user data in a way that can't be reversed or retracted. It's not technically impossible to do that at all, we just haven't done it because it's inconvenient and more work.

    The law sometimes makes things illegal because they should be illegal. It's not like you run around saying we need to change murder laws because you can't kill your annoying neighbor without going to prison.

    Otherwise it's simply a more complicated way of banning AI entirely

    No it's not, AI is way broader than this. There are tons of forms of AI besides forms that consume raw existing data. And there are ways you could harvest only data you could then "untrain", it's just more work.

    Some things, like user privacy, are actually worth protecting.

  • That's not how I read it, but I'm not going to claim to be a fediverse expert. That post specifically says:

    Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:

    To me, this reads as, even if a Threads user follows you, your info gets chewed up by Meta.

    In other words, if you post somewhere on the Fediverse, and some Threads user bumps into it, they can follow you, and that will send all that data to Meta. And it looks to include data well beyond the post the Threads user saw.

    To me, this is a "sound the alarm" moment. If you came here to avoid Meta's data harvesting, this sounds like you at least need to be on an instance defederated from threads, but I'm not sure even that's enough.

  • Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:

    Username

    Profile Picture

    IP Address

    Name of Third Party Service

    Posts from profile

    Post interactions (Follow, Like, Reshare, Mentions)

    So if you follow a threads user or even if a threads user just follows you, they pull all this data?

    IMO this seems like reason to defederate across the board. Someone else can leak your info to Meta.

  • It seems to say that it would report any wifi devices MAC address, which would include the devices connecting to the network and the routers providing the network.

    But you'll have no idea what they are. They could be anything from a router, to a smart light bulb, to a thermostat, to a security camera, to a cell phone, etc.

    I'm sure plenty of polling places will "light up the alarm" - what polling place doesn't have some wifi network for SOMETHING? And some people will have cellphones trying to connect to that network etc.

    I don't know specifics about voting machines, but from a security perspective, their network connections should 100% all be hard wired. Wireless just adds more security holes. They should be hard wired and wifi sniffers will never touch that.

    So either you get no alarm and it could still be hardwired to the internet, or the alarm goes off and you don't know if it's the voting machine or Billy Joe's iPhone trying to connect to the voting centers open wifi network.

    The whole thing is entirely pointless.