cdrx

Junie in Ask mode:

> Which LLM are you?

> I am Claude, an AI assistant created by Anthropic. In this interface, I'm operating as "Junie," a helpful assistant designed to explore codebases and answer questions about projects. I'm built on Anthropic's large language model technology, specifically the Claude model family.

Jetbrains wider AI tools let you choose the model that gets used but as far as I can tell Junie doesn't. That said, it works great.

> bundle it with something like https://fortawesome.com/

Using FA as a CDN is not GDPR compliant, either.

Generally speaking using any public CDN is not GDPR compliant. If you _could_ self host the files, then you can not meet the necessity test required for any of the relevant legal basis in GDPR art 6(1).

Google Fonts and FA are worse, because the personal data is shipped off wholesale to the USA. Neither FA or Google (for fonts) offers a data processing agreement that would make it legal to use.

That is my understanding too. The issue is as much about jurisdiction as the physical location of the hard drive that holds data.

“PII” is not a term the EU or UK GDPR recognises. It may have a specific meaning in American law; but the GDPR definition of personal data is significantly broader.

It certainly includes the items I listed; particularly when linked to an identifier like an IP address.

> This ruling, should Google comply in the end, will not change anything. Google will store the data in the EU and that's it.

The US CLOUD Act allows US law enforcement to force Google to hand over data; even if that data is stored outside the USA.

It is highly likely that processing and storing analytics data only in the EU is not enough to "fix" Google's issue here, because the USA still has juristiction.

See the recent Akamai / Cookiebot case.

By its very nature, an analytics product must process personal data.

Personal data is "any information relating to an identifiable individual" (see GDPR art 4(1).

Your IP address, browser and OS (via user agent), the website you visited, the pages you visited, time of visit, the site you came from (via referrer) are all personal data.

If Plausible have put a US owned cloud provider in-front of their Hetzner infrastructure, even if for a legitimate purpose (CDN, DDoS prevention) then that is likely an unlawful transfer of personal data to the USA.

> As for the privacy laws regarding tracking IP addresses, it's not very clear whether it requires consent or not as the law is ambiguous. The IP itself alone can not be directly considered personally identifiable information (PII) as having an IP address only, can not define which real person is the data associated with.

"PII" has a specific meaning, in American law. Sites with references to it are likely not relevant to you, as you are based in Romania. The GDPR is crystal clear that IP addresses are personal data. There is no ambiguity. Depending on how you derive the hash of the IP and user agent, this could also be an "identifier" that may be personal data.

But! There are six different reasons you can legally process personal data. Consent is only one of them. It is quite likely that a website owner would have a valid legitimate interest basis for having analytics. This does not require consent from the user.

The only caveat to that; is that if the analytics needs a cookie (or local or session storage item) then you must seek consent for the cookie.

ORM will use the same `a` suffix, yes.

There are a few tools that will "tile" an image for you. libvips dzsave works well, even for really big images: https://libvips.github.io/libvips/API/current/Making-image-p...

There are commercial products in this space too (like Maptiler).

Swarm isn't dead, it works just fine and is being actively maintained.

Your understanding of the regulation is wrong, but I’m not going to hammer the point.

> No if a user clicks a button to see the prices at 10 euros but see the prices at 20 euros then that is an issue.

I agree with you, that is a serious issue. But that issue is caused by your use of a/b testing, and if you solve that issue with a cookie then you need consent.

The ICO PECR guidance explicitly states that you can not rely on the strictly necessary exemption for analytics cookies.

Your understanding of strictly necessary is incorrect. You do not need to a/b test a website for it to function. It is optional. It doesn’t become legal just because your tech stack makes it difficult, or because you engineer the site not to work without a non-essential cookie.

You could a/b test based on even or odd numbered IP address and not require consent to store a cookie. You can pass the referrer around via query string and not require consent to store a cookie.

However, as you said, there is no enforcement of the regulation so the risk of non-compliance is basically zero :)

Storing a cookie which is not strictly necessary to provide the service, requires explicit consent. This is a PECR requirement, not a GDPR one. Tracking the source and campaign of a user between pages is not required to deliver the page.

So you may rely on legitimate interest to process the data, but you need the consent to store the session cookie to collect the data in the first place.

> Isn't this what's written in the GDPR?

I wish it was this explicit, but it isn't. EU member states have all interpreted the regulation differently.

Making it harder to opt out than in is explicitly prohibited in the UK and Germany. It is perfectly legal in Italy. In Spain, it is legal to bury the opt out buttons at the end of a 50 page cookie policy.

Full compliance, across the whole of the EU, is exceptionally difficult.

To be legal you need to get the user's consent, upfront, for that tracking. Technical challenges are not a defence.

GDPR is not the only regulation at play here. The PECR also applies. You need consent for the session cookie in the public areas of your site. It doesn't become essential until the user logs in, registers, adds an item to the cart, etc.

Git remotes is certainly not "easier to implement". You need to have ssh infrastructure setup to receive the repository, deal with key management, provide the user some way to input ssh keys, etc. Contrast that with GitHub web hooks + API and I can see why they didn't bother.

I bet GitHub covers the vast majority of their target users.

There is https://apibakery.com on the basic end of the scale

I think forestadmin.com / jetadmin.io are the SQL introspection equivalent of the Django Admin. Both are commercial products though.

Standard DRF is nothing like the JSON API spec.

You can tweet a new colour for the tree to @port57tree.

The tree is driven by two Raspberry Pis, four FadeCandy boards, 2048 RGB LEDs and four 60 amp power supplies. It took about 100 hours to plan and build with another 50 hours spent writing the code.

We also made Tetris run on the Christmas tree but the video latency is too high to play that over the Internet :-)

That isn't the case. There are a whole host of tools, like Reactive Native and Appcelerator Titanium that interpret and execute JS on the device outside of UIWebView.

In the UK, fully-comprehensive insurance can often be cheaper than third-party only cover.