Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: SmallDocs – Markdown without the frustrations

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 53 posts

Re: Show HN: SmallDocs – Markdown without the frustrations

#11

Post by FailMore »

pdyc wrote: post #10

i also used fragment technique for sharing html snippets but url's became very long, i had to implement optional url shortener after users complained. Unfortunately that meant server interaction. https://easyanalytica.com/tools/html-playground/

Really nice implementation by the way.

Re URL length: Yes... I have a feeling it could become an issue. I was wondering if a browser extension might give users the ability to have shorter urls without losing privacy... but haven't looked into it deeply/don't know if it would be possible (browser extensions are decent bridges between the local machine and the browser, so maybe some sort of decryption key could be used to allow for more compressed urls...)

Re: Show HN: SmallDocs – Markdown without the frustrations

#12

Post by pdyc »

FailMore wrote: post #11
pdyc wrote: post #10

i also used fragment technique for sharing html snippets but url's became very long, i had to implement optional url shortener after users complained. Unfortunately that meant server interaction. https://easyanalytica.com/tools/html-playground/

Really nice implementation by the way. Re URL length: Yes... I have a feeling it could become an issue. I was wondering if a browser extension might give users the ability to have shorter urls without losing privacy... but haven't looked into it deeply/don't know if it would be possible (browser extensions are decent bridges between the local machine and the browser, so maybe some sort of decryption key could be used…

i doubt it would be possible, it boils down to compression problem compressing x amount of content to y bits, since content is unpredictable it cannot be done without having intermediary to store it.

Re: Show HN: SmallDocs – Markdown without the frustrations

#13

Post by mystickphoenix »

pdyc wrote: post #10

i also used fragment technique for sharing html snippets but url's became very long, i had to implement optional url shortener after users complained. Unfortunately that meant server interaction. https://easyanalytica.com/tools/html-playground/

For this use-case, maybe compression and then encoding would get more data into the URL before you hit a limit (or before users complain)?

I.e. .md -> gzip -> base64

Re: Show HN: SmallDocs – Markdown without the frustrations

#15

Post by big_toast »

URL data sites are always very cool to me. The offline service worker part is great.

The analytics[1] is incredible. Thank you for sharing (and explaining)! I love this implementation.

I'm a little confused about the privacy mention. Maybe the fragment data isn't passed but that's not a particularly strong guarantee. The javascript still has access so privacy is just a promise as far as I can tell.

Am I misunderstanding something and is there a stronger mechanism in browsers preserving the fragment data's isolation? Or is there some way to prove a url is running a github repo without modification?

[1]:https://sdocs.dev/analytics

Re: Show HN: SmallDocs – Markdown without the frustrations

#16

Post by FailMore »

big_toast wrote: post #15

URL data sites are always very cool to me. The offline service worker part is great. The analytics[1] is incredible. Thank you for sharing (and explaining)! I love this implementation. I'm a little confused about the privacy mention. Maybe the fragment data isn't passed but that's not a particularly strong guarantee. The javascript still has access so privacy is just a promise as far as I can tell. Am I misunderstand…

Thanks for the kind words re the analytics!

You are right re privacy. It is possible to go from url hash -> parse -> server (that’s not what SDocs does to be clear).

I’ve been thinking about how to prove our privacy mechanism. The idea I have in my head at the moment is to have 2+ established coding agents review the code after every merge to the codebase and to provide a signal (maybe visible in the footer) that, according to them it is secure and the check was made after the latest merge. Maybe overkill?! Or maybe a new way to “prove” things?? If you have other ideas please let me know.

Re: Show HN: SmallDocs – Markdown without the frustrations

#17

Post by big_toast »

FailMore wrote: post #16
big_toast wrote: post #15

URL data sites are always very cool to me. The offline service worker part is great. The analytics[1] is incredible. Thank you for sharing (and explaining)! I love this implementation. I'm a little confused about the privacy mention. Maybe the fragment data isn't passed but that's not a particularly strong guarantee. The javascript still has access so privacy is just a promise as far as I can tell. Am I misunderstand…

Thanks for the kind words re the analytics! You are right re privacy. It is possible to go from url hash -> parse -> server (that’s not what SDocs does to be clear). I’ve been thinking about how to prove our privacy mechanism. The idea I have in my head at the moment is to have 2+ established coding agents review the code after every merge to the codebase and to provide a signal (maybe visible in the footer) that, ac…

No, I don't have any good ideas. Just hoping someone else does, or that I'm missing something.

I think it's in the hands of browser vendors.

The agent review a la socket.dev probably doesn't address all the gaps. I think you're already doing about as much as you reasonably can.

Re: Show HN: SmallDocs – Markdown without the frustrations

#18

Post by FailMore »

big_toast wrote: post #17
FailMore wrote: post #16

Earlier quoted context omitted.

Thanks for the kind words re the analytics! You are right re privacy. It is possible to go from url hash -> parse -> server (that’s not what SDocs does to be clear). I’ve been thinking about how to prove our privacy mechanism. The idea I have in my head at the moment is to have 2+ established coding agents review the code after every merge to the codebase and to provide a signal (maybe visible in the footer) that, ac…

No, I don't have any good ideas. Just hoping someone else does, or that I'm missing something. I think it's in the hands of browser vendors. The agent review a la socket.dev probably doesn't address all the gaps. I think you're already doing about as much as you reasonably can.

Thanks. The question has made me wonder about the value of some sort of real time verification service.

Re: Show HN: SmallDocs – Markdown without the frustrations

#20

Post by FailMore »

pbronez wrote: post #19

Cool project. Heads up - there’s a commercial company with a very similar name that might decide to hassle you about it: https://www.sdocs.com/

Thanks + thanks for the heads up. I will see what happens. It's a domain-name war out there!
Post reply on HN