Dll

Best of luck in the future Jordan.

It's simpler than that I think? Bots view as guests and there's an option in the ACP to either show or hide signatures to guests. 
Member settings > profiles > profile settings > show signatures to guests

It's simpler than that I think? Bots view as guests and there's an option in the ACP to either show or hide signatures to guests. 
Member settings > profiles > profile settings > show signatures to guests

I'd give Google analytics a chance to catch up, the data tends to lag a bit at times lately.

Honestly can't get my head around this Pagespeed score obsession, test many of the top sites on the internet and you will find many on par or below a standard IPS forum in this point scoring contest.
Been reading your posts on here for a number of years and I think it's almost a personal challenge for you now rather than something that would benefit your site. 
Use your eyes, they will tell you if your site is loading slowly or not, I'm over 10 years deep into my forum with Adsense on and I haven't had one member complain that my forum is slow on mobile, not one based in the UK on a UK server with members using from the US, Russia and Asia. Not one complaint.
I haven't been punished by Google in anyway, still number 1 for search terms related to my site all whilst using custom.css which keeps all my changes in tact on every single upgrade.
My site isn't unique, take MacRumors for example, Pagespeed 31 for mobile yet still the number one Apple related forum. Go figure.
I wish you luck in your hunt for that magical 100, however the changes IPS have made will benefit all customers going forward. 

Yeah, that would be correct, yes. We do not provide a personalised email service at present

Maybe y'all develop differently to me, but personally I wouldn't browse through a random CSS file to find classnames - there's no context (beyond the classname anyway; you don't get any of the cascade, inherited properties etc. that might affect it).
It makes much more sense to use the web inspector to see what is actually being applied to the element you want to change.
It may be a difficult transition at first but i would consider this an opportunity to improve your own development process.

It was always wrong though. You would change a core file and so every future update of that file would cause an unnecessary conflict. Adding an override in the custom.css was always the right solution. So, the change just prevents you from doing it the wrong way. 

Personally, when I'm theming or updating CSS for something on my site, I'm in the browser inspector for most of time. Looking at how the relevant rules interact with each other and determining which change I want to make to achieve my goal.

There have been plenty of betas and a blog about the changes earlier in August. 
 

I don't know what else we can do. We've given our marketplace authors about a year to prepare. We started releasing betas in May, and we posted the above in August; yet a lot of our marketplace authors seem unaware.

However, we do not want to cause our clients a headache, so we're working on a way forward that doesn't leave you without apps and plugins you need.

All these complaints but a simple server snapshot would have allowed an instant rollback. You’re warned to back up first. 

There have been plenty of betas and a blog about the changes earlier in August. 
 

There have been plenty of betas and a blog about the changes earlier in August. 
 

Try the Google cache or wayback machine.

A simple google image search for the old user name on my website and I found it !! Thanks so much for the great idea. 

Try the Google cache or wayback machine.

Try the Google cache or wayback machine.

Good luck in your new endeavours Rikki.

Good luck in your new endeavours Rikki.

Media queries are the standard way to write responsive websites. I'm not sure Invision need to reinvent that.

There is nothing simple or better about it. It’s just unreliable. What if use a smaller browser window on desktop? The site would break since it can’t be displayed properly. Because with your method, the code for smaller screens would have been removed. What if PHP can’t detect the device clearly for some reason? Again, the site could break because the wrong version could be delivered. 
All in all, the benefits of stripping a few lines of unused code don’t outweigh the potential negative consequences. After all, it IS about the screen size, not the “type” of device. The break points are called “desktop”, “tablet” and “mobile” but that is just a convention. The device doesn’t really matter, so recognizing it isn’t the point. It must work for whatever screen size is available and that is something determined (and possibly even changed) on the client side. 

I blame lack of coffee. Sarcasm accepted LOL
Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

sorry, I was understanding this as "You can edit quotes and misrepresent them", but I get what you mean now. Apologies for the misunderstanding. Let me take a look at this