Node RED VS hackernews-personal-blogs

Good question.

I expect that we're moving into a phase of AIs talking to AIs, and initially it'll be wasteful (because it'll be mostly English), but eventually, they'll derive their own language and seamlessly upgrade protocols when they determine they're talking to an AI. No clue how that will come about or what that language will look like, but honestly, it's kind of exciting.

Really interesting to think about how they might handle context, as well. Even though we have much bigger context windows (and they'll only get larger), context management is still a resource-management issue, which we'll probably continue to refine, as well. Imagine different strategies for managing both what is brought into the context of each request, as well as what form it could take (level of detail, additional references or commentary on it, etc). Things could get really unreadable even in English, and still be very interpretable for an LLM.

W.r.t. the graph-oriented interfaces, are you thinking something like Node-RED [1]? I'm seeing more and more people mention having LLMs produce non-text or structured outputs, like JSON, UI, and other things. Easy to imagine an LLM that wires together various open-source platforms, on-demand. Something like Node-RED for pipelines/functions, some UI tools for visualization/interactivity, other platforms for messaging, etc...

[1] https://nodered.org/

I skipped to chapter 9 in the article ("Clogged"), and it looked like Pipes failed because it didn't have a large enough team or a well-defined mission. As a result they couldn't offer a super robust product that would lure in enterprise users. "You could not purchase some number of guaranteed-to-work Pipes calls per month" is the quote from the article.

The reason I think that interesting is because that's the model these days for everything from AI tokens to Monday.com seats. It makes me feel like Pipes was before its time.

That said I've been collecting different "business glue" products that are similar to Pipes. To me, like you say, they aren't as interesting, exciting and intuitive as Pipes was, but maybe it just takes a little more digging. I tried to focus on open source tools but some aren't.

- n8n io: https://n8n.io/integrations/mondaycom/

- Node-RED: https://nodered.org/ (just read about this one in this thread)

- trigger dev: trigger.dev

- automatisch.io: https://automatisch.io/docs/

- Activepieces: https://www.activepieces.com/docs/getting-started/introducti...

- Huginn: https://github.com/huginn/huginn

- budibase: https://budibase.com/

- windmill: https://www.windmill.dev/

- tooljet: https://www.tooljet.com/workflows

- Bracket: https://www.usebracket.com/pricing (just SalesForce <-> PostgreSQL)

- Zapier: zapier.com/

Anyway I hope some of these are fun!

Source: https://github.com/node-red/node-red

I believe Node-RED (https://nodered.org/) the way to go. It's just an NPM package to install and you can run it how ever you wish (even on Windows). It has a friendly and helpful community with even the main developers tirelessly answering even beginner level questions. In fact the community forum its THE friendliest forum I've ever been a member of by a large margin. Node-RED's development is supported by the JS Foundation and it's completely free and open source. It's widely used in the industrial automation industry and even integrated by some PLC manufacturers such as Siemens.

Does anyone know if their are plans to implement something like this (or if there are already custom nodes out there). I'd like to experiment with things like looping and incrementing values (like a for loop) for a Ksampler for example. It's only an example though, so I am not looking for a ksampler specific solution; just a generic way to have a variable (e.g. Seed value), run some nodes that use that value, increment the value, and then loop back to the beginning until some sort of condition is met. Node-Red (an event driven node based programming language) has this functionality so it could defintely work in a node based environment such as ComfyUI (see here).

Someone compiled this a while ago which is a pretty good starter list for content discovery: https://github.com/outcoldman/hackernews-personal-blogs

I've imported most of them into https://app.recessfeed.com/ and found some nice ones to follow through that

I didn't know about your project and used https://blogs.hn

What's also helpful to get the feeds directly to your RSS Reader: https://github.com/outcoldman/hackernews-personal-blogs

However, I also needed to put some work into it and remove some blogs, because they're written in a foreign language or just not that interesting for me.

The list of HN users personal blogs is quite good:

https://github.com/outcoldman/hackernews-personal-blogs

> I was looking at your HN OPML file on GitHub [0] and noticed that the `xmlURL` and `htmlURL` attributes are the same for each entry; the `htmlURL` currently points to the feed rather than the site. Do you happen to have the original HTML URLs available? Would be nice to have both. (Secondarily, I'm guessing some of the `type` attributes should probably be "atom" rather than "rss"?)

I'm just using the file that someone else made, but I guess they didn't really make the distinction between those URLs in the code, though it shouldn't be too hard to modify: https://github.com/outcoldman/hackernews-personal-blogs/blob...

It is also true that there are both RSS, Atom and possibly other feed types mixed in there. What I did for my site was to crawl through all of those feeds and process them one by one: get all of the posts, do some ordering and grouping and output everything as RSS feeds.

For example, here's the top 100 user feeds for 2023: https://hn-blogs.kronis.dev/feed-top100.xml

Those have HTML links for each of the posts, though I'm afraid it's not exactly what you're asking for (the HTML URLs for the sites/feeds themselves), because I don't actually store that anywhere in my case.

Added a note https://github.com/outcoldman/hackernews-personal-blogs/tree...

I checked yours, the issue is that you are escaping + in application/rss+xml, when it should be just application/rss+xml

I have updated the code and will re-generate. I am not sure if what you are doing is allowed or not.