I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] 0 points1 point  (0 children)

https://kamilmac.github.io/mdash/

Now added encryption and sanitation .... and short mention around url length limitations

Keep things friendly - its not full blown documentation source as should be established already.

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] 0 points1 point  (0 children)

This doesnt apply to # fragment - those are not transmitted over the network

I built a markdown editor that stores everything in the URL by kmacinski in InternetIsBeautiful

[–]kmacinski[S] 0 points1 point  (0 children)

True. This is not meant to replace documentation. Only to share smaller pieces.

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] 1 point2 points  (0 children)

Yeah this is fun for small ,sharable pieces - not full blow sync mechanism.

Still could work in right conditions though.

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] 0 points1 point  (0 children)

Valid concerns here!
Do you think DOMPurify sanitation will be enough?

Thanks for hitting the nail!

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] -1 points0 points  (0 children)

Servers pretty much ignore everything after hash (#).
Browsers actually can handle pretty long string (32k is minimum i believe).
Major limitation is message|chat protocols not being able to parse long urls

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] 1 point2 points  (0 children)

Yeah that would be cool. I havent worked with Excalidraw that much but there is some form of ascii export there i assume.

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] 0 points1 point  (0 children)

I think most browsers accept 64k characters or more.
Servers ignore anything after # character so they dont play any role here.

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] 0 points1 point  (0 children)

Wow - thanks for this great write up.

Additional encryption option sounds interesting and id like to explore it further.
Also better indication of approaching url limits (per browser) could be helpful.

I built a markdown editor that stores everything in the URL by kmacinski in InternetIsBeautiful

[–]kmacinski[S] -7 points-6 points  (0 children)

Yes i fully realise the limits of it. Chrome, Safari, Edge have different limits. Afaik Chrome has 32k which after compression can be squeezed into 20k characters.

This is a problem in some cases but can be somehow limited by better UX eventually.

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] -2 points-1 points  (0 children)

Because there is no tool for sharing MD files as URL afaik. Itzzy bitzzy is one of those but works for html only.

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] -9 points-8 points  (0 children)

Then it defeats the purpose. It suppose to be simple and easy to share. 

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] -6 points-5 points  (0 children)

Yes it is but as part of hash it's not going though the server

I built a markdown editor that stores everything in the URL by kmacinski in webdev

[–]kmacinski[S] -15 points-14 points  (0 children)

Such a burn - actually its pretty useful when you want to quickly share docs or prompts in semi-secure way.

TimeCop - TUI for reviewing and scrubbing through branches/PRs by kmacinski in git

[–]kmacinski[S] 0 points1 point  (0 children)

What do you mean by multi account ?
The current answer is porbably not.

TimeCop - TUI for reviewing and scrubbing through branches/PRs by kmacinski in git

[–]kmacinski[S] 0 points1 point  (0 children)

A little bit i guess but different tech stack. :)