In fact I'm not sure I got a Z all game, though it seems other commenters did.
1,306 karma · joined August 20, 2013
In fact I'm not sure I got a Z all game, though it seems other commenters did.
--------
It feels wrong to loop in the anonymized TraceTogether technology with other genuinely egregious privacy violations of the Singaporean government.
The Android/Apple exposure notifications API[0] rolled out in the early days of the pandemic is a pretty solid example IMO of handling privacy correctly. The protocol generates you a new anonymous ID every 20 minutes and locally remembers the last ~30 days of ids. Through BTLE, it collects the anonymous ids of other phones that it's within range of (and for how long), and remembers them locally for ~30 days. When someone voluntarily self-reports as COVID-positive, the API broadcasts the list anonymous ids used during their likely contagious period, allowing other phones to locally recognize if they've been exposed, and for how long.
It's hard to imagine a more private version of this with any amount of usefulness. Unless I'm missing something (which I may well be!), the privacy loss the article refers can only happen if:
1. The police can legally and physically confiscate and unlock your phone
2. The police can legally and physically confiscate and unlock the phone of the person they suspect you of being/not being within 20 feet of
3. It was less than a month ago
4. There were no other eyewitnesses or evidence of the contact
The first one, of course, also gives them access to plenty of other data we think of as private.
Because this scenario exists, you can definitely make an argument that phones are a little less private with TraceTogether than without. But with the rarity and narrowness of the breach, I have a hard time putting it even remotely close to the other pieces of the article, describing 24/7 security cameras and exposing confidential lawyer correspondences.
The article concludes:
> What’s less considered is the sheer volume of data, and the variety of types of data that the state is collecting, allowing it to piece together people’s lives with much more detail than we might realise.
...and, well, I completely agree. That's exactly the context the article seems to lack.
It's also a broader problem: How do we effectively define and communicate a right to privacy when the volume is what's so important?
[0] https://www.google.com/covid19/exposurenotifications/
[1] https://www.straitstimes.com/singapore/apple-google-contact-...
GPs point is that owning land is not creating value. It is, however, very profitable.
On the flip side, are there any congresspeople who have publicly put all their assets in a blind trust? Any who have advanced bills requiring this of their colleagues?
The solution to problems like this is elections, and you would think "My opponent is insider trading while I literally can't" would make a great campaign ad.
Right. Even the Post Office is not required to deliver pipe bombs.
The issue is that right now, that's not the standard. Amazon /hasn't/ taken down sites in the name of political censorship, but it /could/. The implications of that are important, and they're why I find it hard to be satisfied with justifications like "Amazon is a private company, they can do what they want".
The _visual_ feedback from moving your head and rotating objects with the pen were extremely low-latency. Gesture detection is still nowhere near that level of fidelity but with peripherals, perhaps it's not necessary.
Lichess ratings are inflated not because of Glicko but because of the player pool. New players start at 1500 ELO in both Lichess and FIDE, but Lichess's pool of "new players" is a lot wider and has a lot more amateurs than FIDE's new players. The amateurs' points ultimately get spread around the player pool while they descend from 1500 to a more realistic rating, inflating the ratings of other players on the way.
This makes your git diff highlight the actual different characters between two lines, makes file names easy to see (and easy to copy, due to no a/ b/), makes renames and blank lines clear and readable.
It is so nice to get all this without a separate GUI diff visualiser when doing anything git-related from the command line.
Online chess areas like lichess and chess.com absolutely have automated cheat detection which they consider along with with reports in automated banning of accounts. They consider not just whether the player is playing the excellent moves (something common at any level and very common at high levels), but also how a deep search is needed to evaluate that move, whether other obvious moves were available, how long was taken to play the move, if the position is common, etc. When these serial cheaters are banned, the sites even refund rating points to everyone who lost to them.
However, the issue of isolated cheating incidents is still a big deal, even if the serial obvious cheaters can be detected.
Arguably, it's not this law's job to introduce such a protection! But best I can tell, no other law covers it in MA. It is perfectly legal for 3rd parties to sell this and other data without my explicit consent or even an opportunity to opt out (I think only CA has such an opt-out [0]).
Granted, manufacturers already have and can sell this data with no recourse. But at least manufacturers have national brands which could be hurt by selling or leaking massive amounts of data about their customers. Perhaps some brands could even make privacy a selling point. It seems like this law erodes that thin shell of protection.
[0] http://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?...
The thing that bugs me out about this law is that, AFAICT, this data is _already_ required to be available to any 3rd party manufacturer through a physical "non-proprietary interface" (so far, an OBD-II port) after a similar ballot initiative from 2013 [0]. This law essentially just makes the data available wirelessly.
I care about security holes and I care about consent. Having a physical interface makes it easy to provide data with consent to repair shops who need while trivially making sure no third party manufacturer or insurance company is leaked a massive database of everyone's driving data. I really don't see how the "wireless" addition gives me more of a right to repair, but I clearly see how it forces manufacturers to significantly increase their surface area of possible data leaks.
I'm all for Ben Franklin's liberty/safety argument, but with the 2013 law already in place, I honestly don't see the upside of the 2020 law.
[0] https://malegislature.gov/Laws/SessionLaws/Acts/2013/Chapter....
This boggles my mind. Sure, it will take a reasonable effort to get widespread use of these apps. But the impact would be huge. Even low rates of app use have a real chance of lowering the reproduction rate significantly, and reasonably broad usage bring it less than 1.0.
The technology is designed in the right way, where anonymous data is being collected with no app required. People can download the app right after they get a positive test and report themselves positive retroactively. Same on the other side, you can download the app and know how much contact you've had with positive cases retroactively.
I'm no longer surprised the US federal government is doing nothing to push this. But I expected more out of the states.
[0] https://9to5mac.com/2020/07/13/covid-19-exposure-notificatio...
There's a protocol running on almost every smartphone in the world right now, locally recording the necessary anonymized proximity data with BTLE[0]. All states need to to is produce an authoritative way to declare you have COVID, and release an app that provides notifications if a new case is broadcast that matches your history.
The fact that this protocol allows reporting your recent data even if you've installed nothing before realizing you have COVID is critical for success. The fact that the data doesn't include GPS or any long-time persistent key is critical for privacy (and, thus, adoption).
The upside is potentially significantly lowering the reproduction rate of COVID while businesses reopen. The downside is... what exactly? Why has almost every state (not to mention the federal government) not committed to implementing these apps?
[0] https://covid19-static.cdn-apple.com/applications/covid19/cu...
So for example, if working in a coal mine is 10 micromorts per work day, and you choose to do it each day, it seems pretty reasonable to call that 10 * 5 days * 50 work weeks = 2500 micromorts per year. You're "paying" that cost each time you decide to go to work, and if you decide to work next year it won't somehow "cost" less micromorts – the possible yous who died last year won't be around to make the decision.
Honestly curious: Is there more discussion to be had than that?
I hope that stores like these will one day be hubs where we can refill all our bulk products and actually save on shipping and packaging. I fear that stores like these will just sell me individually wrapped apples because it's not worth the effort.
For digital media, screen readers are an enormous accessibility feature, but having (impaired) vision and knowledge of english is a helpful fallback for the plethora of poorly built sites and applications that have, say, text in an image. Braille is not helpful in a world of flat screens.
Here's a video with more context! https://youtu.be/ysV6iF3Rmjo
This would make the call e.g. v1->cross(v2) syntactic sugar for the call cross(v1, v2).
The main reason it's not just an obvious win for autocomplete and readability is that it provides for multiple ways to do one thing, and is one more thing you need to know when learning this new language. Rather than having some code call plane->yAxis() and other code call yAxis(plane), it might be nicer to have only one way.
The other counterargument: the OOP-like syntax could support the expectation that polymorphism works like e.g. Java, where e.g. v1.cross(v2) would only considers the type of v1 when deciding which overload to call. FeatureScript has multiple dispatch and will consider the types of all arguments when choosing an overload.
All that said, the change it seems like a win overall, but we're waiting for the language to mature more to see if clearer arguments emerge.
[0] https://cad.onshape.com/FsDoc/
[1] https://forum.onshape.com/discussion/comment/33495/#Comment_...
So, what you're suggesting seems a lot like shipping code before code review, and seems to have many of the same problems. What do you do in the long period before critical issues have been addressed? What do you do if the submitter just says "fuck you, my code works, I have more important things to do"?
I do wonder, though, if this will have the opposite effect. There is plenty to criticize about these tweets, and the stable genius behind them, so it's not surprising that many have called for these messages to be banned. But, they still seem like a legitimate use if the platform, so my main reaction reading the messages is "Wait, _that_ would be ban-worthy?". This policy may end up undermining the credibility of the platform more than the author.
In a snow emergency (i.e. when cars are forced off one side of the street for plowing), the vertical barriers can be manually removed.