EVE General Discussion

So, because the forums are "https" and the game client already has an "http://" to web links, we now cannot link forum threads in channel MOTD's and such.

You vikings are smoking some extremely strong stuff up there. Maybe you should cut down.

Jeeezzz...

Have trust and confidence in CCP.

They will fix it.




looooooooooooooooooooooooooooooooooooooooooooooooooooooooool

I would hire a new intern for this project. You should have fired him the last time you put these crappy forums up but to let them continue to strip ALL usability from a forum is a new level of fail on CCP's part.

I said it earlier. HTTPS implementation was merely a patchwork because CCP has nobody versed in forum security. Instead of learning something or hiring someone who knows something, they simply went with HTTPS. Hint to CCP: https is designed for specific instances. Unless you are sharing sensitive financial information with this site why the hell are you using https instead of programing proper scrubs, checks, and simple urls.

Browsing the forum with your url structure I've learned quite a bit about your database structure since you expose so much in the url. This thing will likely be taken down with some injection attacks which your https scheme can't stop. You need proper coding. Oh don't say you can't do simple urls, I've looked at the highlights of yaf and simple urls is one of their listing points (not selling point since it is freeware). instead you don't know how to implement or chose not to when you really messed with the coding.

edit: open the pages in a simple DOM viewer. almost all your code is plain text, you only used obfuscate on direct path in the code. OMG why would you put full paths in your publicly view-able code??

CCP incompetence is very real, and very scary.

The smoking or the linking?

Well, maybe the devs should make a sticky about this because I'm pretty sure I'm not the only one to use links to forum thread in a channel's MOTD. Or at least post a list of the codes we can use while someone works (!) on making this more use-friendly. Wishful thinking, I know.

@ISD Libertina: it doesn't work.

Positive that there were no spaces in my attempt.

Heheheh, web designers trying to make smart remarks about web application development makes me giggle, it causes no harm whatsoever, there might be issues (as per Hellicity twitter post even today) but they're not certainly due to how stuff is obfuscated or not.

Btw, obfuscation (js) primary purpose is not to keep you away from understanding the code, but in browser js engine processing speed up, as it's often translated in to smaller code (thus less text) and better (test proven) fashion to increase speed, besides, many js libs already come 'optimized' (commonly mistakenly called obfuscated).

Just to squelch a little misinformation:

https is good. It's not a panacea, and won't fix poor security, but without it

A: when you log in, your password is visible to everyone between your and the site you're working with. Unless, perhaps, you get funky with javascript and a changing hash. (or use digest auth. but that's very rare)
B: your session is vulnerable to hijacking by anyone between you and the site you're working with.

Short form: https = good. Don't belittle people for using it. Only if it's /all/ that's been done.