I'm wondering if I should do that.


Pros:

* authentication: if shit is done right, you know you're talking to the real K64 server and not a rogue server
* security: logging in doesn't transmit your plaintext password (which can be an issue on public networks with trolls sniffing shit)
* you get away from whatever blocks port 80 (or web filters)


Cons:

* costs money (although much less than a few years ago)
* needs one certificate per domain or something like that (ie. multiple certificates if we also want to secure 4dsdev and some other things)
* needs all assets on the page (images, etc) to come from https sources to be declared secure by the browser
* some more complication in the board's code and related things if HTTPS and HTTP coexist (converting board URLs in posts, should KuriBot's links be HTTPS or HTTP?, ...)

____________________
NSMBHD - Kafuka - Jul
melonDS the most fruity DS emulator there is

zafkflzdasd

most services like Dropbox or imgur already have HTTPS


the issue would mostly be people embedding shit from their own HTTP-only server


(or those making HTTP links, but arguably, for the most common services, you can recognize the links and remove their http prefix)

____________________
NSMBHD - Kafuka - Jul
melonDS the most fruity DS emulator there is

zafkflzdasd

not 'cert not verified', but 'connection not secure' because some requests are made over HTTP, even though it doesn't matter in the case of images and such


then you have those douchebags yelling OMG VIRUS SITE when they see that, but hey, that kind of idiots isn't welcome here anyway

____________________
NSMBHD - Kafuka - Jul
melonDS the most fruity DS emulator there is

zafkflzdasd