> Might as well clean it up and make it machine readable at that point?
For me this looks pretty machine readable.
## Requirements
AUTH.1: Accessible to team members.
AUTH.2: Not be accessible to members with `quarantine` role.
AUTH.3: Redirects unauthorized users to /login.
AUTH.3.1: Redirect path includes `?error=unauthorized`.
AUTH.4: Requires fresh session, no older than 10 minutes.
Yes, yaml is more "parseble". But I still need to use some format conventions inside yaml. So I could just use them inside markdown as well.
https://fooqux.com/ - an experimental article aggregator about software development. For several years now, I've had a routine of collecting articles on topics that interest me throughout the week and then reading them over the weekend. To help organize and streamline this process, I created this website. The main idea is to gather articles in one place and process them with a LLM — categorize them, generate summaries, and try experimental features like annotations, questions, etc. I hope this service might be useful to others as well.
https://fooqux.com/ - an experimental article aggregator about software development. For several years now, I've had a routine of collecting articles on topics that interest me throughout the week and then reading them over the weekend. To help organize and streamline this process, I created this website.
The main idea is to gather tech articles in one place and process them with a LLM — categorize them, generate summaries, and try experimental features like annotations, questions, etc. I hope this service might be useful to others as well.
https://fooqux.com/ - an experimental tech article aggregator. For several years now, I've had a routine of collecting articles on topics that interest me throughout the week and then reading them over the weekend. To help organize and streamline this process, I created this website.
The main idea is to gather tech articles in one place and process them with a LLM — categorize them, generate summaries, and try experimental features like annotations, questions, etc.
I hope this service might be useful to others as well. You can sign up with github account to submit your articles as well. I would appreciate any feedback.
https://fooqux.com/ - an experimental tech article aggregator.
For several years now, I've had a routine of collecting articles on topics that interest me throughout the week and then reading them over the weekend. To help organize and streamline this process, I created this website.
The main idea is to gather tech articles in one place and process them with a LLM — categorize them, generate summaries, and try experimental features like annotations, questions, etc.
I hope this service might be useful to others as well. You can sign up with github account to submit your articles as well.
Thanks. For now, I don't have any plans to automate this process. Users simply add articles to the site, as in other aggregators, and can filter content by tags.
What would the ideal process of working with this kind of site look like for you?
For several years now, I've had a routine of collecting articles on topics that interest me throughout the week and then reading them over the weekend. To help organize and streamline this process, I created this website.
The main idea is to gather tech articles in one place and process them with a LLM — categorize them, generate summaries, and try experimental features like annotations, questions, etc.
I hope this service might be useful to others as well.
For me this looks pretty machine readable.
## Requirements
Yes, yaml is more "parseble". But I still need to use some format conventions inside yaml. So I could just use them inside markdown as well.