Little bit of everything!

Avid Swiftie (come join us at [email protected] )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 33 Posts
  • 875 Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle


  • Yeah reading through the bill I’m feeling better about it.

    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.

    Where an “Account Holder” is:

    (1) “Account holder” means an individual who is at least 18 years of age or a parent or legal guardian of a user who is under 18 years of age in the state. (2) “Account holder” does not include a parent of an emancipated minor or a parent or legal guardian who is not associated with a user’s device.

    The way I read this, this bill actually assumes the person installing it is over 18 and an adult. (Let’s not argue with them on that). It’s simply saying that "You need to provide a way to create child accounts, and your app stores will need to respect that).

    What I do not see is that OS’s must validate IDs or anything.

    provide an accessible interface that allows 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.

    “Mom or dad need to set the age bracket for junior so that apps rated NSFW can’t be downloaded”

    This title does not require the collection of additional personal information from device owners or device users other than that which is necessary to comply with Section 1798.501.

    Honestly, rereading it, this is how I would do age protection if I were to do it. Rereading this multiple times now, this might be the most privacy safe way to validate age, shut up lawmakers who cry “what about teh children!!!” and let us adults move on in peace.

    You buy jr a laptop, it’ll ask on account creation how old they are. That’ll be a flag they can’t modify that will be passed into browsers and app stores. That will prevent children from accessing content they can’t. Adults then continue on. Jr grows up and either buys his own device, or mom and dad swap their account to adult.


  • Interesting, it’s vague, and obviously going to go through legal hurdles. Windows, Google, and Apple will just do it. Ubuntu might, but what about Debian, or any number of server OS’s? Will users need to verify their age logging into a server? What about forks? Forks of forks? OSes developed outside of the US?

    Where this could be an opportunity, and hear me out, is that this could pave the way for privacy-friendly age checks to shut them up about “what about the children”. The bill says that all it needs to check is age - nothing else. If the OSS community can come up with a way to privacy-friendly validate age, then this whole thing could be solved. Websites wouldn’t need to store IDs, they could ask the browser who would check the OS. In fact, that might be the purpose of this bill, to curb all the “Just collect their IDs” with the websites. If the OS had a check stored securely that you’re over 18 and nothing else, then all other age checks could be cut.

    Also interestingly, it reads like they might be angling against Microsoft and Google for collecting private information on minors because “We didn’t know they were minors, how could we?”.

    I don’t like it one bit and it’s going to be completely unenforceable - and OSes like Arch will say “You can’t use this in California”, but if that’s the angle they’re trying to do, it might work.



  • Yes, that is my proposal. Many people complain saying there are better ways to host instances but no one is willing to practice what they preach and actually do it. If you want to see change in the fediverse then you should step up and do it.

    New users have a choice when joining, you should make a new instance and convince the new users why they should join. I would support a toggle on join-lemmy which lets them see what servers are geographically close, but that would be irrelevant before you set up an instance to pave the way.

    If you “can’t be bothered” then obviously you aren’t as passionate about it as you claim to be.






  • Yeah Proxmox leaves a lot to be desired in terms of metrics. However, metrics are supported out of the box. Bad news, you probably won’t get what you want within proxmox. Good news, you have another project you get to undertake! Hooray!

    Like I said, Proxmox supports metrics out of the box. If you go Cluster -> Metric Server you’ll be able to see that you can add a metric server. The first iteration I did with proxmox I added an InfluxDB container which then proxmox can talk to (yes they can be on the same host), and then proxmox will start pumping metrics into InfluxDB. (It uses Telegraf under the hood). Then, you can also run Grafana, add your InfluxDB as a data source, and then you have a sweet metrics dashboard. There are a lot of pre-built dashboards already made that look great, and you can customize from there.

    You can also use Graphite, I personally haven’t used it, but I also dropped Influx over time too. These things evolve in that sort of way. That’s how I’d get set up and started though.








  • Did a takehome for a company recently that did it well. They required that I make a docker file (you could give them one if you wanted) where when ran it would run tests. It was a neat use of docker IMO, it standardized that builds were just “build the docker file” and running was just “run the dockerfile”. You would t have to deal with tar or anything then.

    Thousand ways to skin a cat there