Look through ~/Library, particularly in

  ~/Library/Application Support
  ~/Library/Caches
  ~/Library/Containers

After maybe half a minute searching...

https://skinive.org/

https://www.skinvision.com/

https://dermie.ai/

Not the person above but they're using Video.js 7.10.2 <http://videojs.com/>

You only need to read a bit further...

    The RDSEED instruction is intended for seeding a software PRNG of arbitrary width, whereas the RDRAND is intended for applications that merely require high-quality random numbers.

I don't know if you may like this idea or not. It still requires work, but it avoids spam and it does not turn the site into a community. On the other hand, it doesn't exactly bring the discussions into public view.

The solution would be something like:

1. Add a very simple form that sends you an email to the end of each guide. This isn't different from what you already have in your contact page but it encourages contacting you right when a particular guide is read.

2. Add, again at the end of each guide, a questions section. Format this in a way that could be similar to actual comments.

3. Every time you receive a question, you manually -yes, that means work, I know- add it as a new comment/pair of comments in that section and update the guide if necessary.

Advantages:

- Avoids spam on the site

- Single source of truth

- Encourages readers to contact

- Allows for easier filtering. Nothing gets on the site if you don't actually validate -and process- it.

Disadvantages:

- Still requires work from your part, though not as urgent as "live moderation".

- Does not completely feel like conversations. Doesn't let different readers directly answer each other.

- It may result in you getting spam in your email.

- It's not automated. Again: Nothing gets on the site if you don't actually validate -and process- it.

Neutral:

- Doesn't shift the site into a community. I point this as neutral because it isn't bad per se but I understand that you do not want that.

I've seen this sort of set up work mostly fine. It does require work from your part, I repeat, but that really depends on how well it works -how much feedback you get- and since you seem to want that feedback to update the site, then the effort should be worth it.

If you go this route, one recommendation: In that simple contact form, set the action to something like mailto:contact@allaboutberlin.com?subject=... and include some identifier in the subject that easily links it to the specific guide they're sending it from.

If you mean this [ https://news.ycombinator.com/item?id=45168644 ], then your main problem is that you don't even bother to bring any points to the discussion.

You just throw your random question, regardless of any possible merits or validity, without really making any argument at all. How can you expect to engage anyone's attention at all if you fail to make any effort yourself?

And that's not even mentioning what bell-cot's link points out.

So that's a valid reason to flag/ban posts?

Have you even read the guidelines?

https://news.ycombinator.com/newsguidelines.html

No, they are the same on all websites - censorship.

My impression is HN is being more heavily spammed lately. This needs heavier automated filters and this means more legitimate links end up marked dead on arrival.

The end result is poorer content and less variety.

It may well be just my impression though.

---

Other than that I don't know what exactly you mean by "their content within the sections" or what are you correlating to the rank.

You seem to be missing a link. It may be this one: https://krispy-the-goat.itch.io/prey-2006 this one: https://www.thegamer.com/prey-2006-fan-made-remaster-doom-3-... or maybe https://github.com/glKarin/com.n0n3m4.diii4a

I don't know why the sibling comment is dead (edit: was). I mean, it is a valid concern, if one doesn't know.

So, for slickytail and anyone who has the same question:

The code is actually compressed into a binary blob. You can see it if you just look at the source of https://0b5vr.com/0mix/0mix.html

A small script loads the blob and uncompresses it before running it through eval:

  fetch("#").then(t=>t.blob()).then(t=>new Response(t.slice(156).stream().pipeThrough(new DecompressionStream("deflate"))).text()).then(eval)

This is a common approach in browser demos and what is counted as "less than 64Kb" is that final html. A similar technique compresses it into a PNG.