Aleksandrs A.

u/aleksandrs@feddit.uk
1 posts · 34 comments

Recent posts

Recent comments

I disclosed monetisation at first place because that can actually bias what I recommend. On the other hand AI just helps me with drafting big texts and content, it does not make any decisions so in my head it looked like just another tool I've used during the development and I haven't really thought it's worth disclosing it.

Fair point though, I'll keep that in mind next time.

I am actually eager to fix, not delete. Every claim is sourced so if a company finds any assessment wrong the first thing I want is them to show me and I will correct it asap. There were couple of cases already.

The removal is for other case tho. Some companies just don't want to be on the list. At some point keeping them there will not help anyone. The whole point of this website is to help people find good options, not pointing which is worse. My thought here is that no good product would claim for a removal anyway.

I will look for a way to work this around tho, as displaying something the company doesn't like might still be very useful for the users.

If you mean this page https://euvetted.com/alternatives/hetzner than the first blue line means the product that we compare against, Hetzner in this case. In case if the base product is US the line is red like here https://euvetted.com/alternatives/aws

I've intentionally added alternative to X for some most obvious European products like Proton or Hetzner in this case.

Please let me know if either of these are confusing or do not make sense. Thanks!

Ha, fair and I won't pretend otherwise. The write-ups are AI-drafted. I'm one person covering everything and there is no real option to do it otherwise.

But the line I care about is this. The prose is AI, the facts aren't. Everything you see like ownership, cloud act exposure, hosting region, sub-processors, feature comparisons is verified manually.

And you are right that the tone needs to be fixed.

Agreed and good timing, because that page already exists, it's just not linked well. There's a full write-up at /insights/cloud-act-exposure (why it matters, who's exposed, the numbers across the directory) way more than the About page covers. The gap is exactly what you said: every "CLOUD Act" mention should point to it instead of assuming you'll go find it. I'll wire up the ⓘ link. Thanks.