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/)N
Posts
2
Comments
577
Joined
9 mo. ago

  • Ok, first off, I agree that limiting it to the OS that comes preinstalled on a computer would be a much less ambiguous way to write it. However, I think they're actually trying to prevent more egregious means of age verification by saying "if you get this signal, you will use it, you will not use anything else, and if you stick to that you're in the clear", so having it apply to all operating systems actually helps.

    The crux if the matter then is what is an operating system, who is the developer, and what does it mean to licence it? In your example you talk about publishing your code in a git repository. Whilst there doesn't seem to be any language in the bill clarifying this, and I am, very much, not a lawyer, it seems to me that there us a difference between publishing source code that can be compiled into an operating system, and publishing an operating system. You cannot just load the source onto a machine an have it run, you need to compile it and build it into a usable image first. From that I would say that the operating system is the compiled artefact, and so the developer and licensor of that is whoever built the image, and the controller is obviously the person who put it on the machine.

    That would mean that you are free to publish the code, and only those who package it (likely either the end user or a company that sells OSs) would have to concern themselves with implementing the user age bracket flag.

  • Actually the bill seems to address those points adaquately.

    The requirement to collect the user's age bracket at account creation, so no accounts means no account creation, so no requirement to collect the flag. If FreeDOS or your new OS has no accounts but does have an app store, then I think you could collect it on first use without trouble.

    If you were developing an FOSS OS I think you could make a good arhument that you were not the “Operating system provider” as you don't control the opperating system on the end user's computer, and had no control over them installing it. That would leave the Californian end user to handle it themselves.

    If you read the bill itself it actually looks like it's designed to minimise the risks associated with age gating, and provides various get out clauses that mean that app designers can avoid collecting intrusive information and must instead rely on what they're told by this flag. Without something like this, developers instead need to rely on third parties like Persona that use ID dicuments and videos to validate users, and then, inevitably, get hacked.

    As I said before, all if this is based on the assumption that age gating will happen, and that is looking like a certainty. Given that, I'd much rather have laws like this than ones requiring privacy destroying and intrusive checks.

  • The bill is pretty clear that the user just has to provide their age bracket, there's nothing about validating it, so no webcam required.

  • Working on the assumption that some form of age gating for things like app stores and web sites is coming (the rights and wrongs of that are a separate discussion), I actually quite like this bill as probably the least harmful way to do it.

    The bill itself doesn't say that the OS should validate the user's age, just that it should:

    Provide an accessible interface at account setup that requires an account holder to indicate the birth date, age, or both, of the user of that device for the purpose of providing a signal regarding the user’s age bracket to applications available in a covered application store.

    Similarly it must:

    Send only the minimum amount of information necessary to comply with this title and shall not share the digital signal information with a third party for a purpose not required by this title.

    So you set a flag (under 13, 13 to 16, 16 to 18, or 18 plus) when you create an account on your OS and that's all third parties see. They also can't request more information:

    A developer that receives a signal pursuant to this title shall use that signal to comply with applicable law but shall not do either of the following:(A) Request more information from an operating system provider or a covered application store than the minimum amount of information necessary to comply with this title.(B) Share the signal with a third party for a purpose not required by this title.

  • Your respose is a perfect example of how wrong the left wing response is to this sort of situation. You've been handed two pies, one is undercooked, the other literal faeces. The pie being undercooked has nothing to do with the apple tree, and the other pie doesn't have any apples in it, so your response of 'burn down the tree that produced the fruit' addresses neither issue, and cuts off the supply of fresh apples for everyone until your new tree, hopefully, starts to bear fruit sometime in the future.

    If, instead, you'd said something along the lines of "lets teach people how to check their pies are actually cooked, and how to tell the difference between fruit and faeces", then you'd have been on to something.

  • It'll depend on what OS you're using. On linux you'd probably want to use sha1sum to generate a list of checksums of the files in one directory, then use it to check the other durectories and it'll tell you if any files don't match.

  • Deadly laser? The sun is not a deadly laser, for one thing the emmision band is far too wide for that. It's more of a deadly heat ray.

  • Stick to places lime !upliftingnews@lemmy.world or news sites that are tailored to showing positive stories. You already know there are terrible things going on in the world, there's no need to constantly cudgel yourself with them.

  • You beat me to it. Yes, compared to what people are used to, the face is 'flipped' in photos, which is why the selfie camera on your phone also flips the image to behave like a mirror. Most photos are from far enough away that it minimises the uncanniness of the flip, but ID photos are up close. Another thing that can be offputting is that the image is static, when people are used to seeing their faces moving. The harsh lighting for ID photos can also highlight features that people aren't used to focusing on.

  • Dedicated, single purpose, chip designs are always going to be faster and more efficient to run than general purpose ones. The question will be what the environmental, and financial costs will be of updating to a new model. With a general purpose design it's just a case of liading sone new code. With a model that's baked into the silicon you have to design and manufacture new chips, then install them.

    I can see this being useful in certain niche usecases where requirements are not going to change, but it sounds rather limiting in the general case.

  • Vim. I suppose, technically, I'd need a kernel and filesystem drivers to run it, but Vim is the one true way. (and none of that neovim heresy either!)

  • Come on, you'd be pretty excited too, if someone gave you a treat that was bigger than you! I know I would.

  • At 3am

    Jump
  • No-one:

    Absolutely no-one:

    People who are sick of the no-one format being misused: One day the “no-one:” anti-joke format will die.

  • Here's a response from piefed. Isn't the fediverse a fascinating place? We're all using different software and talking to each other.

    (It looks like the body has been partially duplicated in the title though)

  • This was a completely irrational thing to do. You'll never hear the end of it.

  • Not really. For one, how do you prove that they have expunged it from every backup, replica and server? For another, what you seemed to be concerned about was whether your creation would be used to train LLMs or otherwise be misused, all of which can happen from an "unofficial" copy that was scraped before you tried to remove it.

  • To assert that, you'd have to prove that every single copy of it, belonging to anyone, had been destroyed. If even one offline copy remains it could be put back online, courts or not

  • As others have said, "deleting" your data from reddit does absolutely nothing to stop them using it. They're not actually deleting it, just hiding it, and they'll use it in whatever way they see fit and think they can get away with. You'd think it might stop third parties scraping it and then using it, but all your posts were already scraped within moments of you posting them, so retroactively hiding them doesn't achieve anything there either.

    The rule remains: if you post something publicly, you cannot call it back. It will, or might, remain out there in perpetuity.

  • Not without permission, I hope!

  • PieFed Meta @piefed.social

    An option to be notified of responses to all comments under a a specific one

  • PieFed Meta @piefed.social

    QoL Feature Request - Have a way to avoid being auto subscribed to communities on signup