Skip Navigation

User banner
Posts
0
Comments
1,670
Joined
2 yr. ago

  • So did I up until windows 10, which makes sense because my laptop that had run windows 8.1 had been upgraded from Windows 7 and had the issue every time it seems to have a version release. My windows 10 system was a factory install since I switched to a PC instead of a laptop at that time, and as such ran UEFI out of the box, I haven't had any issue with windows nuking a boot partition since.

    I'm assuming it's because bios boot still uses an MBR which means the actual boot record is at the beginning of the disk, which windows also tries to use for recovery and its boot. With GPT setups like how UEFI requires, there's a dedicated partition that is used instead for storing EFI files, so it allows for a much clearer co-existence.

    Basically if you are running a UEFI system, there's no excuse for Windows to actually nuke grub anymore, because the entire reason it was nuking it in the first place was it was overwriting the MBR at the beginning of the disk so the system no longer knew where grub was. With UEFI the system boot would be the UEFI loader -> windows loader or grub (or like how my system is brokenly setup UEFI -> grub -> windows because I like the traditional style of selecting windows from grub)

  • that's the fun part! you don't 🦊

  • Yeah, I was gonna say I dual boot and I can't recall the last time that Windows nuked my UEFI bootloader.

    But back when Windows still did BIOS boot, it was like every major release without fail.

    edit: Rewreading your post it sounds like you meant updating the BIOS as a whole and not BIOS boot, so that's my bad. Yeah, I definitely haven't seen your circumstance, I had that happen consistently before Microsoft embraced the UEFI style booting

  • fully agree, mine isnt accessible to the outside world either but, you never know if something gets missed or somehow a path gets made. would rather not open up that risk

  • Sadly no recommendations, I still use portainer myself

  • while docker does have a non-root installer, the default installer for docker is docker as root, containers as non-root, but since in order to manage docker as a whole it would need access to the socket, if docker has root the container by extension has root.

    Even so, if docker was installed in a root-less environment then a compromised manager container would still compromise everything on that docker system, as a core requirement for these types of containers are access to the docker socket which still isn't great but is still better than full root access.

    To answer the question: No it doesn't require it to function, but the default configuration is root, and even in rootless environment a compromise of the management container that is meant to control other containers will result in full compromise of the docker environment.

  • man, arcane looks amazing, I ended up deciding off it though as their pull requests look like they use copilot for a lot of code for new features. Not that I personally have an issue with this but, I've seen enough issues where copilot or various AI agents add security vulnerabilities by mistake and they aren't caught, so I would rather stray away from those types of projects at least until that issue becomes less common/frequent.

    For something as detrimental as a management console to a program that runs as root on most systems, and would provide access to potentially high secure locations, I would not want such a program having security vulnerabilities.

  • Regardless of my opinions for it, it'll be a societal requirement with the advancement of technology unless we wish to move away from a monetary based system.

    I personally am fully for it, I am concerned about the productivity drop if it is implemented too early, however such a system needs to exist for continued societal functionality.

  • it wouldn't matter sadly. the program changes the pin on the device, the only solution would be a factory wipe and restore from backup if it's given full access.

  • wait can it? I thought most resets nuke the keystore to prevent the decryption key from being seen. Thats concerning.

  • agree, why I mentioned that in the post. Still doesn't change the outcome that it degraded the channel which was why I used it as an example.

  • yea you have it yes, if they have confirmation that you had said evidence, and they were seizing the device to collect more evidence regarding it then it would be obstruction of justice and destroying evidence, but they need to be able to prove that claim. Unless they can prove that claim then it's an unlawful search (excluding port authority specific laws regarding searches because checkpoints generally have reduced restrictions on lawful searches)

  • The exact circumstances around the search—such as why CBP wanted to search the phone in the first place—are not known

    until this isn't an unknown it's impossible to voice opinion on the legality of this action. If they had evidence that there was something incriminating or against the law on the device and can prove the user intentionally destroyed the info to impede the investigation(honestly this last part is fairly easy as long as the first part can happen) then yea what he did would defo break the law, but until those aspects can be determined this seems like a massive abuse of that persons 1st(due to activism), 4th (due to the seizure of private property without a lawful search), and 5th(again private property) amendment rights.

  • as an ammendum to this comment edit, catfriend edited the post linked and added this to the end

    Edit: Regarding @nel0x , they did not have any history with the Syncthing (Android) project nor an expressive public profile when they applied to take over the Google Play Store entry in Feb 2025. I accepted this and transferred - believing in good will and we agreed on their task to be publishing what was on my repository to Google Play after their review. If they now desire to make their own app, there is, unfortunately no way to clean up the confusion caused if it is called the same other than kindly asking them to rename it.

  • they are claiming the man is in violation of title 18 section 2232 for inputting what seems to be a duress pin that initiated a wipe on the device when they tried to seize it.

    said section does not talk about reasoning for searches though, it uses the terms "lawful authority" which in my eyes indicates that the search as a whole was lawful in the first place. It happend at a port authority though and those generally have weaker protections for citizen rights.

  • the claim they are making is that the user inputted a duress pin at the port, i was under the assumption that they actually need to have evidence that something was there in order to claim destruction of evidence, I'll be curious to see where that case goes. It sounds like it was a routine search with no objective.

  • Degraded as in opinion or actual metrics?

    If it's opinion I feel most channels naturally degrade over time as the broadcasters personality changes with the popularity increase.

    My largest case and it's a likely a controversial take would be Markiplier. When he hit fandom he all but left the youtube lets play field in favor of other opportunities(which to be fair he was fully upfront with before he did it), then after months of almost no activity he came back with a different personality. (somewhat like how Jack did when he did his rebrand but was more noticeable). My eye opener to it was his GTFO series, I don't know of a good way to put it, he seemed super offputting and mean/childish to the people he had gamed with for years. I know it was likely meant to be a bit but, after an extended inactivity in the genre and then coming back and acting like that it was whiplash. He also seems to really be putting his fandom/viewer base on the side burner with everything, he hasen't posted regular videos in a long time(I expect it's due to his movie that he's putting his heart and soul into) and it's made it so I no longer get recommendations to any of his content since his channel has fallen off the algorithm for me. Like don't get me wrong, I still like his content(when he releases it), and he's been clear that youtube was a stepping stone for him and that his passion is in other areas but for the sake of the question I feel the channel fits.

  • yea it makes it so much easier since there's only one user in the system anyway so makes no sense for everything to be installed system level

  • The majority of my development work is on chat bots or sites so I've always just used bot as the name

  • further more the opencollective project hasn't seen an expense report for development since july of 2024 only domain renewals. so it's not like they are working behind the scenes and just haven't pushed anything to the gitlab (which also hasent seen any real development activity since july 2024)

    edit: I just saw this on their blog.

    Personally I will not do any more work on Manyverse. And my impression is no one else is planning to either. At most I might do a patch release (no features/big bug fixes) to wrap up a grant. The codebase could maybe keep living in a fork where the backend is swapped out with some other protocol, but this is a big project which would probably lose backwards compatibility with the current SSB main network, and I don't think this is very likely to happen. Personally if I'd work on a P2P app now it'd probably be a (comparatively) "smaller" project, like a chat app or similar, using a newer protocol.

    so it sounds like the project is essentially dead