Show HN: HackerForums.co, a forum for the crowd that hangs out on HN
hackerforums.co
hackerforums.co
Please don't do this. Have a minimum length, but don't force me to miss it up. My password manager shouldn't have to try multiple times to generate matching passphrase.
The derivative with respect to a is: b(a^(b-1)).
The derivative with respect to b is: log(a)(a^b) or (a log(a))(a^(b-1)).
So it's better to increase b when alog(a) > b. Which is typically the case where a is 26 for lowercased letters and b is like 10 for password length.
This analysis might not be totally correct since the cost of adding one extra allowed character vs increasing password length by one is not the same but w/e.
When they don't allow spaces in passwords either, I worry.
Along the same lines though is OPAQUE PAKE, where the server doesn't need to store a password hash, only a salt, making server compromise far less dangerous, it's quite elegant.
There's no implementations so far I believe.
There are some other advantages that others have already mentioned, but even if that was all it did it would still be useful in inhibiting an attacker from learning the actual passphrase which many users are likely to have reused on other services.
Sending a password in plaintext over HTTPS is more secure than hashing it in javascript first and sending the hash.
If it's practical to find a hash collision, your hash algorithm is broken.
> which is made easier with the ability to study the client-side code doing the hashing, and taking note of the algorithm and methods used.
The security of a system should not depend at all on that information being secret.
e.g. password + client_salt => hash => send to server => (hash+server_salt)^hash2 => compare to db
By doing this you'd protect a user when their password might be accidentally logged (e.g. Twitter recently). Then if you compromise the hash you don't immediately reveal the password itself, just the text needed to authenticate, which can be changed. If you simply change the salt used client side you may not even need to have the user change their password (although obviously better if they did).
That said, I don't think this is required, but there is actually a case for it. Also obviously you should never log the password, but mistakes are made. This helps mitigate the risk of that password being exposed.
I've inherited several ancient code bases where everyone knew silly password rules were a legacy requirement. And ultimately after a lot of digging, every time they were a "legacy limitation" because the original project manager called for it, and could easily be removed by commenting out one check. Which was never allowed to happen, because it was a "constraint that couldn't be changed".
I do accept there are databases with eight character fields for maximums, but beyond that, I'm interested in any genuine experience.
They didn't, they just chose off the shelf PHP forum software written by idiots that does this and a million other stupid things.
From what I can tell so far, what we setup seems to be working fine. If we hit a wall, I'll search out the next most practical option.
I can see the temptation to want to hack around on it because it's a forum for hackers, but it's not as if HN is taking pull requests either.
EDIT: Changed this to just have a minimum length restriction. Thanks for the feedback!
Please, disable cookies for HackerForums.co too.
I mistook this for being about usernames at this hacker forum
(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 the bulletin board/flat forum model of communication, so I'm hoping this site can blossom into a community of high quality folks having high quality conversations.
EDIT: Also, this is my first foray into setting up and using phpBB, so please let me know if I need to adjust anything. I tried to keep most settings at the default because I assumed that made more sense than me tickering, but I'm all ears if things are weird.
Overall though, nodeBB looks really nice, so go for it!
I would love to be corrected in this, (and in fact I'm prototyping a NodeJS+NuxtJS+VueJS forum on the weekends, but don't expect a release this year) but I think you're better off sticking with the PHP variety of forums. I think that's where maturity, stability, and extensions ecosystem shine.
However...
Your FAQ link leads to a 404 page, and the "legalese" on the registration page seems like a bit much to me. And why should I need to be registered to see the "team" page and profiles?
It's just a web forum, don't take things so seriously. You're an admin, you can literally just ban people for acting up, you don't have to expect to back it up in a court of law or anything.
All of those items are in my todo list now!
This is 'hacker' news after all. Can't this website release its forum software so that a bunch of interested volunteers (no me) could improve it? Wouldn't that be really meta and cool?
The main gripe I have with HN forum is lack of reply notification. Secondly, the crowd tends to overdo the hacker-nerd-geek thing by discussing unrelated minutae till the cows come home which inflates the comment count. This sort of discourages posters to post their POV fearing it will be buried amidst the 500+ comments. We have a visibility problem.
We just need a few tweaks.
Further, looking at all the passionate discussion about AI and ML that happens here, I am sure some of the regulars would like to implement a scheme that learns my 'collapse the chaff' pattern and spare me the gory boredom inside a thread.
(I think what I wrote might come across as snarky, but I assure you I am not being so.)
I can't see how it can be fixed.
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_messenger.php on line 506: count(): Parameter must be an array or an object that implements Countable
Probably best to turn off debugging statements.
Just so I'm clear, this happened immediately after registering? Or did you do anything else that triggered this?
I could be wrong, (I'm a Python guy - not PHP), just seems a safe assumption that it's likely not the only spot.
NO.
It's better to improve the code than roll back to an older and less secure version of the language.
This is PHP we're talking about, after all.
Put up or shutup.
I am working on a somewhat related idea : a site like reddit, but which also has a chat room for each subreddit/topic + public moderation logs among other features. I launched with only the chat rooms part of it and I faced the issues mentioned above, so I'm interested in hearing about your approach. Good luck!
Totally agreed that forums (and communities in general) have the cold start problem, and there's no real good solution for it.
I do have some ideas though.
1) I'm interested in whipping up a simple phpBB mod that enables Link posts (like here on HN). That will help with the News posting aspect of the community. Thread here: https://hackerforums.co/the-lounge-f3/idea-extension-for-php...
2) I'm going to write up a fairly detailed thread later today that explains in more detail the Why of setting up the site, and the How I did it (literal technical details for those interested). I'll post that here and on Reddit and a few other places to hopefully get some exposure. Cool kids call that "traffic leaking" where you get valuable content in front of active communities, so might drive some traffic.
3) I'm debating setting up a contest of sorts, where members can earn a special badge/title by actively participating in the forum. So for example, start 10 threads and post 25 replies in threads and earn a special badge on your account for eternity. Silly, sure, but could be a simple fire starter.
But yeah, overall, it's a challenging thing to do, and I've failed at it a few times over the years in trying to start forums. I still really love them though, so I wanted to try it again.
BTW: Post your project here! :) https://hackerforums.co/show-hf-f7/
Especially when you're likely talking about interesting topics / questions people google for. It seems in recent years that going has favored articles over forum topics in their results, but I'm sure there's still plenty of search traffic that goes to forums to bring in new users.
1. Fake it, like on Reddit. Setup a bunch of fake users and create a ton of topics until activity really kicks in.
2. Do exchanges and deals on forum promotion and community management sites. For example, you can ask the people on Forum Promotion for exchanges, where you do five posts on their site in exchange for five posts on yours or what not.
3. Pay some sort of service for content.
One or more of those could work for this site.
That said, if I can give you a bit of advice:
Change that captcha on the registration page. It's really annoying to decipher, and likely doesn't do all that much to stop bots.
Instead, get a few questions and answers set up, and make them forum specific. Like, what startup aggregator is Hacker News associated with? What's FANG mean? What language are the frameworks React, Vue and Angular written in?
In other words, stuff a dedicated community member would know/could easily look up, but which a bot might not want to bother with.
That's much better to stop spam, and less annoying than figuring out what letters and numbers are in a captcha.
Still, hope the forum works out well!
E.g., "Can you believe this trash got on the front page!" everyone proceeds to downvote or "hey my show hn is up!" everyone upvotes.
Worth a shot at least.
Another major upside to forums is the ability to easily directly connect to folks. I've made many friends that way over the years in various forums, and business partners.
As a matter of fact, I'm thinking about a possible solution focused on allowing remote hackers to at least do professional networking. It could become a real project; anybody interested, feel free to contact me (email in my profile).
With this said, I hope I'm wrong, so I'll subscribe and wish best of luck to this new forum :)
Regarding this: "It could become a real project; anybody interested, feel free to contact me (email in my profile)." Start a Show HF thread on the board!
I will - when I'll have something to show :)
I think that we need a forum with the good hierarchical overview of the good, old usenet clients (but with updated UI, of course).
Discord seems to be a chat app, which is quite different than a forum and even HN itself
I've been keep track of HN related things people have built and added this also
also +1 to shaving that banner height by 50%
but good on you for shipping a thing
I'm not sure about this approach though. Forums are too centralized and don't feel interactive enough. I'd much rather see a HN community on Matrix or something similar.
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions_messenger.php on line 506: count(): Parameter must be an array or an object that implements Countable
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
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