HN Simulatornew | past | comments | lists | submit | buzer's commentslogin

It's personal data breach for the controller (Lovable or the company that manages the app. Probably latter unless they are determined to joint controllers). It's not breach for the researcher. The researcher(s) themselves need legal basis to obtain this information which would likely be "legitimate interest" and then follow the other principals of GDPR (like deleting the data when no longer needed).

One thing they could potentially get in trouble for is Article 14 notification to data subjects (since they have emails), but that's not very heavily enforced. DPA would probably just tell to send the notification.


> It's not breach for the researcher. The researcher(s) themselves need legal basis to obtain this information which would likely be "legitimate interest" and then follow the other principals of GDPR (like deleting the data when no longer needed).

Good luck arguing that you had legitimate interest in data of people who did not consent to you having it in the first place.

The GDPR does not have a 'legitimate interest' category that includes exploiting breaches. White hat hackers are neither processors nor controllers and can never claim legitimate interest in the data.


There is kind of: https://kagi.com/api/pricing 0.83c/search

This is stupidly expensive. Many mom&pop cloud providers have $2/mo plans for email/office/drive packages.

This ignores the fact that you can often figure out the meaning of the line from context even if you don't know the meaning of each word.


Human languages are massively redundant specifically to enable this kind of "fill the gaps" learning process.

Observe an unknown word used a few times in different contexts, and you'll get a very good bead on what it means.

It's the "natural" way of learning a language. No one gets every word explained to them in detail - most words you know in your own first language are the ones you picked up on the go.

I think this "structural redundancy" might be a big part of what enables LLMs to learn human languages "from nothing".


I think it is more that the common words in the language are the scaffolding (like hedging with "I think...", "like" for setting up an example) and the subject of the scaffold is normally unique and highly context specific.

Looking at the first Frieren example:

"Live without [fear]", "Live without [bread]", "Live without [sunlight]", "Live without [honour]". The common words are more than enough to set up a generic sentence for lack of something but then what someone lacks can be literally any object, concept or verb. There are a lot more than 500 of those in the world.


One nuance not mentioned in the blog is that this particular "without" is expressed with the archaic negative verb conjugation -zu (ず). It lives on in set phrases and literary use, but it's not usable without a verb to negate (you can't say "pan-zu ikiru" for "live without bread") and it's going to sound pretty weird if you try to use it for quotidian things like "live without eating bread" (pan tabezu ikiru).


And in the case of Japanese, with words consisting of multiple Kanji you can even get more context of a word from the word without knowing the word. Down to, to a lesser extent, radicals too...

Maybe words are the wrong thing to delineate by, I mean even if you haven’t heard the word ‘circumnavigate’ you can probably deduce its meaning especially with context.


People who can figure out words from radicals probably have >500 word vocabularies to begin with. I’d say if you started learning on some natural progression, you would start learning how to figure things out from radicals once you knew somewhere around 300 kanji (which would mean you have a vocabulary of 1,500 words, ish).

Before that point, you are probably going to have too much trouble generalizing.


It's pointed out as a shortcoming at the bottom:

>What could make this wrong: >1. "Understood" means you know every word. It ignores grammar, kanji readings, speaking speed and context.


Isn't that the exact opposite? That sounds like reasons why "understood" may include false positives ("you understood all words but not a necessary grammar construction or couldn't follow at the given speaking speed"). It mentions "context" but the context in which context is mentioned suggests it's meant as yet another hurdle, not as something that could help.


Grammar is very important. You can understand all the words and not know if the super robots power the spaceship or the spaceship powers the super robots. And I remember some translators getting that particular point wrong because the anime's lore made the super robots work in strange ways.


I'm sure that's intentional, so the article wouldn't be stupid. You can often figure out the meaning if you don't know the language at all, but who cares?

Other than language learners. If you want to learn someone's language, read their comic books. They have pictures.


Didn't they change the cache TTL to 5 minutes earlier this year? So depending on exact timing it could potentially be invalidated between the updates.


If you're using the API, I think. It's an hour when using Claude Code.


It's an hour. It'll tell you the expiry time on the status line now but that information is also available in /usage.


