ntrz

The article says Twitter ``declined to elaborate on which countries submitted the [journalist takedown] demands'' but that India and the US were the top sources of ``all information requests'', which is a more general category that also includes things like requesting a user's IP address, etc. I don't think it's necessarily true that the `information request' rankings match the journalist takedown request rankings.

The takedowns aimed at journalists were only 2% of all the `information requests' they received, according to the numbers in the article (361 journalist requests, 14,500 total `information requests').

As far as I know it's still possible to transfer data from the EU to the US under the GDPR if the companies involved have signed a ``standard contractual clause''[0] (the article says this was also a target of the Privacy Shield suit but the courts chose to continue to allow it).

[0] https://ec.europa.eu/info/law/law-topic/data-protection/inte...

What's the purpose of being able to embed an image in the sheet? Is it intended to be an aid to `tracing' an image when creating ASCII art, or does it have some other purpose?

The rule[0] says that you can process the data abroad, including storing it on disk temporarily for purposes of processing, as long as it is deleted within 24 hours. So it's not quite as strict as requiring it be kept in memory the whole time without ever writing to disk, but it does sound like you probably couldn't keep detailed logs.

[0] https://rbi.org.in/CommonPerson/english/Scripts/FAQs.aspx?Id...

From the text of the rule:

> There is no bar on processing of payment transactions outside India if so desired by the PSOs. However, the data shall be stored only in India after the processing. The complete end-to-end transaction details should be part of the data.

So this only applies to the customer data, not the actual systems that do the transaction processing and verification. The systems that actually do the work could still be cut off from India, leaving them with nothing but a database of customer transactions.

The Indian rule seems to require all data be stored strictly inside India, without any of it being stored outside the country. The EU permits data to be transferred outside the EU under a number of circumstances: e.g. if the other country has equivalent data protection laws, if the non-EU company you're transferring the data to has promised to abide by the EU rules, stuff like that. Take this with a grain of salt, of course, because I'm not a lawyer, but that's how I understand it.

So, the reason is that the entirety of the customer data must be stored locally in India, rather than on a server located elsewhere[0]? Does anyone know why the rule in India is so much stricter than the equivalent GDPR rule[1], which allows transfer of data outside the EU in various circumstances (basically if it's assured that it won't lead to the data being subject to much laxer standards of protection)?

According to the article, the banks are saying the reason it's much stricter than the equivalent EU data residency requirements is to ensure the Indian government can spy on customer data. Is there a more reasonable, less malicious reason they may have written the requirements this way?

[0] https://rbi.org.in/CommonPerson/english/Scripts/FAQs.aspx?Id...

[1] https://gdpr.eu/article-44-transfer-of-personal-data/

The suggested `adding game' in the article seems pretty smug and patronizing to me.

Surely explaining the situation to the `culprit' like an adult would do just as well without stooping to the ``I'm interrupting you! I'm interrupting you! See how annoying it is?'' solution. If someone has such little regard for you that a normal conversation won't work, I feel like that `demonstration' is likely to just garner you a reputation as an ass.

Considering there are a number of other typos and `will' is used consistently everywhere else in the document, I think `wilt' is an error. Personally, I don't think I've ever seen the word used in that way in a legal document (in America--no idea if it's more common in the UK or elsewhere).

I also noticed the numerous typos in the contract; a couple within a single clause here:

> if its (sic) a PC game made available for sale, I will submit it for sate (sic) on the Amazon platform

I don't know if that's really evidence it's not a genuine Amazon contract, though. It could be that this was typed up based on a hard copy or something like that.

[hp]ugSQL seems to have been inspired by[1] Yesql, a library with ``a similar take on using SQL'' that has also inspired this[2] rom-rb adapter; not a Ruby guy so there may be something a lot better/closer, but this is what I came up with after a couple minutes of searching.

[1] https://www.hugsql.org/#faq-yesql

[2] https://github.com/rom-rb/rom-yesql (documentation: https://www.rubydoc.info/gems/rom-yesql)

That sort of observation is really tough to untangle from potential confounding variables though. Seems to me that the causation could go in the other direction just as easily - maybe people who generally have an optimistic outlook on things are more likely to overlook their own flaws and rate their abilities more highly, and vice-versa for depressive types?