[flagged]
Well I mean... I like the idea of you having autonomy over your own bio .. :P I kinda want to see how this xss vuln plays out.
Show HN: Markdown HN profiles at {user}.at.hn
51–60 of 169 posts
Re: Show HN: Markdown HN profiles at {user}.at.hn
#52And are you prepared to respond to GDPR and other jurisdiction requirements of data collection and management?
My hope is that, since it's opt-in, and people are publicly publishing this stuff, It'd be alright. Dunno.
Re: Show HN: Markdown HN profiles at {user}.at.hn
#53And are you prepared to respond to GDPR and other jurisdiction requirements of data collection and management?
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...
Re: Show HN: Markdown HN profiles at {user}.at.hn
#54And are you prepared to respond to GDPR and other jurisdiction requirements of data collection and management?
No action is needed if OP doesn’t store unnecessary info or use spyware
Re: Show HN: Markdown HN profiles at {user}.at.hn
#55[flagged]
Well I mean... I like the idea of you having autonomy over your own bio .. :P I kinda want to see how this xss vuln plays out.
Haha yeah, I realized he fixed the obvious one with javascript injection but since markdown doesn't convert html I figured a normal html redirect would work and it did!
Re: Show HN: Markdown HN profiles at {user}.at.hn
#56so perhaps some kind of collaborative filtering or cohort graph or AI summary can be added on top of this? What other users often comment on the same kinds of stories? Who often replies etc? What kind of stories do they engage with? Etc.
Re: Show HN: Markdown HN profiles at {user}.at.hn
#57Earlier quoted context omitted.
That second one doesn't give me a 404 but correctly shows your profile.
Weird, it also works for me now, I could've sworn it didn't work before. The firebase API on the other hand remains case-sensitive: https://hacker-news.firebaseio.com/v0/user/Retr0id.json => full response https://hacker-news.firebaseio.com/v0/user/retr0id.json => null
I think maybe you're thinking about the "threads" list/page:
- https://news.ycombinator.com/threads?id=Retr0id - Works
- https://news.ycombinator.com/threads?id=retr0id - Doesn't work
Which somehow I guess the API is using.
Re: Show HN: Markdown HN profiles at {user}.at.hn
#58> opt-in only by adding a slug to your bio I really like this. It’s respectful of people’s wishes to not be added to any random site, and at the same time the way to give consent advertises the service. Ethical and effective business practice? Yes, please. If only all things posted to HN were like this. PS: It says something about my disillusionment with most software projects these days that I have nothing but prais…
> It says something about my disillusionment with most software projects My disillusionment is I don't trust any of you. My devices have so few apps, that it could almost be mistaken for a clean install. In coding, I use very few libraries because I don't trust anyone. I don't have time to read all of the code of the dependencies. Also, by using libraries, I don't learn how to do what is needed to be done. I hate bla…
[deleted]
Re: Show HN: Markdown HN profiles at {user}.at.hn
#59I'm getting Internal server error 34. Which is one I'd never seen before. ;)
Same here... HN kiss of death maybe? Too bad. Looks fun.
Re: Show HN: Markdown HN profiles at {user}.at.hn
#60Earlier quoted context omitted.
Weird, it also works for me now, I could've sworn it didn't work before. The firebase API on the other hand remains case-sensitive: https://hacker-news.firebaseio.com/v0/user/Retr0id.json => full response https://hacker-news.firebaseio.com/v0/user/retr0id.json => null
I think maybe you're thinking about the "threads" list/page: - https://news.ycombinator.com/threads?id=Retr0id - Works - https://news.ycombinator.com/threads?id=retr0id - Doesn't work Which somehow I guess the API is using.
Possibly, although according to this[0] the main profile URL used to be case-sensitive too. It must've changed recently, but I have no idea when.