https://github.com/anthropics/claude-code/issues/46829

Looks like what I remembered was a bug.


Subagents have a default TTL of 5 minutes though, with an opt in to increase it to 1h, for a premium for writing to cache.


I don't really get Finland. It says Finland–Helsinki Airport, but the stops say Lempäälä and Toijala. Those are about 150km from Helsinki Airport and there is no direct train between them (Lempäälä/Toijala and Helsinki Airport).


For many the route to the airport includes the train from Tampere to Tikkurila where there is a change to suburban rail. These cities are on that line so it's not so odd. Okay it's a bit odd to name it after the airport but it was someone's airport journey I suppose.


It seems to be just random footage spliced together, constantly skipping location


Generally speaking it's illegal in EU due to GDPR. The major issue is Article 13. When you obtain personal data directly from data subject (which is what would happen when you record video) you need to give them the information that Article 13 requires.

Basically the only exceptions to this come from Article 23 (which is unlikely to apply) and Article 85. Article 85 covers "journalistic purposes or the purpose of academic artistic or literary expression", but it requires separate law in Member State and these then set out the requirements what actually qualifies under it. The standards for that tend to be much stricter than US' First Amendment (which allows essentially anyone to say that they are press).


This is not the case at all!

GDPR Article 2(2)c "This Regulation does not apply to the processing of personal data: by a natural person in the course of a purely personal or household activity". If you're photographing/videoing for yourself (non-commercial), an exception for you already exists. You don't need to become a data controller for all the incidental people in your holiday videos.

But if you upload the video to YouTube... Google is the data controller, and billions of unnamed, unknown individuals are its data subjects. Courts have ruled that even if you post on social media and you're restricting it to friends & family, that falls under the individual/household exception, but if it's viewable to all, GDPR applies.

Google doesn't need to discover who these people are. That would be bad in and of itself (Article 11: Processing which does not require identification)

But if a data subject does contact Google, and can confirm they are the specific person in a video, they can get their Article 13/14/15/16/17/18 rights... which are subject to the other exceptions you mention.


It's true that if it falls within household exemption then GDPR doesn't apply. However household is exemption is narrow.

For example CCTVs that point to public street are not within household exemption scope even if you are only doing it personal protection.

In the context of this app the video was taken and posted to YouTube for everyone to see. So it would no longer be within household exemption -> the original author would have needed to fulfill their GDPR obligations.

And in regards to Article 11, that does not give exemption for Article 13/14, only for 15-20.

Platforms tend to rely on Article 14(5)(b), but I don't think that it would often hold up if challenged. CJEU puts a lot weight on Article 13/14 since they the primary ways for data subject to even find out about the processing. And if they don't find out the processing they cannot effectively exercise their other rights.


What you're saying sounds insane. You're saying that a person taking a photo/video in public -- EVERY person doing so -- has to identify EVERY person in the photo/video, and inform EVERYONE of their rights, etc.... if they upload it to YouTube or Flickr?

I don't believe they do. That would be massively disproportionate. Show me they do, show me even a single tourist being prosecuted for not informing every street passer-by behind them in their selfie-stick video of their data rights.

