Well… I think you are putting too much expectation on a common person. I’m pretty sure a lot of people are going to be ‘mind blown’, by the ability of the new Recall feature. They will hail it as a technological marvel. Very few people care about privacy, and even in that, very few people really understand how they can have some privacy. Complete privacy is near to impossible.
Come on… don’t be so pessimistic!!
Hmm… Machine learning on a dataset with images?
Recently they officially added a module to censor stuff on an individual instance basis…
The what?? Is it a condition?
What’s the licensing part you mentioned? Can you elaborate a little?
Well this can be a starting point of a rabbit hole. Time to spend hours reading stuff that I don’t really understand.
Well this thread clearly established that I neither have technical knowledge and I don’t pay attention to spelling…
Jokes aside this is a good explanation. I have seen admins using vSphere and it kind of makes sense. I’m just starting to scratch the surface of homelab, and now started out with a raspberry pie. My dream is a full fledged self sustaining homelab.
Oh dear… I really thought I understood what bare metal means… But looks like this is beyond my tech comprehension
Hey sorry for the confusion. What I meant is Proxmos is considered as a bare metal hypervisor and Virt manager is a hypervisor inside an OS, right?
Aah… Isn’t that what called a bare metal OS?
What is the difference between Virtual Machine Manager and Proxmos?
TBH I felt this is something they made up once it got more attention. If they had felt remorse, they might have come back to apologise or correct their mistake, sometime in the past two weeks I guess.
Who knows maybe they are really ill. Maybe they just made everything up.
There is no limit implemented, but it constantly failed to get an 8gb file to be transferred between two VMs. LocalSend is more reliable in my case.
Try this. Still under active development, but I like it so far.
I have been using something very similar to this. In my team I insisted on people without any git experience working on a separate local branch, than the feature branch
. To ensure screw ups are minimal, we pull and create a local feature branch and then a new local only dummy branch, on top of it. Once the team is more comfortable with git, I am planning to treat the local feature branch as a dummy branch.
So far things have been pretty neat. Spaghetti is no more with minimal conflicts.
Offtopic question. Are you familiar with AVEVA (Wonderware) System Platform? We have been working on it for smart city command and control centre. The challenge is bringing in equipments from different OEMs under a single interface. Some projects want this to simplify operations. They prefer one application over many. What
Another thing is I saw you specified some OEMs. And most of the time they have some variant of an open protocol that only works with their PLC. Why does the SCADA/Automation not move into some universal standards? Is it because very few OEMs have significant market share? I am aware of OPC UA. But no universal support.
git commit --amend --no-editThis helped me countless times…