0des

139 ms·

1. 1831.▲
   by 0des 5y ago

   Needed a thing for a project, so I built it, only to find out the next day when I showed it to a friend that I had basically built a really terrible crayon-version of json web tokens. Surely I'm not the only one this happens to.. Anywa
2. 1832.▲
   Show HN: Ticket-Agent – Simple Session Auth as a Service(hackmd.io)

   2 points by 0des 5y ago|1 comments
3. 1833.▲
   by 0des 5y ago

   Thanks for checking it out! To be clear, there's nothing for sale here. It's MIT licensed, anybody can de-brand it and use it as they want- the main draw for me is that some day I want to be able to have these features available t
4. 1834.▲
   by 0des 5y ago

   This was originally a piece that I wrote for Software Engineering Daily that never got picked up, so I put it on HackMD and posted it here in hopes to generate some discussion around feeds. It's something I'm passionate about and
5. 1835.▲
   Nobody cares about feeds anymore(hackmd.io)

   5 points by 0des 5y ago|3 comments
6. 1836.▲
   by 0des 5y ago

   As much as it hurts to say it, this seems like the safe way to err on the side of caution.
7. 1837.▲
   by 0des 5y ago

   This is great! I love these types of podcasts. Adding this one to my subscriptions list right now. A bunny CDN episode would be fun. Thanks for putting this podcast on my radar.
8. 1838.▲
   by 0des 5y ago

   Hey there! First off, thanks for the submission. It's a refreshing take on the homepages we knew and loved. I'm curious what you plan to have in the paid tier. Can you detail some of your ideas with regard to that? Also, is there
9. 1839.▲
   by 0des 5y ago

   I found this podcast [0] by Radiolab on the topic to be quite the eye opener. (ear opener?) [0] - https://www.wnycstudios.org/podcasts/radiolab/articles/alpha...
10. 1840.▲
    by 0des 5y ago

    Glad you made it through, wishing you the best on your new life.
11. 1841.▲
    Solar Protocol(branch.climateaction.tech)

    1 points by 0des 5y ago|0 comments
12. 1842.▲
    by 0des 5y ago

    The cohort concerned about tracking, one would think, would not be deterred by broken CSS considering they already live in a JS-free world and might be used to some visual-compromise when browsing.
13. 1843.▲
    by 0des 5y ago

    Just curious, how is something like this typically handled/addressed internally? Is it one of those live and learn type situations or was there any consequence other than your email getting flooded?
14. 1844.▲
    by 0des 5y ago

    Sweet, as someone who's never reached the front page, or the second page, I applaud this effort.
15. 1845.▲
    Show HN: Lens – lens Is not ls(github.com)

    2 points by 0des 5y ago|0 comments
16. 1846.▲
    by 0des 5y ago

    Thanks for taking a moment to review the spec > Which keys are mandatory and which are optional? I think that the pictures, long descriptions, web page URLs, and possibly some others, should be optional. It might only be a podcast and no
17. 1847.▲
    by 0des 5y ago

    Thanks for commenting, this is the exact type of critical analysis and collaboration that was being sought in posting here. > It's also a bit weird that the yaml keys are all lowercase but the other two formats are camel cased That&
18. 1848.▲
    Show HN: Loud – Podcast-first feed syndication protocol(loud-feed-format.github.io)

    7 points by 0des 5y ago|4 comments
19. 1849.▲
    Show HN: Proposal for a podcast-first feed syndication protocol(hackmd.io)

    2 points by 0des 5y ago|0 comments