dvrj101's comments

On: A new form of verification on Bluesky

[dvrj101]

> how does the bsky team decide which orgs can be trusted?

read again, slowly perhaps about first layer of verification.

On: The Cost of Being Crawled: LLM Bots and Vercel Image API Pricing

[dvrj101]

Nope they have been ignoring robots.txt since the start. There are multiple posts all over the internet.

On: Everyone knows all the apps on your phone

[dvrj101]

phones had/some still have user profile/account option so you can do this on a single phone

[Explore4526 → dvrj101]

Why is that feature removed by companies? It still exists in vanilla Android, but for some reason the phones sold don't have it.

On: Google to buy Wiz for $32B

[dvrj101]

> Corporations care about their data a lot and would cancel deals over this. Since you have mentioned "a lot" share few examples, pls.

On: Robotics and ROS 2 Essentials

[dvrj101]

https://foxglove.dev/blog/introducing-foxglove-schemas-to-vi...

On: Tell HN: John Friel my father, internet pioneer and creator of QModem, has died

[dvrj101]

is this his youtube channel : https://www.youtube.com/@JohnnyMarauder , the last video is : "Getting an old copy of Qmodem running on a restored IBM 5150 PC." with

description: "I wrote Qmodem originally on an IBM PC Clone, the Tava PC. I've restored an actual IBM 5150 with the same cards and software from back in the day, and here it is running Qmodem V3.1"

[AaronFriel → dvrj101]

Yeah, that's his channel.

On: Ask HN: Product to improve monitoring and documentation: a good idea?

[dvrj101]

so the documentation get's parsed by a program which detect hook parts , set them up and look for any trigger then update that part of documentation to show that particular node is active?

edit- or the hooks are already set the program just link them to which part of documentation get's update. Like a tag system?

[d--b → dvrj101]

Thanks for the feedback.

I was thinking much more freeform.

In the code, you'd send events to the backend using something like:

`post_to_aerial("task_X","some args")`

In Aerial, you would then match "task_X" to some icon or some part of your documentation. The way I envision it is that Aerial is very visual, so it's mostly diagrams.

In a way, if you start by drawing the diagram the way you envision things to run, you could setup the monitoring before the code itself, in a sort of "monitoring-driven-development".