1,367 karma · joined October 8, 2016
Especially interested in systems scaling & IAM and also general interest in most of thing on backend side.
You can reach me via <username>@<username>.net
At least according to that they won't ask you to accept new ToS, probably due to the fact ToS allows them to change ToS at will.
Of course, if the protocol added workaround for NAT and NAT is modifying that application layer data then it can cause another set of issues.
https://edpb.europa.eu/system/files/2022-01/edpb_guidelines_...
> Example 3: GAMER X is registered as a user on the gaming platform of PLATFORM Y. One day, GAMER X is notified that his online account has been restricted. As he is unable to log in anymore, GAMER X asks the controller for access to all personal data relating to him. In addition, GAMER X requires access to the reasons for the account restriction. PLATFORM Y, the controller of the online gaming platform with which the request has been lodged, informs the users in its general terms and conditions available on its website, that any kind of cheating (mainly by the use of third party software) will entail a periodical or permanent ban from its platform. PLATFORM Y also informs the users in its privacy policy about the processing of personal data for the purpose of detecting gaming cheats, in accordance with the requirements set out in Art. 13 GDPR.
> Upon receipt of GAMER X’s request for access, PLATFORM Y should provide GAMER X with a copy of the personal data processed about GAMER X. Regarding the reason for the account restriction, PLATFORM Y should confirm GAMER X that it decided to restrict GAMER X’s access to online games due to the use of one or repeated gaming cheats which are in violation with the general terms of use. In addition to the information provided about the processing for the purpose of gaming cheat detection, PLATFORM Y should grant GAMER X access to the information it has stored about GAMER X’s gaming cheats which led to the restriction. In particular, PLATFORM Y should provide GAMER X with the information that led to the restriction of the account (e.g. log overview, date and time of cheating, detection of third party software,...) in order for the data subject to verify that the data processing has been accurate.
> However, according to Art. 15(4) and Recital 63 GDPR, PLATFORM Y is not bound to reveal any part of the technical operating of the anti-cheat software even if this information is relating to GAMER X as long as this is can be regarded as trade secrets. The necessary balancing of interests under Art. 15(4) will have the result that the trade secrets of PLATFORM Y preclude the disclosure of this personal data because knowledge of the technical operating of the anti-cheat software could also allow the user to circumvent future cheat or fraud detection
> The extent of the information provided to individuals will be heavily context dependent, taking into account the nature of the data controller and the nature of the breach of the terms of service. In some cases, it may only be possible for the data controller to provide basic information in response to an access request to which Art. 15(4) applies
So at least some information should be provided while some things could fall under the trade secret exception. I would imagine at least some cases need to go to DPA in order to get some clarification on what information must be provided and which things they could avoid disclosing, but that is going to take quite a while to get any resolution on.
I tried it by putting Finnish prompt and I got answer in Finnish (e.g. "Miten paistan pihvin?"). Translations were also quite good on some samples that I tried (Finnish-English, English-Finnish, Japanese-Finnish, Japanese-English).
(2002)
A bit more unclear situation is if non-resident is visiting EU and uses services from their home country.
CJEU ruled back in 2016 that IP address is personal data if provider has legal means to identify the person. This includes, as example that was given in the case, laws that give means for service provider to identify the users in the case of cyber attack by requesting help from other authorities.
This ruling is from before GDPR and relates to the older Data Protection Directive, but the relevant chapters are largely same (GDPR mostly increased the explicit scope).
Ruling: https://curia.europa.eu/juris/document/document.jsf?docid=18...
The "tl;dr" parts are 30 (the question) & 47-49.
The old directive: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...
While I don't think I have seen it on Twitter (then again I only read it when it's linked) I have seen plenty of it in some older forums & IRC. Generally it's just nonsense like "jqrfefafasok" or ":DDDDDD" being posted lots of times in quick succession, often to either flood out other things, to draw attention to poster or to show annoyance about something (like being banned previously).
Firefox blocks the access to site, I think most of other browsers do not.
I have no clue why they are saying that they are hard linking directories, I sure hope they are only doing it on file level.
* there was no obvious way to do it. Closest thing was by reporting issue on product.
* there was no way to show the customer service agent a picture of the mail. Chat did not support sending pictures & they were unable to open imgur link.
* agent recommended me to leave a report it by leaving review to the seller page. I did that and next day review was deleted.
https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL... & https://europa.eu/youreurope/business/dealing-with-customers...
> 13898 Anime
The new site does seem to have more entries, but I haven't checked what the differences are exactly (e.g. are some things counted in one but not in other). For example the table shows 36 movies from 1910s, in AniDB there is only 26 (search with start time between 1.1.1910 and 1.1.1920, the only entries are movies).