(POSSIBLY IMPORTANT) We've just made a change to the server that may affect this option in Augmented TCF.Features
- General
- HTTPS to HTTP: Automatically moves you over to http if you're found to be on https.
As an ATCF user, I can confirm that this will cause problems.(POSSIBLY IMPORTANT) We've just made a change to the server that may affect this option in Augmented TCF.
The server will now force forum links to use HTTPS. If you have had this ATCF option turned on, you may want to turn it off now.
This change was made to hopefully fix the intermittent logout problem for everyone, not just ATCF users.
Strangely, it didn't cause problems for me using Firefox. I'm trying to contact Everest now.As an ATCF user, I can confirm that this will cause problems.
The forums will reload constantly everytime it's fully loaded.
So it's an option to turn it off, but it'll be even better if Everest can manage to remove the function entirely, so nobody will have issues with it anymore.
Might be depending on browser, I'm using Google Chrome.Strangely, it didn't cause problems for me using Firefox. I'm trying to contact Everest now.
Using chrome and I also had this issue.Might be depending on browser, I'm using Google Chrome.
Ah, so that's what was going on!(POSSIBLY IMPORTANT) We've just made a change to the server that may affect this option in Augmented TCF.
The server will now force forum links to use HTTPS. If you have had this ATCF option turned on, you may want to turn it off now.
This change was made to hopefully fix the intermittent logout problem for everyone, not just ATCF users.
The great extension programmer that made TCF great again and saved a lot of people from logging out out of nowhereWho is this "everest" dude anyway
Hey, as Firefox develops, it will become easier to maintain your add-on.
Since you made this add-on, I thought the following article would be useful to you.
I'm currently on Nightly 56, so we're one build away.
My biggest concern about v2 is the lack of current support of WebExtensions for Firefox. The estimated (imagine the italics to add enough emphasis to "estimated" to make it slanted at a 90 degree angle) release is Firefox 48. The Release Calendar says that'll happen way out on August 2nd. So about 6 months.
That's good to hear. Sorry for not seeing that post. Typescript is AWESOME, I can see why you're in love with it...Thanks for the heads up, but I'm already very aware of those wonderful changes, as I outlined in a post almost one and a half years ago:
Since then, the aforementioned version of v2 has been scrapped and (as of last week, in fact) I've started rewriting ATCF 2 using even more modern technology (including WebExtensions, which I was already writing for). Here's an overview of the tech I'm using to build ATCF 2, and it's advancements over v1:
And yeah, that's all I can think of right now.
- TypeScript (<<< currently in love with this )
- Prior to TypeScript, v2 was being written using Babel to get those juicy new ECMAScript features, which TypeScript also includes.
- webpack
- v2 features a custom webpack plugin to actually compile a manifest.json file (using data that's implicitly and explicitly defined in the package.json file), which is required for WebExtensions
- Possibly React
- I've yet to decide for certain whether I want to go forward with React, but I most likely will.
- It's open source on GitHub, because I can (and should). [url soon c:]
- The plugin system is more modular, allowing for easier development.
- If you've read this far in, then you're the kind of person I'd like to advise: working with XenForo's stuff from an extension standpoint is no fun q-q, don't try it.
- Settings are going to be cached on the background 'thread', which might (or might not, I'm probably not going to test it) prove to be an optimization.
- Currently, v1 accesses storage for settings every time you visit a page, which (in my head) seems costy, though I'm sure browsers are optimized to handle it.
- A different set of augmentations available
The idea of updating ATCF really does sound joyous to me, and I'd love to see it through, but the biggest block in getting me to update is usually motivation. I'm pretty good at self-motivation, but sometimes development gets stale without feedback (my fault, by far ). I urge anyone who wants a better ATCF to poke at me whenever I stop working, publicly or privately [cough lovely forum staff cough], and that should get the gears turning . Even a message as small as the one I'm replying to above is enough to motivate me.
Expect some extra info about ATCF 2 (i.e. screenshots, source code, etc.) soon. Maybe. Hopefully.
Have you considered making the project open-source to allow other members of the community to help add new features?Thanks for the heads up, but I'm already very aware of those wonderful changes, as I outlined in a post almost one and a half years ago:
Since then, the aforementioned version of v2 has been scrapped and (as of last week, in fact) I've started rewriting ATCF 2 using even more modern technology (including WebExtensions, which I was already writing for). Here's an overview of the tech I'm using to build ATCF 2, and it's advancements over v1:
And yeah, that's all I can think of right now.
- TypeScript (<<< currently in love with this )
- Prior to TypeScript, v2 was being written using Babel to get those juicy new ECMAScript features, which TypeScript also includes.
- webpack
- v2 features a custom webpack plugin to actually compile a manifest.json file (using data that's implicitly and explicitly defined in the package.json file), which is required for WebExtensions
- Possibly React
- I've yet to decide for certain whether I want to go forward with React, but I most likely will.
- It's open source on GitHub, because I can (and should). [url soon c:]
- The plugin system is more modular, allowing for easier development.
- If you've read this far in, then you're the kind of person I'd like to advise: working with XenForo's stuff from an extension standpoint is no fun q-q, don't try it.
- Settings are going to be cached on the background 'thread', which might (or might not, I'm probably not going to test it) prove to be an optimization.
- Currently, v1 accesses storage for settings every time you visit a page, which (in my head) seems costy, though I'm sure browsers are optimized to handle it.
- A different set of augmentations available
The idea of updating ATCF really does sound joyous to me, and I'd love to see it through, but the biggest block in getting me to update is usually motivation. I'm pretty good at self-motivation, but sometimes development gets stale without feedback (my fault, by far ). I urge anyone who wants a better ATCF to poke at me whenever I stop working, publicly or privately [cough lovely forum staff cough], and that should get the gears turning . Even a message as small as the one I'm replying to above is enough to motivate me.
Expect some extra info about ATCF 2 (i.e. screenshots, source code, etc.) soon. Maybe. Hopefully.
Have you considered making the project open-source to allow other members of the community to help add new features?
It's open source on GitHub, because I can (and should). [url soon c:]
Missed that (or perhaps forgot). Thanks for pointing it out!He appears to be working on that.
Seriously - I've been worried about the upcoming FF changes (Web Extensions) for a while now, primarily if that were to disable this plugin for a while or even permanently. I've used it for so long that it's hard to imagine TCF life without it. Glad to see that you're still working on this, Everest.
Have you considered making the project open-source to allow other members of the community to help add new features?
It's open source on GitHub, because I can (and should). [url soon c:]
Good to hear this, I'll keep an eye outOi m8, did you read the post?
It's technically already up, but it's very unfinished (hell, I have basically half of the project on my local machine for stuff I'm working on atm). I can guarantee that by release, and likely sooner, I'll be more willing to share the url, but until then I'm more focused on building the base up before I start asking for help with features.
But I'm definitely open to pull requests, both now (just pm me), and in the future (GitHub)