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

Show HN: HackerForums.co, a forum for the crowd that hangs out on HN

hackerforums.co

Post reply on HN
Print view View original

81–90 of 140 posts

Re: Show HN: HackerForums.co, a forum for the crowd that hangs out on HN

#81

Post by dchuk »

swaggyBoatswain wrote: post #74

I think its a great idea. Topics shouldn't be the same as those found on hackernews, those would be redundant though. I would suggest using discourse.org instead of rolling your own phpBB instance

Well, it's been rolled :)

I'm honestly not the biggest fan of discourse, though I do appreciate it as a project. I like the old school BB style.

One opportunity we have as a forum is to create continuity between the trending conversations and more "long term" discussions that are difficult to have on a platform that is churning out new content constantly and lacks notifications about replies etc

Re: Show HN: HackerForums.co, a forum for the crowd that hangs out on HN

#87

Post by LambdaComplex »

keithnz wrote: post #83

I wonder if a discord for HN would be better? I've been keep track of HN related things people have built and added this also https://github.com/keithn/HackerNewsCommunity

I feel like most of HN would rather have an IRC server/channel

Re: Show HN: HackerForums.co, a forum for the crowd that hangs out on HN

#88

Post by lgregg »

dchuk wrote: post #2

This site was borne of the discussion here: https://news.ycombinator.com/item?id=17068138 (Specifically this part of the thread: https://news.ycombinator.com/item?id=17071224 ) I spun up an instance of phpBB (trying to keep costs down) and customized a ThemeForest theme to make it not ugly. I'll post a thread today that lists all of my notes from the setup process of the site for anyone interested. I'm a huge fan of…

that is a throwback, starting a phpBB forum was one of my first forays into the web back in 2001.

Re: Show HN: HackerForums.co, a forum for the crowd that hangs out on HN

#89

Post by angelsl »

zrm wrote: post #67
toomuchtodo wrote: post #36

Earlier quoted context omitted.

Keep in mind, there are situations where the website you're using is interfacing to backend systems that have constraints that can't easily be changed (colloquially known as "legacy systems"). Feedback is good, but change takes time.

Passwords should be hashed client-side anyway, so the real issue there is how to encode the password hash in a way that satisfies the legacy system. But this is usually plausible, e.g. by base64 or hex encoding the hash to avoid disallowed characters and then appending specific characters that satisfy the set of required characters.

This just makes the password the hash of the user's passphrase.

Re: Show HN: HackerForums.co, a forum for the crowd that hangs out on HN

#90

Post by mygo »

zrm wrote: post #67
toomuchtodo wrote: post #36

Earlier quoted context omitted.

Keep in mind, there are situations where the website you're using is interfacing to backend systems that have constraints that can't easily be changed (colloquially known as "legacy systems"). Feedback is good, but change takes time.

Passwords should be hashed client-side anyway, so the real issue there is how to encode the password hash in a way that satisfies the legacy system. But this is usually plausible, e.g. by base64 or hex encoding the hash to avoid disallowed characters and then appending specific characters that satisfy the set of required characters.

You don’t need to hash a password over the client so long as it’s sent over an encrypted network. The goal of submitting a password is that it’s not sent in open plaintext. Otherwise even if you hash it on the client, the plaintext hash can still be intercepted and used, exactly as-is, as the plaintext password.
Post reply on HN