insane
at.hn
| insane | at.hn | |
|---|---|---|
| 2 | 2 | |
| 457 | 48 | |
| 0.9% | - | |
| 0.0 | 7.5 | |
| 9 months ago | 4 months ago | |
| JavaScript | JavaScript | |
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
insane
-
Show HN: Markdown HN profiles at {user}.at.hn
Since marked doesn't do it for you, make sure you sanitize the user input (the text on the user profiles) before rendering it to visitors.
Some libraries for doing that with good defaults:
- https://github.com/cure53/DOMPurify
- https://github.com/apostrophecms/sanitize-html
- https://github.com/bevacqua/insane
(right now your site looks vulnerable to XSS)
-
How To Parse and Render Markdown In Vuejs
Vue does not have as much support for Vue as there is for React. Examples are markdown-it, Remark.js, marked.js. But hopefully in the future, there should be more support, and after much research, I picked marked.js because it has the most stars and has zero vulnerability. Marked does not sanitize (meaning it does not secure HTML documents from attacks like cross-site scripting (XSS) ) marked output HTML as that feature is deprecated and has vulnerability but however, it supports the use of other libraries to secure output HTML such as DOMPurify (recommended), sanitize-html or insane.
at.hn
-
Show HN: Markdown HN profiles at {user}.at.hn
Usual note that IANAL, but looks like this service is opt-in, and only relists data which is already public on a user's HN profile.
If a user removes the reference from their bio, then the user's profile will be essentially inaccessible through the service (although technically the cached version would still be on the server. Adding a check to delete the file which matches the user's hashed ID here[0] would take care of profile deletions on subsequent accesses.
Failing all that, a user could request deletion and OP could delete the user's file manually.
There's nothing that seems overly onerous to implement to be (at least) GDPR compliant.
[0]https://github.com/padolsey/at.hn/blob/d4ca6702c558edf736652...
What are some alternatives?
sanitize-html - Clean up user-submitted HTML, preserving whitelisted elements and whitelisted attributes on a per-element basis. Built on htmlparser2 for speed and tolerance
remark - markdown processor powered by plugins part of the @unifiedjs collective
DOMPurify - DOMPurify - a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMPurify works with a secure default, but offers a lot of configurability and hooks. Demo:
marked - A markdown parser and compiler. Built for speed.
blog - Jeff Schnitzer's Blog
Hacker News API - Documentation and Samples for the Official HN API
markdown-it - Markdown parser, done right. 100% CommonMark support, extensions, syntax plugins & high speed
keybase-issues - A single repo for managing publicly recognized issues with the keybase client, installer, and website.
hncomments