An excellent argument to be made when arguing about the
STop Unrelated Crap Killing budgets act.
STUCK(b) Act. See? Even has a cool acronym.
And if they take a few dozen sessions deliberating over it while the government keeps funding and running on previous bills, that’s OK. That’s the point. There should not be an easy path to leverage government’s ability function to force a vote in your favor, bypassing traditional debate, compromise, and processes.
+1
Can’t even open the appearance menu. iOS 18
Was also forced to log-in again after the update. Related?
Y’all need to get a word in with your representatives that what’s needed is legislation preventing budget bills from containing anything other than budgets.
That would solve this problem real quick. It’s been sounding stupider and stupider using the budget meeting to force unpopular agendas down throats or else the government is held hostage.
I think it would fit the bill if budgeting was held up over allocations, one side wants more border spending, one side wants more educational spending, etc, that would make sense but “allow us to attach this whole other unrelated law to declare the sky is actually green(which also contains a tag along that I get to be emperor), or nobody gets paid” is just ridiculous.
Tomorrow? Oh, so you already forgot the announcement from last month? Well, I mean I guess we have a lot of our own stuff going on right now…
/s?
Yup. Or anything held against them is now just fakery.
Sometimes it feels technology may doom us all in the end. We’ve got a rough patch in society starting now, now that liars and cheats can be more convincingly backed up, and honest folk hidden behind credible doubt that they are the liars.
AI isn’t just on the path to make convincing lies, it’s on the path to ensuring that all truth can be doubted as well. At which point, there is no such thing as truth until we learn yet a new way to tell the difference.
“They don’t need to convince us what they are saying, the lies, are true. Just that there is no truth, and you cannot believe anything you are told.”
Worse than that, the slot they left is also locked out for a year. Although you can return to your previous spot freely, so break up and make up is fine.
I get why, if it were too flexible publishers would fear sales loss and opt out en masse but still feels rather long.
One thing I can think of is an overzealous corporate security solution blocking or holding back your email purely for having an attachment, or because it misunderstands/presumes the cipher-looking text file to be an attempt to bypass filtering.
Other than that might be curious questions from curious receivers of the key/file they may not understand, and will not be expecting. (“What’s this for? Is this part of the contract documents? Oh well, I’ll forward it to the client anyway”)
Other than that it’s a public key, go for it. Hard (for me anyway) to decide to post them to public keychains when the bot-nets read them for spam, so this might be the next best thing?
Are you installing needed libraries?
For example, the installer runs because it doesn’t need any, but then your app needs say VCRedist 2010, and so won’t until run until you add the vcrun2010 extra library with Winetricks or the menu in Bottles.
The way I understand it, I think the real issue here is that Proton Drive should clear the sync state or identity when uninstalled. The identification of the PC should be unique to each install, so that when you reinstall it later it understands that it is now a “new” system needing to be reworked from scratch, and that the empty folder is awaiting initial download, not mass cloud deletion. Would that lead to multiple copies in the “Computers” backup section? Sure, but that can be a good thing too, or at least better than wiping the drive, and more easily remedied.
I wonder if Proton could shave off some work hours by just putting the API team in contact with the RClone backend developer, or by contributing to it.
I get the feeling even if Proton released a drive app for Linux, all but the most casual users will just be waiting for when RClone learns from it and improves.
What happens next? A wave of even worse disregard for things.
After all, if we can bring back the mammoth, who cares if we off <insert species here>, they’ll just bring it back next rotation. /s
I enjoy it, but I feel like it’s something they could do more with and don’t.
Maybe one day they’ll find other ways to sneak it into new content, like the Necramech. That was also interesting but underwhelmingly supported, and now they try to squeeze it into places to make it relevant. But it still feels like it needs….more.
Oh, and who remembers Fish Team? I don’t even know if that feature got added, I avoid the Lich stuff.
It’s not really because it fell over. It’s because it wasn’t supposed to fall over. Consumable launch materials don’t contend with this because failure to return is a success. This is a failure. This must be learned from and fought against/prevented going forward.
Being an instant nuclear fusion epicenter aside, you’d be blind from the lack of light moving off things and into your eyeball, how would breathing work with immobile gasses, etc etc.
RClone? I understand it’s a bit hacky but it works well for me in testing and is a generally accepted option for cloud storage of all kinds on Linux.
Since you mention setup instead of any manual install screwery, I’d say root(uid 0) is still very real, you just didn’t setup any login for it. Every time you sudo (substitute-user-do), you(probably uid 1000) are running that command as root instead of you. In fact, just sudo -i and you are now “logged in” as root.
Edit: Missed the context. Should still be useful info but you probably are not accidentally remoting into an account you never setup the login for.
Raspbian is sometimes a compromise between security and usability, because it is designed to go into the hands of new users. It also used to ship with a default “pi/rasberry” login hardcoded and IIRC permitted root password login over ssh. Things experience users change or turn off, but needs to start friendly for the rest, you know?
By doing this, they can take a step in the right direction by separating the root and login user, without becoming annoying asking for a password frequently as a newbie copies and pastes tutorial commands all week.
And as I said it’s unlikely, even very unlikely, but just not impossible. Everything comes with a risk, I just believe it’s up to you, not me, what risks mean in your environment. Might be you’d like to have the convenience on the home dev server, but rather have as much security as possible on a public facing one.
Or maybe you’d like to get really dialed in and only allow specific commands to be run without a password, so you can be quick and convenient about rebooting but lock down the rest. Up to you, really, that’s the power of Linux.
Does this mean the RClone integration can be improved?
It feels a little hacky right now, and as I previously learned when I last recommended it does not do things like image thumbnails which turns people away.