FailMore

9 ms·

1. 91.▲
   The surprisingly complex journey to text-selectable client-side generated PDFs(sdocs.dev)

   86 points by FailMore 5mo ago|62 comments
2. 92.▲
   by FailMore 5mo ago

   I've built side projects for years. My most recent one (also Markdown related [1]) is my first open source one and I've found it to be the most rewarding experience by far. So far I have 54 stars on GitHub and have had people emai
3. 93.▲
   by FailMore 5mo ago

   I noticed you switched from paid to free? What was behind that decision? I’m very interested in Markdown related tools, I’m building one myself [1]. How have you found working with the MCP? I went for a CLI tool myself. Have you found that
4. 94.▲
   by FailMore 5mo ago

   I really like the docs idea. I think it’s great to automatically render the side menu. The prevalence of Markdown from agents made me work on something similar too. My Show HN for a similar cli + web based solution ( https://sdocs
5. 95.▲
   by FailMore 5mo ago

   This is a beautiful project. Well done. This problem has risen to the top of many people’s minds at this moment (including mine!). My Show HN for a similar cli + web based solution ( https://sdocs.dev ) was on the /show page
6. 96.▲
   by FailMore 5mo ago

   This is a beautiful project. Well done. This problem has risen to the top of many people’s minds at this moment (including mine!). My Show HN for a similar cli + web based solution ( https://sdocs.dev ) was on the /show page
7. 97.▲
   by FailMore 5mo ago

   I built https://sdocs.dev which solves this pain point. You can “sdoc file.md” to instantly open it. It was discussed on Hacker News here: https://news.ycombinator.com/item?id=47777633
8. 98.▲
   by FailMore 5mo ago

   This is very cool. It was obvious to me how to actually mix the paints, and I'd like a white for that.
9. 99.▲
   Show HN: Proving sdocs.dev is running the public code(sdocs.dev)

   2 points by FailMore 5mo ago|0 comments
10. 100.▲
    Proving sdocs.dev is running the public code(sdocs.dev)

    2 points by FailMore 6mo ago|0 comments
11. 101.▲
    by FailMore 6mo ago

    Yep , exactly
12. 102.▲
    by FailMore 6mo ago

    Nice, I enjoyed it. Fyi I think you should edit the title to be "Show HN: <title>". This will mean it will be on the /show ( https://news.ycombinator.com/show ) page.
13. 103.▲
    Ask HN: Do you comment on a code/Markdown files, then get your agent to reread?

    2 points by FailMore 6mo ago|2 comments
14. 104.▲
    Ask HN: Is your Claude pausing more frequently?

    1 points by FailMore 6mo ago|1 comments
15. 105.▲
    by FailMore 6mo ago

    Interesting idea, do you have any ideas of states that could be particularly useful to have? It's not something I have thought of before
16. 106.▲
    by FailMore 6mo ago

    Thanks very much, maybe I can add something to ‘sdoc’ to make that easier
17. 107.▲
    by FailMore 6mo ago

    That’s exactly what happens. We encrypt client side. The sever only gets encrypted data. You can inspect the network request to see what the sever receives. Your decryption key always stays client side (in the url fragment). Also, the short
18. 108.▲
    by FailMore 6mo ago

    https://sdocs.dev/trust Now lets you verify you're being served the actual open source code
19. 109.▲
    by FailMore 6mo ago

    My solution is now live at https://sdocs.dev/trust . Open to feedback
20. 110.▲
    by FailMore 6mo ago

    Tyvm
21. 111.▲
    by FailMore 6mo ago

    I think the next thing I want to do (but not sure how to implement yet) is to make it easy for your agent to go from SDocs url to content. I don't know if that's via curl or a `sdoc` command, or some other way... That could includ
22. 112.▲
    by FailMore 6mo ago

    That's basically exactly what I'm working on now actually. We will let you compare all the publicly served files with their hashes on github
23. 113.▲
    by FailMore 6mo ago

    I have something coming out soon (just working on it). Your client (browser) has hashing algos built into it. So the browser can run a hash of all the front end assets it serves. Every commit merged into main will cause a hash of all the pu
24. 114.▲
    by FailMore 6mo ago

    I feel like things have changed as the main interface for code has (for some) become an agent running in the cli. I feel like we (certainly I) check my code editor way less frequently than before. Because of that (for me) easily reading&#x2
25. 115.▲
    by FailMore 6mo ago

    I feel your pain. My project is https://sdocs.dev , the homepage is actually the rendering of a markdown file (sdoc.md), so you can see how SDocs renders immediately. There are some links on the homepage to other Markdown files w
26. 116.▲
    by FailMore 6mo ago

    Maybe not a direct answer to your question, but https://sdocs.dev has a cli built for agents. ‘sdoc —help’ and ‘sdoc schema’ and ‘sdoc charts’ teach your agent how to use it. You can try it with ‘npm i -g sdocs-dev’
27. 117.▲
    by FailMore 6mo ago

    This is cool. Can you tell me more about the :: blocks thing. I didn’t know that was a Markdown element. This problem has risen to the top of many people’s minds at this moment (including mine!). My Show HN for a similar cli + web based sol
28. 118.▲
    by FailMore 6mo ago

    Thank you. If you use an AI agent you might be able to tell it to curl the target website, extract the content into a markdown file and then sdoc it. It might have some interesting ideas with images (using the hosted URLs or hosting them yo
29. 119.▲
    by FailMore 6mo ago

    (I left a stand alone comment, but:) A little update: I added privacy-focused optional shorter URLs to SDocs. You can read more about the implementation here: https://sdocs.dev/#sec=short-links Briefly: https:/&#x2
30. 120.▲
    by FailMore 6mo ago

    A little update: I added privacy-focused optional shorter URLs to SDocs. You can read more about the implementation here: https://sdocs.dev/#sec=short-links Briefly: https://sdocs.dev/s/{short id}#k=