snlr

https://github.com/sindresorhus/awesome-awesome-awesome-awes... :D

I take my list to 1001 entries and only then start pruning. I'm at half that now so I know I currently have non-awesome entries. However, during this ramp-up I collect the information needed to programmatically prune some day. A repo without recent commits might be perfect and therefore awesome. Taking some time to add more and more signal to each entry will eventually yield the metrics needed for cutting off the tail.

Expecting awesome to mean curated manually is unrealistic now. But there are plenty of opportunities to make an awesome list compelling via automation.

One of many examples is WebMCP-support. How often did you find a truly awesome, perfectly maintained list and felt overwhelmed? Then you bookmark it and get a coffee. A list with proper agent-support will allow me to cut through the non-noise. Finally the list will be actually helping me instead of being a bookmark.

There are more examples like this. Awesome Lists have a golden future as one of the knowledge resources that are not gatekept.

"Publisher" was created as a plugin for ChatGPT's web UI. It's a regular MCP server, so any client is technically supported. The basic thought is making website publishing "zero-click" by sending the data to the user's own Cloudflare account directly.

I'm assuming that I introduced specific security issues while simplifying this workflow. Docs note that users currently have to place considerable trust in the vendor. The code itself is written almost exclusively by Astra 6.

I'm looking for advice how to tighten security around such a plugin (more so the installer part). How to prove to the user that the code that is about to be installed in their CF Workers is not malicious or compromised?

Cleaned-up notes on security are at https://github.com/JumperMCP/chatgpt-to-public-page#security... and more slop-y ones in https://github.com/JumperMCP/chatgpt-to-public-page/blob/mai...