Hackaday is a content aggregator site that usually has more content on these topics - https://hackaday.com
Or there are still some good old blogs out there with RSS feeds http://www.righto.com/http://oldvcr.blogspot.com/https://blog.ret2.io/
Hackaday is a content aggregator site that usually has more content on these topics - https://hackaday.com
Or there are still some good old blogs out there with RSS feeds http://www.righto.com/http://oldvcr.blogspot.com/https://blog.ret2.io/
At least with email, you're in control of what shows up in your inbox as well as message routing with filters of your choice
And it's open-source:
https://github.com/apple/container
It's not really supported before Tahoe, presumably due to required hypervisor support.
NetBSD still supports it, and a wide variety of other SPARC systems https://wiki.netbsd.org/ports/sparc64/
The photography world is mired in proprietary software/ formats, and locked down hardware; and while it has always been true that a digital camera is “just” a computer, now more than ever it is painful just how limited and archaic on-board camera software is when compared to what we’ve grown accustomed to in the mobile phone era.
If I compare photography to another creative discipline I am somewhat familiar with, music production - the latter has way more open software/hardware initiatives, and freedom of not having to tether yourself to large, slow, user-abusing companies when choosing gear to work with.
Long live Magic Lantern!
cries in .x3f & Sigma Photo Pro
I can't seem to find anything.
I wonder what the protocol for sending update requests is. It sure must be encrypted? If so, what if the encryption algoritm is weak by modern standards, given Voyager 1 is 46 years old, and can be reverse engineered somehow? I.e. can someone outside of NASA send requests to Voyager to change its code?
Unless you've got your own very-very high power transmitters and large dishes, you're not communicating with either Voyager satellite
"Newer" science & research satellites from the late 2000s onward do support a variety of encryption in transit and authentication from the ground stations
Then a link to be found on goog or few comments further down, says, they wanted to do it on iCloud. But everyone is going rage mode. So they retracted and wanted to do it with more "privacy" on device.. and then, the link also say, they created an API to filter what for example kids should not see or send and app developers can use it.
iCloud scanning is ok with me and my privacy advisor. There are bad guys out there.
And certainly the corporation couldn't be be coerced by the government that's built the largest surveillance apparatus in human history to keep the csam feature running on billions of devices?
Yes, the corporation can be trusted.
/s
Small teams are more efficient but (obviously) can't produce at scale. When you scale up, there's enough HR or finance or marketing, or PM, etc. work for full-time specialists. And larger orgs need bureaucracy - if you have a way around that, the world is yours.
Why Mozilla won't let people financially contribute directly to Firefox development and continues to pursue these stupid monetization paths is a mystery.