I was trying to make a new kind of rss reader. I call it rss viewer (like a image viewer, video player). You just open up the current feed(s) and you can browse it.
So no downloaded items, no feeds manipulation, no read/unread items.
The article view doesn't show the `item.content`, it parses the article url and extracts the header, image, content, which is formated in basic html and then translated to pretty terminal text.
I don't have very much of the paperwork. Just wanted to organize our home documents.
So I have a script that gets the image from scanner, then crops, corrects skew and runs tesseract on it. Then saves it as pdf with text.
Then I've written a shitty tool to make a fulltext index of all the pdfs in the current directory https://git.sr.ht/~ghost08/pdfq (It doesn't have documentation or even a README so ...)
And then I search like so: `cd my/documents/path && pdfq index && pdfq search "my query"`, it just prints the file names which match the query.
Also for backup I use syncthing, so I have 3 copies of all my documents on 3 computers in my house.
Maybe it is because all the major browsers, except for chrome, don't support them. I've build this, because the polymer project made web development exciting for me :) but javascript didn't. And go is awesoooome!
I thought web components was supposed to be a standardized native html thing, and not something ten different frameworks would provide for us, all with their own way of doing it.
Seems like the standardization effort has stalled out. Did React kill the perceived need for it?
You are right - it is standardized thing, thought right now Opera,Safari and Chrome supports v1 (basicly everything webkit/blink based) out-of-the-box, Firefox has that behind flag and not ready, Edge is implementing it.
You can use the polyfills for the older browsers for now, not everything can be polyfilled perfectly though.
Web components are a bit low-level, so you have libraries and frameworks like Polymer, X-Tag, Svelte, SkateJS building on top of the standard to make the development fun and friendly.
The article view doesn't show the `item.content`, it parses the article url and extracts the header, image, content, which is formated in basic html and then translated to pretty terminal text.