Next Gen textboard features

Ideas:
- federated (boards can share threads & replies)
- tags rather than boards
- multiple markups (bbcode, markdown, sexpcode/lispmark)
- OAuth & PGP for "secure" tripcodes (novelty)
- "flair" (tripcodes / secure tripcodes have small bio pages, and can pick a color for their tripcode)
- youtube embed
- Various thread modes (sticky, lock, stickylock, permasage)
- IRC, Discord, microblogging integration

>>1

- federated (boards can share threads & replies)

NNTP

- tags rather than boards

..except in a stackexchange style

- multiple markups (bbcode, markdown, sexpcode/lispmark)

Use a script

- OAuth & PGP for "secure" tripcodes (novelty)

We do not need tripcodes at all. OAuth is cancer and anyone who wants to identify themselves can use normal OpenPGP.

- youtube embed

This would be a perfect example of something that one can easily implement using a client side script.

- Various thread modes (sticky, lock, stickylock, permasage)

We already have these.

- IRC, Discord, microblogging integration

Cancer
Also, how would this even work.

>>2

☰ menu

I don't get it.

pseudo-youtube embeds -- there is a youtube thumbnail and it only adds the embed when you click on it (video embeds make a page slower, especially if there are lots of them)

Client side script

ability to hide threads client-side on a per-thread or per-term basis (like filtering posts/threads that contain the word "lisp" or "anime")

Client side script

CSS3 animations instead of things happening instantly

I.. This has to be a joke, no?
If you hate yourself so much use a client side script.

VirusTotal auto-scans all links posted

VirusTotal is a cancer - they do not publish their db.
What if I wanted to post a link blacklisted by virustotal though?
Same question goes for

Spamhaus and malwaredomainlist to vet links

Anyway, client side script.

bug bounty program

Solution: don't implement bugs

ability to report threads or posts

Censorship is bad

ability to delete your posts

Might as well be censorship

"front page" showing the threads with an algorithm similar to reddit's "hot" posts (lots of posts in a short amount of time = "hot" thread)

Client side script that reads threads.txt

ability to mark posts as SFW or NSFW

You already proposed to add tags, why also add this?

upvoting without accounts, similar to ylilauta -- might be a bad idea due to tech-savvy people manipulating the votes

Why not use a client side script for this?

checkbox for sage; get rid of email field entirely

Good, idea. Have you considered making a client-side script for it?

flat-ish design, maybe with some subtle material design elements

Can be trivially done using a client-side script.

>>3
Have you tried using a client side script for this?