Skip Navigation

帖子
1
评论
2733
加入于
3 yr. ago

  • A windows sysadmin does not need to be granted the authority to alter or disable the binary blob that performs the age verification. Microsoft can restrict that access and maintain control over that aspect of the OS. As they will be held liable for allowing it to be disabled, they are not likely to do so.

    Canonical cannot compel a similar restriction in its users and sysadmins, due to the FOSS-ness of the software. They cannot be held responsible for what that sysadmin does with their software. The sysadmin, then, becomes the OS Provider.

  • They control the OS the same amount under either windows or Linux.

    That is false. The Windows sysadmin does not fully control the binary blobs of the OS, including (presumably) the blob that performs this age verification process. If Microsoft is going to be held responsible should that feature be absent, Microsoft is not going to allow that feature to be disabled, unless responsibility for compliance transfers to another "OS Provider". This restriction is well within Microsoft's power and control: they do not grant full and total control of the OS to the end user.

    The age-signaling apparatus will be well within the the Linux sysadmin's control. This is simply the nature of FOSS. The Linux sysadmin can't be stripped of that control: they control the source code to the OS. They always have the power to determine what functions their OS will and will not perform. Their decision to use such an operating system qualifies them as a "developer" under this law.

    But it isn’t like Canonical and RedHat are just some guy in a basement - these are commercial entities developing and licensing software just like Microsoft.

    Canonical produces a version of Ubuntu with the age signalling apparatus. A California sysadmin installs it on a child's computer and removes or bypasses the signalling apparatus. Is Canonical still the OS Provider?

    What if he doesn't disable it, but a bug in the age verification app causes it to fail. Canonical puts out a bug fix in an update, but the sysadmin's update policies block that update. Canonical can't force an update in the way that Microsoft can. It is the sysadmin's choices that are preventing the patch from being applied. Is Canonical still the "OS Provider" under this law? Or is the sysadmin the responsible party?

  • This bill makes the operating system provider the responsible party. They have to implement this, and ensure compliance. Failure is a $2000 fine every time a child launches an application.

    Under this law, Microsoft and Google are charged with implementing this feature and ensuring compliance. They are, obviously, "OS Providers". They control their respective operating systems.

    With FOSS OSes, Ubuntu isn't the OS provider. Arch isn't the OS provider. Debian, Redhat, Gentoo aren't the OS Providers. The product each of these entities provide is an OS, but it is an OS that is under your full and total control. Not theirs. They cannot control what you do with the OS. They cannot ensure your implementation is compliant with state, local, national, or international law. Under this law they are not the responsible party.

    Under this law. You are the "OS Provider".

  • This law keeps Linux out of schools and businesses. Google and MS are "Operating System Providers" and would be the responsible parties under this law.

    If a school sysadmin decides to adopt a Linux desktop for his school, that sysadmin becomes the "OS Provider": they have full and complete control over the OS; they are fully responsible for everything that happens with it.

  • Even if Linux offers the option, school districts won't use it. The district itself will be considered the "OS Provider" under this law, if they choose to use a FOSS OS. They have complete and total control over the OS. That makes them liable, rather than leaving that liability with Microsoft or Google.

    This sort of regulation violates the first amendment right to speech, the first amendment right to free association, antitrust, and a whole shitload of really good law.

  • I just scrolled through about two dozen comments in your recent history. Every single one focused on banning and blocking content in the fediverse.

    Do you ever actually participate in the discussion?

  • It's hard enough trying to get Linux adoption in schools and businesses. This law makes it an additional liability.

    Administrators of FOSS systems will be considered OS Providers under this law, and will be liable at $2000 to $7500 for every child they expose to a non-compliant OS.

    Those few schools that have adopted Linux will be forced to switch to M$ and Google products.

  • This is a gift to Microsoft.

    This law only applies to computers used by children. The law explicitly defines "users" as minors. It does not apply to machines used solely/primarily by adults. It does not apply to servers, or other machines with no local users. It won't affect the tech industry directly.

    This law effectively prohibits your children from (legally) using anything but Microsoft/Google products until they are 18.

    With this law, Linux cannot be installed on a school computer. With a FOSS OS, the local systems administrator would be considered the OS provider, and would be liable under this idiot law.

  • For the next year or so.

    State law in California (and soon, Colorado), as well as UK and EU laws, are beginning to require OSs to spy on users and developers. Privacy-focused Linux and FOSS software will soon be deemed illegal in these jurisdictions. Which will make it a liability for companies, and force them back to shitty commercial offerings.

  • I think you should actually read your link:

    This apostrophe form of the possessive remained extremely common throughout the 17th century and was used by the likes of Thomas Jefferson and Jane Austen. The version without the apostrophe only became dominant in the 18th century—probably because it's was taking on a new role, replacing the contraction 'tis.

    It would be simpler, of course, if there were only one form in use, and there's an argument to be made for using it's in all cases; 's serves both purposes just fine for nouns. In the cat's bowl it signals possession, and in the cat's sleeping it represents the contracted verb is.

    The "its" construction espoused by Messrs. Merriam, Merriam, and Webster was a satirical attempt at formalizing an exception to the possessive rule rather than acknowledging a typographical error in an advertisement for their new dictionary. That satire was lost on the general public, and "its" was born.

    Your commitment to their 250-year-old joke is laudable, but the joke itself has run its course. "Its" was never actually a word. It was always a typo.

  • There is no such word as "its". That archaic usage was an exception to the "appostrophe-s" construction used to indicate possession. Deprecating that usage eliminates that unnecessary rule exception. While abandoning this antiquated rule does create a homonym, the contractive or possessive meaning is clear in context, as your criticism clearly demonstrates.

    "It's" is both the contractive form of "it is/was" and the possessive form of "it".

    Only English teachers and similar obnoxious, gatekeeping pedants mourn the loss of "its".

  • Thank you!

    I should stress that my explanation is a gross simplification, and some of my examples might be a little off. Further, the specific role varies from jurisdiction to jurisdiction.

    The key takeaway: The role of the coroner is (generally) closer to that of the prosecutor than it is to that of the medical examiner.

  • I think you're misunderstanding the role of the coroner. The medical examiner looks solely at the corpse to determine cause of death. The coroner examines the broader conditions and circumstances surrounding the death.

    To understand the difference in the various investigative roles: The medical examiner can determine that the fatal injury was a hammer impact to the back of the skull. They are not legally qualified to determine whether that hammer was swung, dropped, or thrown. They aren't even qualified to determine if a particular hammer was the cause of death.

    Forensic pathologists can determine the particular hammer, and whether the hammer was swung or thrown. They are not legally qualified to determine who threw it. They are certainly not qualified to determine why it was thrown.

    The coroner can determine who did the throwing. They are not legally qualified to determine whether the act of throwing the hammer was justified or criminal. (If it was thrown to stop the deceased from attacking a victim, for example. The coroner is not qualified to make this determination.)

    The trial court can legally determine that the hammer was thrown with intent to kill. The criminal trial court can determine if that intention was justified or not; whether the defendant committed a crime. The civil trial court can determine how much harm the victim's family has suffered.

    Another example, this time drawn from real life: in the Triangle Shirtwaist Factory fire, the medical examiner can determine that the deceased died from smoke inhalation. The medical examiner cannot determine who is responsible for the fire. The coroner can call for an inquest. They can convene a jury. And they can legally determine that responsibility for the fire lies with the owners.

    There is no particular need for a coroner to be medically licensed, provided they are not personally expected to perform an autopsy. Where they are not medically licensed, they cannot conduct their own autopsies, and must instead rely on medical examiners for that one small piece of evidence.

    It would be more appropriate for a coroner to be licensed to practice law, rather than medicine.

  • Which one? Israel or Trump?

  • They can't get around it for private employers, but state and local governments are employers and perform withholding.

    The state could also enact a job placement program, and function as a temp agency: the worker is the employee of the temp agency, not the client company they are contracted to.

  • I understand and agree with the hate for the play store, but why the focus on f-droid in particular? There are a multitude of other repositories, or you can grab the apk from anywhere else.

    F-droid is great, for now. But it is still a centralized resource, and it is perfectly capable of enshittification.

  • The taxpayer is paying their federal taxes. The money is being withheld on their behalf. They are receiving a W2 stating their earnings and withholding. Their employer is properly filing, but they are not sending the money they claim to owe.

    If your employer does all this, the IRS can't blame you for not paying your taxes. You have proof that you did. The IRS can't sue all of the company's employees for the company's failure to pay. They have to go after the company, not you.

    They could even do it legally. If the state won a case saying the federal government illegally withheld Medicaid funds from the state and its citizens, the state could get an order to seize federal assets, including employee withholding from state workers.

  • You're not quite right, but I'll reply there instead of here.

  • Most people don't pay their taxes directly; they are withheld from their paycheck by their employer. State and local governments are employers; they withhold taxes from their employees. They can report that they have withheld those taxes from the taxpayers, but transfer those taxes to the state treasury instead of the IRS.

    The state could create a jobs placement program that operates like a temp agency. Workers participating in the program are employees of the state, not the business they are contracted to.

  • No Stupid Questions @lemmy.ca

    Anyone know of any interesting, money-making hobbies or flexible gigs?