>Pinktext / Orangetext by using "<" maybe even a third kind
Currently < is bluetext and ^ is fagtext because it points towards OP, as seen in second pic in OP.
>A hide thread button on the catalog (8chan style), not as a tab (4chan style)
>Shift Click / Alt Click to hide/pin threads like on 4chan
Middle clicking the post options button hides a post/thread, and it works in catalog. Not sure if I want to add a second button for left clicking, but I'll add it if more people want it. I'll make a note about keyboard shortcuts.
>A hide locked threads function that actually works
I'm not sure why that's special, but it's trivial enough so why not. Threads will have CSS classes to indicate they're locked/stickied/etc, so you can also use custom CSS to modify them.
>The ability to hide names / trips in the menu completely so you never see them, even as a drop down
>a separate "extreme" option that hides any replies to them also.
When you click the arrow next to a post? This gets a little difficult because it's hard to tell when people want the filter to be permanent and when temporary. And if you want to support all options, then there will be a million buttons in the dropdown. I can add a shortcut to it for creating permanent name filters though.
However the post filtering system (which you'll have to edit in a menu) I have is way better than anything I've seen anywhere else. You can target names/trips/filenames, replies, specify OP or catalog, whitelist/blacklist boards, toggle case sensitivity, there's options to invert it and add multiple keywords to the same filter, etc. I'm also going to add stacked filters, so you can only apply filters inside threads that are filtered by a "parent" filter. (for example detect OP that has "draw thread" in the title, and then highlight all posts that contain "requesting" in the post)
>A "watchlist overboard" which just shows you threads you have watched.
There will be a watchlist on the edge of the screen which also shows new posts (pic related). A catalog for them seems redundant, but I'll consider adding it.
>An "auto-watch feature" where any thread you have posted in becomes watched.
Considered it in the past but didn't need it myself, I'll include it this time.
>Working nerve centers with more than 8 boards with configurable number of threads of the nerve center. So if you want to cap it at 50 threads you can, or if you want to see every existing thread on all boards on the nerve center, you can do that too.
There's a feature I've called "multiload", it lets you load multiple boards into the same catalog view, and create groups into your favorited boards list. It has no limit on how many boards you can add (though it'll load longer the more you add). "Every thread" is a problem though because your browser can't handle it. Loading every thread into the catalog will just freeze and choke the shit out of it. You'll be able to configure how many threads it shows though. There's also a feature that highlights threads that have been bumped/created since you last viewed the catalog, and those threads will show up even if they go past the thread limit.
>Ability for ranked users to add or remove tags from threads
BOs will be able to create jobs with very customizable privileges, you could create a job that lets someone edit tags (in that board) but nothing else. An admin could also create global jobs like this. There won't be any upvote-like reputation shit, only jobs that must be assigned by a mod/admin.
>An ability to share "instances" with other users which would be a version of a board or nerve center, with your particular tag / filter set-up.
I'm not entirely sure what you mean by this, but it sounds extremely complicated and not something that more than a handful of people would use. I can kind of imagine how to do it, but it doesn't seem worth the effort.
>A custom CSS creator. Board creators could simply select colors / pics for each element in a menu and it would generate the CSS for them.
I'd rather create tutorials on how to use your browser's tools to get CSS rules from the page and modify them. It's an interesting idea though and surprisingly simple to do, I'll probably do it some day when there's nothing more interesting to do.
>Dynamic CSS. So if you are browsing on an overboard or nerve center, each thread (on index or catalog view) will have the CSS of the corresponding board, even without opening the thread.
Best way I can think of is generate a separate CSS file with altered rules in the server when a BO updates the board CSS. It would work but I have no idea how to accomplish that kind of CSS splicing, so probably not going to happen.
>Ability to have different CSS on the same board, like on /server/.
This is a little easier than above, because the CSS rules only need to be valid for the thread itself and the user knows it when creating it. I actually like this idea and I'll add it as a regular option if I can (so optionally anyone can set custom CSS for their thread). Should be straightforward enough unless I'm overlooking something.