165 karma · joined May 31, 2020
In my country, fiber is run to my apartment building and through the technical shafts. Very easy for the telco: to connect a unit, they only need to branch off from the technical shaft. I imagine the total cost to connect 200 apartment units is much lower than connecting 200 farms or 200 houses in the suburbs, even with the red tape.
What printers are similarly priced and have similar specs, for someone relatively new to 3D printing?
> 10: The researcher found out about this success by receiving an unexpected email from the model while eating a sandwich in a park.
Phew. AGI will be televised.
In the old system, I could just punch in the code or scan the QR code, but now I have to do this dance of “why won’t it connect?” every time
I have not been able to read the docs fully, but some questions:
* How do you handle state that is too big to send to the client fully? In a chat application, does the client need to have the whole channel history, or is syncing a subset of that supported? * Does permissioning support partial CoValues? For example, "You can edit the contents but not the title of the 'blog post #11' object" * Do you have resources about the suggested data modelling? Things like how granular should a CoValue be and what the trade-offs are. * How do you handle deletion? Do you tombstone? Is there a way to fully scrub a value from history (to support, for example, GDPR's right to erasure)?
However, a shooting is just one type of mass casualty event.
From what I remember, the ePrivacy-GDPR cookie mismatch (consent as the only allowed legal basis for cookies) is due to ePrivacy being older than the GDPR and not intentional.
Article 5 (Principles) is always a good mention - just having a legal basis is not enough, you always need to respect these principles (such as lawfulness, fairness and transparency).
The dig at pseudonomyzation not being enough is great. It's a personal pet peeve of mine. Pseudonomized data is still personal data!
The GDPR does not prescribe how to anonymize data. It just says "as long as someone can identify a person, then it's personal data." For example, you might think that aggregating based on city is enough to anonymize, but my nephew was at one point the sole person living in a village - that would have directly identified him. Likewise, stripping the last octet of IP addresses might not be enough if I personally own a /24. It's all about context.
The biggest thing I personally learned, was that any solution claiming to be "GDPR proof" probably is not compliant.
Known as "the Egg" locally.
The city of Ghent was eyeing autonomous small crafts as "water taxis", and a big shipping provider wanted to do last-mile(s) delivery for shops, restaurants, and small parcel pickup points along a river. For the latter case, the vessel would still be manned, but instead of having to navigate, that person could sort and prepare parcels for delivery.
https://videoweek.com/2020/08/12/server-side-ad-insertion-ex...
Antigen tests are less sensitive, applicable in a much more narrow time frame than PCR tests, and not as trivial to perform correctly as suggested in the media. On top of that, they can be sensitive to external factors as well (such as temperature swings for tests in storage, and fast expiration).
I dislike these antigen tests due to the false sense of security they give people. They have their uses, but they are not a substitute for PCR tests.
There's a reason why influenza antigen tests are not widespread.