Meanwhile my sister’s fiancee drank the whole pitcher and is back working there totally believing Elon is some super genius and that the cars are capable of full self-driving. (I really have to bite my tongue when listening to him)
My camry can self-drive too, same outcome. (just off a cliff, rather than in front of a train)
The real stuff (the kind that doesn’t leave residue) can get expensive as hell though.
I think ‘uncanny’ would fit better, as certain surfaces would fluoresce despite having no apparent source of light, artifacts, or glaring that you could see.
I think the closest would be the TicWatch, though you’d be using an old Wear OS version and likely never get any updates for it.
Pretty sure they meant 8nm and not 8mm
It looks more of an antelope than a goat
Latter Day Saints
Yeah, there’s a 3rd-party driver called Spacenav that works pretty well. I haven’t gotten the two side buttons on my mini wireless one though.
(I wouldn’t bother with the driver from 3DConnexion as it hasn’t been touched in 10 years old)
ETA: The settings for it in FreeCAD is at Tools>Customize>Spaceball Motion/Buttons
And notification led with nSIM+nSIM/μSD tray
They’re using full disk encryption, which won’t let any part of it be read (even its partition table to boot the OS) until a password is entered. A system using FDE will go straight from POST to a password prompt.
A lot of people like FDE as it makes the encryption completely invisible to the OS and would normally have zero compatibility issues be problem-free.
KVM trays are generally only used for terminal/CLI access where widescreen doesn’t make much sense.
Widescreen ones are available (though not as plentiful) when the user is regularly using GUIs on it.
I thought AGPL only makes sure that a modification from the original must be released, and doesn’t cover new unmodified software that would connect to a server.
A company like meta could easily design their own product from scratch that would also have it’s own network and just a simple plugin that can communicate with the fediverse. Wouldn’t this could be a way for them to skirt around sec. 13 of the AGPL.
Honest discourse for the purpose of highlighting any possible issues and fortifying against the EEE process. (Prepare for war; hope for peace):
Let’s say they were able to join… (We should at the very least go over this possibility, as it can also help our admins decide.) How would we be able to protect our network?
Would making sure any features of one instance/app be open and able to be modified and/or gracefully integrated into another be an option? (similar to the GPL license) An example would be keeping a party from restricting access to a private network only through their app. (looking at you, gTalk and iMessage)
Any other suggestions?
Someone actually asked an almost identical question on StackEx a while ago. (things may have changed since) From what I got from skimming the answer, is there is precedence, and it should be covered within the TOS of the hosting website/network (i.e. lemmy.world)
Until there’s an option to turn off auto-update (without killing the daemon), snap can go to hell.
Ive lost so much time with snap updating Firefox and breaking my current session of multiple private windows/tabs. (Yes, I know you can use the .deb version but I shouldn’t have to go through those extra steps)
Not just any human. It should be a board certified child psychologist. They would be one of the few who could recognize a legitimate threat/concern or bullying from a poor joke or a stressed-out kid just venting with an empty threat. And on a positive ‘hit’, should just be a visit from the counselor to see what’s going on. IMO, psychologists should also be the only ones allowed to look at any of the info as they should know how to keep private conversations private if intervention is unnecessary.
The idea of the software does show some merits, but it is way, way too underdeveloped and grossly misused to be of any use.