mnau

Please elaborate on less strict rules for Gdpr? There is Record of Processing Activities exemption for <250, but if you have to comply with Gdpr (and you do), you need essentially same info as Ropa and of course it has to be up to date. How else can you ensure you are in compliance?

> Do YOU want to have that preemie die because the evil hippies want to take away your plastic, mnau?

Honestly, you sound like you have problems. Personal attack, tangent from original theme "don't have plastic in the ocean" to multi paragraph rant about RRR. Have a nice day.

> automatically sort plastic both by type and color, which is quite impressive

.... I am sorry, but how can that impress you? That would be impressive in 1990. Today, with deep learning and all AI, I would consider having robots open trash bags and sort whatever is inside for more processing (e.g. organic waste, plastic and so on, depending on how dirty it is) only slightly impressive. Unlike Amazon pick up challange, they don't need to be perfect.

> distract from real unsexy solutions like grab the plastic in rivers BEFORE they make it to the ocean.

They pivoted to mostly river cleanup (interceptors) many years ago. And they clearly show that it is just one step back, not a full time solution. Ocean cleanup is last step, river grab is the step before that and having proper garbage collection would be best.

Which is literally written in TFA:

> Now they mostly intercept plastic when it first leaves rivers and enters the ocean instead of trying to scoop it out of the middle of the ocean, though the open ocean work is still mentioned on their website

HIP was such a self-own and clear demonstration of AMD software capabilities... well, the lack of software capabilities. HIP was hard-coded for one GPU architecture. CUDA did it right, it has a intermediate virtual assembly PTX and driver compiles it to whatever actual instruction set card actually uses.

Imagine a meeting where they signed off on that. So each developer will have to provide a different binary for each of our architectures? Yep. And once we release the new architecture, developer will have to recompile his program for the new architecture? Yep. Sounds good to me.

> It was very useful for me

Exactly. You want others to change to fulfill your needs. Their priorities and needs are different. In this case, it was evaluated and found not to be useful (cost > benefits).

Azure is not the best, but it mostly works. GitHub gets only 98% reliability for git operation component, reading and committing. This is the most basic component. The fact they are not on this 24/7 and it isn't fixed is the result of a culture (=what is prioritized, what quality is accepted).

Compare costs, monetary risk and TTM to renewables with battery backup. Nuclear is dead as a doornail.

Look at the nuclear buildup. Vogtle in US 10 years. Hinckley Point C is estimated to be 13 years. Flamanville 3 took 17 years. All these years you put money in and get nothing out. It's a disaster for balance sheet. Instead, you can build renewables plus batteries and have it connected within a year, generating revenue.

I would argue that it can be circumvented, not that it won't help. If a human uses his/her signature for content farm, it can be flagged as such.

Signal to noise ratio is getting *lower (EDIT: was higher) than ever. I don't see a way out of this other than "human certified" digitally signed authorship (e.g. by using eIDAS in EU). There could be a proxy to at least retain pseudo-anonymity, but trackable to a human. Tragedy of commons strikes again.