Assuming we can make and dump dry ice / ice at scale through renewable energy, would it be a feasible / meaningful solution to even try, in order to extend time (not reduce temperature)?
Absolutely not. Adding carbon dioxide to water creates carbonic acid, which dissolves shellfish shells and coral reefs.
In fact ocean acidification from dumping carbon dioxide in the air is already putting us at risk of losing most of our shellfish in the next few decades.
Although the privacy related changes were somewhat expected, the timing and aggresive timeline will likely play out in Facebook's favor.
While giving users a 1 month grace period to either comply (share their data) or delete their account already seems like a pretty aggressive window that limits the ability for users to fully assess options or migrate existing groups/chats to alternative platforms, the short timeline combined with the on-going pandemic, and the fact that WhatsApp has become one of the primary means of communication for many around the world will likely lead to a very limited drop in users leaving the platform as a result of this policy change.
Beyond Febuary, once users have already shared their data, there is likely minimal incentive for groups or individuals to overcome the network effects and move to another platform in the short term.
I’d be surprised if this isn’t just whitewashing some previously shared data.
Also, a preparation for antitrust action - once the data is shared and integrated, even if they are forced to separate WhatsApp, they have all the metadata (which takes 3-5 years to become stale) and now they will have it “legally” (sadly, this extortion is indeed legal. It shouldn’t be)
> Isn't WhatsApp still purportedly end-to-end encrypted? What data is "on the table" when it comes to sharing - just contact lists and phone numbers?
It is, and same is claimed in their privacy policy and ToS. According to the original article it will include, what is already being collected:
User phone numbers
Other people’s phone numbers stored in address books
Profile names
Profile pictures and
Status message including when a user was last online
Diagnostic data collected from app logs
Along with possibly:
Purchases
Financial information
Location
Contacts
User content
Identifiers
Usage data and
Diagnostics
A little more than contact lists and phone numbers.
No idea on how complicated it is to file an S1. I just type code :)
From my understanding, the SPAC goes public (with an S1) with the intent to acquire "some company". Then the company being acquired doesn't have to file an S1. I would guess that the SPAC's S1 is going to be a lot less complicated, as it's a do-nothing holding company set up to acquire some TBD company.
It is probably not very useful for lidar, because the effect only works for UV wavelengths. At the normal eye-safe infrared wavelengths used for lidar the quantum efficiency of this type of detector is basically 0.
It does work well for general low light imaging and nightvision applications, you can get a black silicon sensor quite high QE (~80%-ish depending on what wavelength ranges you are interested in) commercially from https://www.sionyx.com/
This is awesome! I just started using the WorldBrain Memex and was trying to solve the issue of accessing other data sources, so perfect timing -- thanks!
Good to see this finally happening. I wonder how they're going to scale this out though -- AVs are still pretty expensive to build/operate (COGS/TeleOps/Maintenance etc)
Haven't seen a recent study/article around cost/ROI (not sure if these have gone down significantly) -- any recommendations?
Does anyone know if these types of bug bounties are negotiable?
As several people have mentioned, hackers can sell to the highest bidder and having proof that you have an exploit is probably sufficient, but what if Apple was willing to pay as much as the highest bidder?
This may also likely convince people who have sold bugs to reach out to Apple.
It probably costs them a fraction of the PR spend or risk of data breach/user exposure etc.
The press release specifies that the $1000000 quoted figures are minimum payments for the given category of bug, so the actual amount paid could be anywhere upwards from that.
Wow. Never thought about this approach to leveraging RAM for cameras. Awesome guide!
Can anybody chime in regarding the resolution limit (640x64) -- If this is for memory reasons, could we pick alternate values such as 200x200 as long as the total pixel count is the same?
I think you're stuck with the oddball aspect ratio. Part of the CMOS readout process is done an entire line at a time, and there just isn't a way to increase the speed this much without dropping most of the lines. Actual high-speed cameras have similar limitations at the higher speeds.
> Never thought about this approach to leveraging RAM for cameras.
This is normal for high refresh rate cameras. They store straight to ram then dump to the disk (SSD) after. Especially the higher end cameras, they literally can't store data fast enough to go anywhere else.
>Can anybody chime in regarding the resolution limit (640x64)
Light exposure on the sensor, the faster the frame rate, the darker the image as its a fixed aperture. Photographic buffs could explain it better, but my take is the faster the exposure the bigger the aperture that is needed to let more light in to make the photo look well lit. I don't know if parts of the sensor also work faster due to its circuit design but I would imagine this is also a factor just like its possible to read more data form the outside of a spin disk than the tracks close to the centre.
Came across this interesting idea of storing ship emissions as dry ice at the bottom of the ocean. [1]https://fathom.world/co2-spears-decarbonise-ccs/