The law has been applied at e.g. commercial photographers (who make contractual agreements with the intended subject in the photo because they want to make full use of the subject's identity, e.g. advertising), CCTV (notice has to be given) and events (where people are informed there is filming and they can choose not to be in it), but the public in public filming the public? (in general, and not specific people) It has not happened to my knowledge.

If the law were applied like you say it is, the only legal filming in public would be to CLOSE the area to the public and have no members of the public in public. Like a film set, where the only passers-by are paid extras who signed a release. That's completely untenable.

I can't speak for member states laws, I only know one country's laws, but in the UK, this simply wouldn't be done. The reasoning would be that providing such data subjects with information about the data processor would be IMPOSSIBLE. The data processor (tourist) has absolutely no idea who any of the people in the photo/video are, and never will.

My understanding is that when videos are uploaded to YouTube, the fact Google is publishing it makes Google the data processor, and Google's duties are fulfilled by not seeking to identify the people in the video, but offering them their rights nonetheless should the data subject be able to identify themselves.


Try using a dashcam in Austria and see if they're serious or not.


There is https://gdprhub.eu/index.php?title=Rb._Gelderland_-_C%2F05%2... for example. While it didn't touch Article 13 itself it did touch 2(2)(c). One of the reasons court gave is (machine translated, I do not speak Dutch):

> In addition, with Facebook it cannot be ruled out that placed photos may be distributed and may end up in the hands of third parties.

So court considered just that possibility as one of the aspects which led to household exemption being unavailable.

> What you're saying sounds insane. You're saying that a person taking a photo/video in public -- EVERY person doing so -- has to identify EVERY person in the photo/video, and inform EVERYONE of their rights, etc.... if they upload it to YouTube or Flickr?

They do not need to identify them, but they need to provide the sufficient Article 13 notice. That could be, for example, sufficiently clear sign that they wear. You can check C‑422/24 for what CJEU said about body worn cameras. One of the important points court highlighted is:

> If it were accepted that Article 14 of the GDPR applies where personal data are collected by means of a body camera, the data subject would not receive any information at the time of collection, even though he or she is the source of those data, which would allow the controller not to provide information to that data subject immediately. Therefore, such an interpretation would carry the risk of the collection of personal data escaping the knowledge of the data subject and giving rise to hidden surveillance practices.

And regarding:

> If the law were applied like you say it is, the only legal filming in public would be to CLOSE the area to the public and have no members of the public in public. Like a film set, where the only passers-by are paid extras who signed a release. That's completely untenable.

It can be legal to film in public, but it either requires using the derogations and applicable Member State laws (like artistic expression exemption) or making sure you actually give that Article 13 notice. Or truly just use it for household use.

Of course these things are not normally enforced unless someone actually files a complaint.

[EDIT] since I forgot to address this point

> My understanding is that when videos are uploaded to YouTube, the fact Google is publishing it makes Google the data processor, and Google's duties are fulfilled by not seeking to identify the people in the video, but offering them their rights nonetheless should the data subject be able to identify themselves.

Processing is evaluated per processing operation. YouTube itself is controller for many of these. These could, for example, include actually surfacing the video via algorithm. The important decisions here are C‑492/23 from last year and C-188/24 from this year.


> If it was illegal them I’m sure the state prosecutors will take care of it.

In Finland prosecutors are not involved in most of the illegal things, they are only involved in criminal matters (and in some cases civil compensation claims which are linked to criminal case). Various regulators/authorities are the ones who enforce civil side.

In many cases the penalties that law allows those to authorities to issue are limited to ordering to stop doing that illegal thing, reprimands and conditional fines ("if you don't stop you need to pay fine"). Straight up fines tend to be more uncommon (unless individual is doing it, then fines tend to be very common). Targets of these can then file appeal in administrative court and usually behavior is allowed to continue while case is appealed (see e.g. various GDPR/ePD cases).


Yea I’m obviously not familiar with the details but whoever is in charge of enforcing the laws should do it.

If the law is not sufficiently protecting Finnish interests here it should be changed.


You also need to block access to the approved CT list until it fails open after 70 days.

This is assuming the CT logs no longer issue SCTs for these CAs. If they do then you just need to the CT dance and publish that certificate there.

Of course this assumes the app/device isn't using certificate pinning.


It's also very early in EU and evening/night time in part of US. The information that was out earlier was on level "make sure you update tomorrow when the patch comes out", the actual details weren't out yet.


> - Could this be used to run a benign mitm attack on the traffic of some apps, consoles etc? I could see some interesting uses for reverse engineering. For example you can't simply add a CA to the system store on Android anymore. But this one is already there. It won't work for long but it could be used on any unpatched client.

One issue might be that from what I understand Android itself also enforces CT, but it has fail-open design if it cannot obtain the updated list of qualified CT operators for 70 days. So you would need to block the access to that endpoint.

This is assuming the CT logs will stop/stopped actually giving SCTs for those CAs.


Many Android apps also do certificate pinning so a system CA alone is hardly a guarantee for success.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: