ATTN: FFR Website Devs

[gold stinger]

Your Google Plus front page icon is broken.

You can view what the icon is supposed to look like by clicking anywhere on this blue link. (It's literally a copy-paste from the src)

This is what it looks like now:

anyone else getting the problem? is it to certain browsers?

edit:
also where is facebook like button, just going to leave a like & g+1
move the facebook like button up next to the google plus button


asdf

[Fission]

there is <blink>tons</blink> of stuff on ffr that is "suboptimal," including butchered web development best practices throughout that can be seen at a cursory glance of the frontend code

[Velocity]

Originally Posted by Fission

there is <blink>tons</blink> of stuff on ffr that is "suboptimal," including butchered web development best practices throughout that can be seen at a cursory glance of the frontend code

The joys of really old code and multiple developers~

[FF_rules]

Originally Posted by Velocity

The joys of really old code and multiple developers~

Slightly off topic; Gambling hall tends to eat infinite memory on my firefox after I use it for a few hours (from constant refreshing). Is this just more? I'm not tech savvy enough to understand the issue at all (If I were to guess; cache issue?)

[Fission]

it takes a concerted effort to adhere to best practices and can't be magic'd in overnight as you probably already know. multiple developers isn't really the problem on its own so much as not adhering to good coding practices is. somebody has to be watching for it or else it creeps up and you end up with the current state of FFR's codebase.

[gold stinger]

figured out how to solve the problem at least on my end: had to clear cookies and cache related to facebook & google.

[mrpreggers]

Originally Posted by FF_rules

Slightly off topic; Gambling hall tends to eat infinite memory on my firefox after I use it for a few hours (from constant refreshing). Is this just more? I'm not tech savvy enough to understand the issue at all (If I were to guess; cache issue?)

a few hours what de fuck you addict

[s1rnight]

Originally Posted by Fission

it takes a concerted effort to adhere to best practices and can't be magic'd in overnight as you probably already know. multiple developers isn't really the problem on its own so much as not adhering to good coding practices is. somebody has to be watching for it or else it creeps up and you end up with the current state of FFR's codebase.

pls bring this guy in to fix the code. i trust him a lot

[Velocity]

Originally Posted by Fission

it takes a concerted effort to adhere to best practices and can't be magic'd in overnight as you probably already know. multiple developers isn't really the problem on its own so much as not adhering to good coding practices is. somebody has to be watching for it or else it creeps up and you end up with the current state of FFR's codebase.

Most of the developers (including myself) that worked on FFR website learned to program websites using FFR, so as they learned, they got better. This also means that early projects by them are best described as a clusterfuck,but never got revisted due to them "working as intended".

[FoJaR]

Originally Posted by Fission

it takes a concerted effort to adhere to best practices and can't be magic'd in overnight as you probably already know. multiple developers isn't really the problem on its own so much as not adhering to good coding practices is. somebody has to be watching for it or else it creeps up and you end up with the current state of FFR's codebase.

so so true. most of the time in the world of coding there are multiple developers working on a project. this is not an excuse.