The worry is people being pushed into it by family who don't want to care for them. Or just people who feel like a burden.

Before it becomes law I'm sure the protections will be made iron clad but it is a real worry.

My nan is having to sell her house to pay for the care home. I can imagine people wanting to get their relatives out of the way to avoid losing their inheritance.

How do they steal your data? They also said malware

Nah he's just bullshitting to his base. This isn't a mental health crisis or anything. Just grifting.

But then they'll only refuse in areas they think they'll lose.

Not sure if Vietnam is quite the amazing example they think it is.

The letter "W" is called "double U" because the Normans invented it by combining two pointed capital letters to represent the sound "w" in Anglo-Saxon words after the Norman Conquest of England in 1066. The name "double U" still indicates how the letter was created.

Before the Norman Conquest, the Latin letter "V" was used to represent both the "v" and "w" sounds. The Anglo-Saxons created a separate character called "wen" to represent the "w" sound. After the Norman Conquest, the Normans combined two pointed capital letters to create the "W" to represent the "w" sound in Anglo-Saxon words.

So basically we can do nothing lol

At the end of the day if you don't want them using your data don't give it to them. It's the only way.

Don't use their service. Get a privacy focused browser. Get an ad blocker. Disable 3rd party cookies. Container off the sites. Only use the Internet to view furry porn.

Then you're totally protected.

I guess you can argue it's already written in C. So that was always a requirement.

What they actually do is record everything encrypted and wait for computers to get fast enough to crack it.

1. The general wisdom is that the dbcontext is already a repository and you should use Select statements to grab only the data you require from the database. So in your service you can do something like

    await context.Movies.Where(...)
    .Select(m => new { Property1,Propert2, ... })
    .AsAsyncEnumerable()
    .SelectAsync(m => new Dto(...))

this way you only pull the exact fields you need.

2. Just new up genre, add your movie to it and add it to the dbcontext and call save changes.

3. Again just do a where against the context.

4. It is and there's no need to add another layer that limits what you can do with it.

This argument for a repo layer was all the rage about 10 years ago. It is absolutely not required and as you've identified makes working with the dbcontext a pain.

For testing either mock the dbcontext or use the in memory db provider.

One thing to look at to formalize your queries is compiled queries. These give you strongly typed queries and removed the SQL generation step each time you run it.

Ending private landlords seems easier

Sources as in causes of poisoning not references. Maybe work on your reading comprehension before you're pointlessly rude to people.