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/)TS
thanks_shakey_snake @ thanks_shakey_snake @lemmy.ca
Posts
4
Comments
687
Joined
2 yr. ago

  • Oh, no, I mean I have an account, but I never (...exceedingly rarely) go on Facebook itself. messenger.com is just the messenger with no feed or other features, and there's a standalone mobile app called Messenger as well, same idea. I use those when I need to interact with someone over Facebook so that I'm not exposed to most of the crap.

    I don't know anything about using it totally without any account.

  • Right! For music, I think it's even like saying... The process of making music is much more than just literally performing it... But it'd be weird for the creative process to not contain any playing-of-music that looked in some ways like performance.

  • I don't think it's just marketing bullshit to think of LLMs as AI... The research community generally does, too. Like the AI section on arxiv is usually where you find LLM papers, for example.

    That's not like a crazy hype claim like the "AGI" thing, either... It doesn't suggest sentience or consciousness or any particular semblance of life (and I'd disagree with MW that it needs to be "human" in any way)... It's just a technical term for systems that exhibit behaviors based on training data rather than explicit programming.

  • Tbh I think alot of the "thinking" still looks like visible work though. I feel like the article makes it seem a little too much like there's nothing observable, nothing to show or demonstrate, until POOF the code comes out.

    But I find that I often need to be doing visible stuff to make progress... Like devising little experiments and running them to check my assumptions about the system (or discover something new about it), and making little incremental changes, running them, using the output to guide the next thing I do... Even occasionally spending the time to write a failing test that I plan to make pass.

    So I'm 100% on board with letting managers believe this "80% of the work is invisible" thing... But I think as advice for programmers, it's really important to not get too stuck in your head and spend too much time not kinetically interacting with the system that you're trying to change.

  • It's actually not that high-tech... Like jamming a wifi signal is basically like just shouting over someone to prevent them from speaking (or at least from being heard). To make one from scratch, you need a little bit of technical prowess, but it's definitely a beginner project... But to use one, you literally just turn it on, and maybe choose a frequency. They're widely available and cheap.

    There are pretty cool sophisticated digital crimes out there though, so take heart!

  • Opt-in is only meaningful if users can make an informed decision. I think explaining a system like PPA would be a difficult task. And most users complain a lot about these types of interruption.

    In my opinion an easily discoverable opt-out option + blog posts and such were the right decision.

    So you see, because the users can't meaningfully give informed consent, their consent is therefore uh... [checks notes] not necessary.

    Bullshit. Everyone knows that it's because if you actually ask someone "do you want to be creepy tracked, less-creepy tracked, or not tracked?" they'll pick "not" every time.

  • If your efficiency function is centered around revenue, then yeah, of course... No surprise that one of the world's most successful for-profit companies generates more profit per watt-hour than a nation, which encompasses all sorts of non-revenue-generating activity like running hospitals and keeping street lights on.