Barnacles is a link-aggregation site for small, self-funded businesses that define success on their own terms. The goal is to continue and grow the generous, collaborative community that gathers at events like MicroConf and BaconBiz. The code and name are based on Lobsters, a tech news site.
Some other link aggregation sites are operated by corporate entities which may have significant financial incentive to censor or artificially promote the links and discussion that relate to those entities, their investments, or their competitors. Some of these sites have had moderators of popular sub-forums banned after it became known that they were being paid by 3rd party companies seeking special treatment of their submitted stories.
All moderator actions on this site are visible to everyone and the identities of those moderators are made public. While the individual actions of a moderator may cause debate, there should be no question about which moderator it was or whether they had an ulterior motive for those actions.
All user voting and story ranking on this site uses a universal algorithm and does not artificially penalize or prioritize users or domains. Per-tag hotness modifiers do affect all stories with those tags, but these modifiers are made public and usually used to shorten the life of meta-discussions. If certain domains have to be banned from being submitted due to spam, the list will be made publicly available.
If users are disruptive enough to warrant banning, they will be banned absolutely, given notice of their banning, and their disabled user profile will indicate which moderator banned them and why. There will be no hidden "shadow banning" or "hellbanning" of users.
The source code to this site is available under a 3-clause BSD license for viewing, auditing, forking, or contributing to. It is based on Lobsters codebase generously shared by joshua stein.
All stories are tagged by the submitter from a list of predefined tags. Users can choose to filter out all submissions with particular tags, but rather than use rigidly segmented sub-forums that users must each subscribe to, all users see all tagged stories by default.
This helps keep the site on-topic, keeps conversation from fragmenting, and prompts more collaboration. Users who strongly dislike a topic enough can filter it out.
Creating, changing, and retiring tags is done by the community by voting on and discussing meta-tagged requests about them. If you are suggesting a new tag, build your case by explaining why it's vital and including stories that should have been tagged.
Invitations are used as a mechanism for spam-control and to encourage users to be nice. New users must be invited by a current user, though there is no vetting process. The most efficient way to receive an invitation is to talk to someone you recognize from the site. Invitations are unlimited unless scaling problems temporarily prevent new accounts. In case of serious abuse that require banning, the user that invited them may also be banned, going up the chain of invitations as needed.
The full user tree is made public and each user's profile shows who invited them. This provides some degree of accountability and can act as a tool to help identify voting rings.
Downvotes are not for disagreeing or punishing. Users downvoting comments must choose a reason which is visible to the submitter and moderators.
For submitted stories, downvoting is done through flagging (also requiring a valid reason) and these flag summaries are shown to all users.
Mailing List Mode
Users can enable a mailing list mode of the site which e-mails all new stories (including their plain-text content as fetched and extracted by Diffbot) and user comments as threaded discussions. This makes it easy and efficient to read new stories as well as keep track of new comments on old threads or stories, just like technical mailing lists or Usenet of yore.
Each user has a private mailing list address at this domain which allows them to reply to stories or comments directly in their e-mail client. These e-mails are then converted and submitted to the website as comments, just as if the comment was posted through a web browser.
Private Messaging: Users here can send private messages to each other without having to publicly disclose an e-mail address, and can receive e-mail and Pushover notifications of new instant messages.
Integrated responsive design: enhances functionality on smaller screens such as phones and tablets without having to use a separate URL, 3rd party sites, or proprietary mobile applications.
Integrated search engine covering all submitted stories and comments, including full-text caches of all submitted story contents.
Story merging to combat the problem of multiple stories at different URLs being submitted in a short timeframe about the same news subject. Rather than have multiple stories on the front page with fragmented discussions, all similar stories can be merged into one. An example of a story having been merged into a previous one, combining all comments on one page.
Fuzzy-matching of submitted story URLs to avoid duplicate submissions of similar URLs that differ only in http vs. https, trailing slashes, useless analytics parameters, etc. When using the story submission bookmarklet, story URLs are automatically converted to use the page's canonical URL (if available) to present the best URL to represent the story.
Per-tag and site-wide RSS feeds are available to the public and logged-in users have private RSS feeds that filter out each user's filtered tags.
Hats: a more formal process of allowing users to post comments while "wearing X hat" to give their words more authority (such as an employee speaking for the company, or an open source developer speaking for the project).