clipnotify VS software-ideas

The common xclip utility can be used to get or set clipboards. And, there's a tiny little utility script called clipnotify that I found really useful for debugging this. I cloned and built it, then ran it in a loop:

I rewrote this app for learning purposes, personal use and why not for sharing with other people to use as well.

Credit: I took inspiration from clipnotify.

I don't think time to learn bash or programming intuition can reasonably be included in the timeframe to build a product. It's assumed that time starts after you come up with the idea to do something, and retroactively saying "this project took me a year" for something you created in a few hours is ... odd.

I agree that the time spent to find the libraries and their documentation should be factored in, so I'd like to note that that part of the process took ... 3 ddg searches (so +a few mins).

?where does parcellite store clipboard data -> https://www.mankier.com/1/parcellite -> `clipboard -c`

?regex for url -> https://gist.github.com/securibee/f15f8c7aaa0593cc32fc30f585...

?get notified when something has been copied to clipboard linux -> https://askubuntu.com/questions/1167026/detect-clipboard-cop... -> https://github.com/cdown/clipnotify -> `while clipnotify;do`

:)

Using clipnotify[0], one could fix the busy-wait issue pretty easily.

[0] https://github.com/cdown/clipnotify

I think a version of this is what the internet needs but using headless browsers from the client and with a somewhat-centrally curated set of scraper "recipes" if you will. Basically a community curated/updated set of scraper logic per site (yes some trust is required) that essentially provides JSON data and/or APIs based on the site. Even just a neutered HTML equivalent of sites (e.g. amp w/out the Google and ads stuff) would be good.

Since it is all client side, it can be dubbed a "browser" not a "scraper" and one might hope popularity is high enough that active blocking of it is blatantly user hostile. Granted one hopes that, like EasyList and uBO and others have shown, the community can outpace site owners. Not appearing headless (tunneling captchas, literal mousemove events in pseudo-random human-like ways, etc) should be doable.

It's something I have thought about and once dubbed "recapitate" (https://github.com/cretz/software-ideas/issues/82) and plan to revisit. I have seen many versions of this attempted. We need to encourage shared data extraction tools.