• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle
  • So this is neat. Potentially life changing for some type 2 diabetics, but that depends because some t2 diabetics are not failing to make enough insulin, they’re just no longer sensitive to it at a level that makes it functional for them. I suppose it’s possible that this therapy could cause them to grow enough islet β cells to overcome their lack of sensitivity, but (and I’m a type 1, not a type 2, so maybe my info is incorrect here) that lack of sensitivity can grow with further exposure to insulin making this a stop-gap at best for those cases absent other therapies.

    …and with all of that said, being able to regrow islet β cells has never really been the problem for type 1 diabetes. You can regrow all the islet β cells you’d like and it’s not going to cure the underlying immune disease that has caused your immune system to kill off all of your islet β cells to begin with. Unless you can figure out why t1 diabetes causes one’s own immune system to go psycho killer on their islet β cells, you’ve done nothing to “cure” diabetes. Without being able to suppress that impulse for your immune system to murder your own cells, any ability to replace the islet β cells is going to be temporary at best, and probably a waste on the whole.

    My brother in law is a “cured” type 1 diabetic, by virtue of his having had a kidney replacement and being on immune suppressing drugs for that. Since they were already replacing the kidney and he was going to have to take immune system suppression medications for that, they also just replaced his pancreas at the same time and the suppression of his immune system has allowed the new pancreas to thrive and continue to make insulin. Easy-peasy. The only trade-off is that he is super immunocompromised and can be killed by common colds, so not a great strategy in general.



  • If you’d like to look into it further. the +i flag in chattr is setting an attribute making the file (everything in Linux is a file, so yes this even means directories) immutable. When a file is immutable, it isn’t possible to change the ownership, group, name, or permissions of the file, nor will you be able to write, append, or truncate the file.

    It’s been a while since I’ve used it, but I don’t believe it’s possible to have an immutable directory where you can still modify the contents therein, but I may be misremembering that. It would seem unlikely since adding content to the directory should require that you modify the links for the directory, which shouldn’t be allowable with an immutable object?

    It’s possible that the +a chattr attribute may achieve what you’d prefer. I believe that flag will make it so that files (and again, everything in Linux is a file) can be created and modified, but never deleted. I’ve actually never used this one, but I can foresee how this still may not be ideal for your wishes since updates to games may expect to be able to delete old content which would be thwarted here. 🤷




  • If gaming with Nvidia hardware is your primary concern, then maybe Bazzite would suit you. It’s based on Immutable Fedora, with tweaks to give it a SteamOS like experience. It offers Gnome or KDE for the desktop, and supposedly has everything dialed in for gaming. I’ve heard a bunch about it doing great with Nvidia cards and gaming in general, I suspect that you’d be able to do everything else you might need via the desktop it provides, but I have no knowledge of how it handles multiple monitors so maybe therein lies the fatal flaw.


  • If you use a fancy official VPN client from Mullvad, PIA, etc, you won’t need this since most clients already have a kill switch built in (also called Lockdown Mode in Mullvad).

    According to the researchers

    The result of this is the user transmits packets that are never encrypted by a VPN, and an attacker can snoop their traffic. We are using the term decloaking to refer to this effect. Importantly, the VPN control channel is maintained so features such as kill switches are never tripped, and users continue to show as connected to a VPN in all the cases we’ve observed.

    Killswitches are insufficient protection since the TunnelVision attack never disables the VPN tunnel. The TunnelVision attackers are instructing your physical layer connection to route everything through a node of their choosing rather than killing your VPN connection, and since the VPN connection never drops, a killswitch will never engage. The VPN stays up, thinking it is doing a good job, but in the meantime your network interface has been instructed to route no traffic through the VPN and instead route everything to the location of the attacker’s choosing. I have heard that a couple of VPNs think their clients are not vulnerable here, but I haven’t seen independent conclusive proof one way or the other yet.

    I suspect that your “Solution” also fails to mitigate the issues in TunnelVision because it allows LAN access to the physical interface. In a TunnelVision attack the hostile has to be on your LAN (or rather the same LAN you are on since I suspect that “The coffee shop wi-fi” is the more likely network for an attack like this) already, so if they’re going to tell your interface to route traffic somewhere else, in all likelihood that somewhere else will already be in the same LAN you are and their exfiltration will be allowed under your configuration.


  • At this point they’re only wagging their fingers to make it appear as though they’re considering regulation.

    Again, it’s disingenuous to claim that their pragmatism in the face of unreasonable actors is the same as being the unreasonable actors. What are the left supposed to do? Pull a Trump and pretend that the laws and systems that make our country don’t exist and just say that what they want is law and ignore that half the country is electing morons who will fight them at every turn? That’s not how it works and frankly I wouldn’t want it to work that way because it’s just incredibly dangerous. They’re trying to work within a system where the right has learned they can con half the country into believing they’re doing their job while they sit back and do their damnedest to ensure that the government doesn’t function at all because that’s the only way that conservatives can stop progress at this point with their platforms being as unpopular as they are.


  • The left is definitely more open to considering regulation. It’s not even close. The right thinks that regulation is a four letter word and they’re generally not a fan of those either. It’s disingenuous to both sides everything. Much of the time where the left allows a carveout for vampirism, it’s because it’s the best compromise they can mange to a given end given that the right is out there swabbing their throats and getting all hot and bothered waiting for daddy Drac to come and give it to them, not because it’s their preference that we allow unfettered late-stage capitalism to destroy lives. Again, it’s disingenuous to claim that their pragmatism in the face of unreasonable actors is the same as being the unreasonable actors (and I am well aware that there are exceptions that prove the rule on both sides of the isle, so 🤷‍♂️)

    …and lest anyone think that this problem isn’t solved with government regulation, I invite you to look at the medication situation in nearly any other country in the world where by and large they are not afraid of regulation for the same drug companies that are fucking us sideways in the US and see how much cheaper and better their access to medications is solely because they’re willing to support that maybe there is a greater public good than shareholder profits.





  • I’ve dabbled with Linux on Mac hardware a couple of times and I’ve got to say that Linux DEs generally hew closer to Windows conventions than Mac ones and I found using the Mac keyboard with Linux to be a dreadful experience without the fact that the chiclet keyboards are the worst shit I’ve ever put my fingers on.

    I very quickly snagged a standard mechanical qwerty 104 key with brown switches and cursed every moment that I had to use that abominable keyboard built into the stupid MacBook. Apple seems determined to do things different for the sake of different as much as they possibly can and trying to adapt all their nonsense to the Win/Lin way of doing things made my life worse in numerous ways (most DEs have great remapping for keys and such, but it gets messy fast if you’ve got apps from different paradigms.)

    I’d very much recommend against going out of your way to get a Mac keyboard for using Linux unless you enjoy fighting against things. But hey, if that’s your kink, then a Mac keyboard with Linux would be my recommended way to go.




  • A process running as root does not need a prompt or any user interaction to do whatever the hell it wants on most (nearing ALL, but I’d be wary of absolutes with Linux) systems. I’m unaware of any means that a Desktop Environment could restrict a process running with root permissions by requiring an interactive prompt of some sort for anything. If your DE is running as root, all of its children are also running as root (unless you’ve rigged things up to run explicitly as other users) which means just about anything you are doing could be running rampant malicious actors on your system and nothing would seem amiss until it made itself evident.

    Now, it does seem unlikely that anyone has written any malicious code that would run in a browser expecting to be root on a Linux system, so that’s likely the saving grace here, but that’s only security through obscurity and that’s not much to hang your hopes on for any system you care about.





  • Your Mastodon data is already an open book to Meta if they care to have it. The protocol is open, they could already be black-ops scooping up everything that’s fit to federate without turning on Threads federation, so them doing that really changes nothing. And what I mean by that is that they could already have set up unknown instances to leech whatever data they want out of the Fediverse, which instances masquerade as normal mom and pop installs just federating and sucking up everything without bringing anything back to the table. There’s literally nothing stopping them from leeching everything out of the Fediverse at any time other than people being better at detecting their activity (and actively thwarting that activity) than Meta is at keeping it off the radar.

    In this case they’re making it so that I might have a chance to follow and interact with people already in the Meta/Instagram/Threads atmosphere without having to convince those people to leave the confines of what they’re comfortable with and find a Mastodon instance to sign up for. Maybe they’ll be more comfortable with leaving Meta after dipping their toes in the open spec?

    How is that not a win? If Meta/Threads decide that they want to fracture the protocol and go do their own thing later, so what? We’ll go right back to where we were before they brought their users into the Fediverse. If people decide that they value the Threads extras/connections more than they value the purity of the ActivityPub protocol then maybe Meta is actually providing something that matters and we’ve lost by not supplying that need before the corporate interest figured out that it existed. In that case we’ll deserve the death that causes in use of the open spec, but the open spec will still be there and people who want to do their own thing with it can’t be stopped now. The code to run an open ActivityPub Mastodon instance is already out there and it’s impossible to take it back now.

    Everyone is out here decrying this as a subtle takeover of the Fediverse by Meta, but did Facebook “takeover” the HTTP spec when they started operating facebook (dot) com on the world wide web over the HTTP protocol? It’s an insane assertion. I’ve been running my own opensource web servers since well before Facebook was a thing and I’ve continued to do so despite most people opting to depend on a mega-corp to be steward of their online presence. That Meta has a very successful and popular website that I’ve never been a fan of has never impacted my ability to use the open protocol they operate on to continue doing my own thing. The same thing will be true here.

    It really seems like people are just upset that Threads might bring ActivityPub to the mainstream and force them to contend with the realization that a diaspora of open spec implementations already lost the war to Meta/Facebook. We had that once before. It was called the World Wide Web and you could go and find forums, fan pages, company websites, and everything else back then that has since moved to Facebook (or other content aggregator sites) because people value the network effects and homogenization more than they care about one big company being in charge of it all. (…and not to belabor the point, but most of that stuff is still out there, it’s just waned in popularity because the network effects are not there.) Here we are with a chance to try and break things out again and people are seemingly worried that we can’t if we let the Meta users in? Maybe they’re right, maybe it’s impossible to achieve victory here, but gatekeeping the standard and enacting some purity test for which providers are allowed on the protocol isn’t going to tip the scales in favor of the open standards implementation.

    If the protocol is truly open, then how can a corporation embracing it be a danger? We’re all free to adopt any changes or not at any point in the journey so it’s impossible to lose, you’re free to keep doing your own thing any way you look at it. Tell me how any of this is untrue.

    TL;DR: Threads coming to the Fediverse is a good thing. It’ll make it possible to expand the network effects of an open protocol far faster and more than any amount of Fedinerds proselyting the gospel of ActivityPub ever will. The only thing that is at risk of being lost is that we’ll refuse to adapt to what end users want fast enough to keep a large corporation from bending the spec to their ends. Which loss again only means that you’d be cutting yourself off from those who WANT to embrace the revised spec by not adopting those changes yourself. That option (to just not adopt changes to the spec) can’t be taken away from you in the future, so worrying is only warranted if you feel like your ideal ActivityPub implementation can’t win out in the marketplace of ideas and that you’re owed that victory even if others are able to expand it in ways that people actually want to use enough to dismiss whatever downsides it contains.