Melody Fwygon

  • 0 Posts
  • 137 Comments
Joined 2 years ago
cake
Cake day: June 1st, 2023

help-circle
  • It is likely they have the ability to sign the public key of your console with a “Suicide Key” which would signal your console to commit suicide by burning some internal e-fuse.

    It is also equally likely this is an over-broad version of “Legal Rear Armor” that means nothing explicitly about what they can do. This is because modifying your system has long carried risk of bricking and their security systems to prevent modifications have only increased in strength.

    It’s likely the new security system in the Switch 2 is so naively hair-trigger sensitive that it absolutely will brick you or disable some functionality permanently if it thinks you even so much as modified a backup copy of a save file or encrypted binary stored on your SD card itself. It’s very likely that any kind of attempt to write invalid foreign files onto an SD may result in issues. I’d expect Switch 2 systems to spontaneously self destruct if exposed to bad quality or fake SD cards with insufficient capacity; or an SD card that is failing if what I am guessing is true.

    Is this confirmed? No; it’s just idle wild speculation. But it is what I expect from Nintendo; given that their creatives have all been driven away from the executive positions of power and only money driven executives are left at the helm.

    Given that the Switch has already been thoroughly cracked; it’s likely now more than a want or need, Nintendo now has a mania or obsession with making their consoles un-exploitable. Likely, this is because they’re too naive to avoid promising their consoles are ‘unbreakable’ to their third parties and publishers.

    Unfortunately Nintendo is full of foolish pride and stubbornness. Tinkerers and video game preservers the world over will need to once again break the Switch 2 security to pieces to prove to Nintendo that this endeavor is futile.

    In the meantime; don’t tinker with a Switch or Switch 2 you can’t afford to lose. Hell, don’t even buy one if you’re sensitive to it being un-tinkerable. Don’t gift them to any children in your life either. Instead; gift them something more useful; like teaching them how to emulate one of the older Nintendo Systems and gift them a Library of ROMs so they don’t have to torrent it themselves and ‘give the family computer a virus’ or ‘cause a scary letter to be sent to their parents’ with their inexperience. If you can’t bear piracy; then go pick up one of the old legitimate retro systems. Buy it somewhere used and pick up whatever used games you can for them at any occasion.


  • Given the absurd number of sites that require a login for no discernible security reason at all whatsoever; I get it.

    A “Common” password makes sense. This password should never be used to log into or protect anything secure however.

    Similarly a “Common” password might be used to enable login more easily from certain devices; but ideally this “temporary” password should probably be something that is, yet again, different from the first “Common” password you use.

    It boggles my mind that someone like this isn’t at least using a specific passphrase for secure work accounts only.

    While I can personally understand a need for some password reuse across multiple domains; at least there should be some separation of larger “superdomains” such as “work”, “personal” and “throwaway” so that breaches don’t have such a catastrophic impact.

    A system of generating secure, unrelated but memorable phrases (for you) for those times you can’t carry or use a password manager is frequently essential. That way you can recall the password on the fly when it is asked of you; all you need to do is think about the unrelated thing you attached that information to.


  • This is mostly useless to me; I already enforce all tabs into unique containers to isolate browsing and website contexts from one another; while still allowing me to make exceptions to the rule and “unbreak” things if that’s causing an issue, but still keeping things isolated from the rest of the browsing.

    As for Tab Management; I use two windows and a plugin; Tab Stash Plus; which collapses tabs I stash into a bookmark.

    Every so often when I reach a critical mass of tabs I personally go through them and play “Keep/Toss” with more odds on Toss. Only useful tabs get stashed and are then searchable from the plugin.

    In general; since this feature now presents a possibility of an extremely UNWANTED AI integration I will be setting the config to off and leaving it off…using a relevant config policy tool or plugin to enforce this to off if needed. I hate AI features that I didn’t ask for and this one definitely doesn’t seem like it’s going to be helpful nor compatible with my current workflow.



  • No; it’s not inarguable.

    I do feel that some minor limitations around social media should exist; such as hours of the day you may not be allowed to read or post; but they should be simple age-gates created to privately verify a person’s age via a simple SSO/OAuth style token. If you can’t authenticate against some privacy respecting identity proving entity you probably aren’t old enough and any account(s) you create would be limited.

    Not all social media needs to be age-gated either; but social networks could be forced by law to avoid monetizing your account or habits at all if you don’t willingly identify. (and by doing so; also CONSENT TO THIS MONETIZATION) In short; if you are not verified they’re required to assume you are a child and handle your data as such…with utmost respect to your privacy.


  • All that being said; I’m going to be watching carefully.

    I still think they have time to backpedal, make it right, and clarify. I don’t permit my installations to talk to their data collection services anyways; via network policies. I have no problem tightening those screws and forcefully disabling their telemetry in other ways as well.

    If I have to migrate; well; I already have LibreWolf installed. I might try a few other forks next; to see which ones ‘just work’ with the web properly to protect my privacy while still allowing all websites to work properly as intended so long as I give that website appropriate permissions as I see fit.


  • I don’t believe that anyone misunderstood the wording.

    The problem lies within the broad meaning of the chosen words. If you are angry, you have absolutely every right to be.

    Regardless of Mozilla’s intent here they have made a rather large mistake in re-wording their Terms. Rather than engaging with a legal team in problematic regions; they took the lazy way out and used overbroad terms to cover their bottom.

    Frequently when wording like this changes it causes companies to only be bound by weak verbal promises which oftentimes go out the door whenever an executive change takes place, or an executive feels threatened enough.

    Do not be deceived; this is a downgrade of their promise. It is inevitable that the promises will be broken now that there is no fear of a lawsuit. There’s nothing left to bind them to their promises.

    The Mozilla foundation wasn’t ever intended to remain “financially viable”; it was supposed to remain non-profit. They should be “rightsizing” and taking pay cuts instead of slipping a EULA roofie into their terms of use.


  • It is not only true; it is required by the WMF. Wikipedia and Wikimedia will go dark before it compromises those values.

    Wikipedia can always be revived by it’s massive worldwide community; on Tor even. Trump taking down the WMF servers won’t help; the databases probably get backed up daily and would likely end up on torrents within moments of it being taken down.


  • As an editor with advanced rollback rights on Wikipedia; I can agree with the above statement.

    It is Extremely Difficult; even with slighly escalated rollback rights such as mine; to push an agenda on Wikipedia.

    WP:NPOV is a good read and the editing community and contribution culture on Wikipedia enforces it strongly.

    EnWiki itself for certain has some very strong Page Protection policies that prevent just any editor from munging up the encyclopedia or changing history.

    It’s safe to say that Wikimedia cannot be bent or broken easily by special interest groups…Vandalism and PoV pushing is quickly quelled by sysops on Wikipedia. There are more of us editors than Elon could ever possibly hope to take on.

    Not even Elon Musk gets to ignore Wikimedia policies. That will never change. They are written in blood and sweat and cannot be manipulated. The entire foundation is set up in a way that it always, eventually, cracks down on corruption and greed. Not even a cabal of admins, bureaucrats and Wikimedia Stewards can help you.



  • I suspect they probably do far more than their title lets on; but damn that’s an extremely unfortunate title to have. I can’t imagine that particular part of the title sells well on the resume.

    That said; I think numbers 2 through 5 could probably see their pay halved or cut by a third and they’d still be fine. I wouldn’t push anyone below 200k though. I didn’t suggest the Chairperson because it appears that Mozilla isn’t actually paying them, some other entity is doing so and it’s being reported here for “tax purposes”.

    Note: This isn’t to suggest that they need to cut these folks’ pay right now; it’s just observing where Mozilla might reduce spending if it were to become necessary to keep things going for them. I am actually assuming good faith that each of these folks are well worth their current pay.


  • Hearing this sort of law go into effect just makes me sadly want to ban anyone from the UK from my small communities.

    I’d hate to be forced to do it; but I certainly would immediately start swinging the hammer with IP range bans and banning anyone who is clearly professing to be from the UK.

    Unfortunately the kind of laws they’re trying to pass do nothing to fix whatever problems they have Online; and are basically meaningless political posturing. I feel sorry for people in the UK and strongly recommend they start using VPNs; as it’s the only way to ensure they won’t get snared up in the ensuing waves of bans when compliance with the OSA law that they let get passed is mandatory

    The shoe is clearly on the other foot. It’s not so easy to manage when politicians are allowed to get so uninformed that they go out of their way to pass bad laws.


  • If I can’t buy it, and own it, for a reasonable price - Piracy is acceptable. Copyright holders are required to sell/license their product in an accessible and reasonable manner in order to assert their copyright over consumers.

    If I can’t legally obtain a copy for a period of time longer than a year - Piracy is acceptable. Withholding copyrighted products to make them artificially scarce or to manipulate sales of other products is the same as the previous scenario; it is a failing to sell your product in an accessible manner.

    If the only manner of sale is ‘a streaming license of the content’ - Piracy is acceptable. If I cannot go to any retailer and buy a physical copy legitimately, expect users to ignore unreasonable terms of sale to access their content in a format of their choosing. This physically sold copy may be reasonably more expensive than the digital license edition; but not over significantly in excess of the cost of box/media/cover art. Make a profit; not a mint.

    If the only version of physical media is over-encumbered with Rights Management or other digital restrictions - Piracy is acceptable. Sold physical copies must be playable on any compatible device as determined by the media format with minimal exceptions. We shouldn’t need to connect our BluRay players to the internet every month to pull fresh certs down and lose the ability to play new BluRays when the player runs out of cert storage or becomes unsupported.





  • I am glad to see it when the selfish people at the top fall so far down the hill. They orchestrate their own falling typically, much like Ikarus in his waxen wings, falling when he flew too close to the sun in direct sunlight at the height of a hot summer’s day.

    As for Google; I hope the DoJ not only pulls up all of the resultant weeds in the garden, but also makes sure to till and salt the soil thoroughly, so that no part of Google can ever hope to rejoin it’s other pieces to form a monopoly or ‘anything like a monopoly’ on anything, ever, again.

    Google must rightfully suffer a most painful and enduring ‘Corporate Death Penalty’ so to speak; in order to ensure that no company ever gets so bold again. We must also repeat this with several other large companies like Microsoft, Amazon and Apple too; as well as a few other companies I’m unable to name because I’m unaware of how ridiculously massive and monopolistic they are.


  • This is exactly the kind of task I’d expect AI to be useful for; it goes through a massive amount of freshly digitized data and it scans for, and flags for human action (and/or) review, things that are specified by a human for the AI to identify in a large batch of data.

    Basically AI doing data-processing drudge work that no human could ever hope to achieve with any level of speed approaching that at which the AI can do it.

    Do I think the AI should be doing these tasks unsupervised? Absolutely not! But the fact of the matter is; the AIs are being supervised in this task by the human clerks who are, at least in theory, expected to read the deed over and make sure it makes some sort of legal sense and that it didn’t just cut out some harmless turn of phrase written into the covenant that actually has no racist meaning, intention or function. I’m assuming a lot of good faith here, but I’m guessing the human who is guiding the AI making these mass edits can just, by means of physicality, pull out the original document and see which language originally existed if it became an issue.

    To be clear; I do think it’s a good thing that the law is mandating and making these kinds of edits to property covenants in general to bring them more in line with modern law.


  • Keybase is better than Signal. You may not like it’s current owners but it still works, still functions, and can be used to chat privately. It’s entirely OSS on the client side; and server-side software isn’t provided; but with an open Client; it’s likely trivial to reverse and re-implement your own. (Keybase itself doesn’t provide their server code; it’s private due to abuse constraints)

    Keybase is End to End Encrypted. It may not be as “feature rich” but all features are private.

    I’m not sure if it’s indev anymore though; and it does allow you to be as public or as private as you’d like to be about your identity.