Jump to content

InterLinked

Member
  • Posts

    482
  • Joined

  • Last visited

  • Days Won

    4
  • Donations

    $0.00 
  • Country

    United States

InterLinked last won the day on January 20

InterLinked had the most liked content!

8 Followers

About InterLinked

Profile Information

  • OS
    Windows 7 x64

Recent Profile Visitors

2,641 profile views

InterLinked's Achievements

170

Reputation

  1. ... and to make it worse, it doesn't seem the profile can be moved. I *copied* (I suspected moving might be a bad idea) the old profile folder to the new location. Initially I got all the standard welcome new user stuff when opening MailNews. Now I get: Ugh.... I'm an id*** now for upgrading these programs "just cause"... I really just wanted the updated New Moon for the nullish coalescsing/optional chaining support, not this whole can of worms. If there's no way to fix this, I literally have to spend 4 hours setting up my email and another 8-12 hours syncing it. Biggest headache ever. - Okay, looks like moving the *contents* of the profile folder as opposed to the profile folder, and overwriting all the default files, does work. The folder statistics had to rebuild, but at least no lasting damage appears to have been done - my email is back in business. Now I just need to figure out the New Moon stuff. I didn't have many customization to it, I can rebuild it if necessary and don't mind much, but it would be nice to be able to migrate the profile folder if that can be done.
  2. Okay, don't mean to go off on a rant here, but seriously, WHO CHANGES THE PROFILE LOCATION in MailNews? I've upgraded MailNews before, usually a couple times before, along with New Moon, and it's all gone well before using my auto install scripts, since it upgrades the application. However, it now appears to be looking in %userprofile%\AppData\Roaming\OpenSource\MailNews instead of %userprofile%\AppData\Roaming\Binary Outcast\Interlink\Profiles This is a *HUGE* break in compatibility and a divergence from the previously offered backwards compatibility. Sorry if I missed some announcement about this or something, but this is a huge change that is bound to mess up the entire userbase. I have 11 email accounts and 8 GB of email, it literally takes 3 hours to get the email accounts setup properly in MailNews. (Modern TB, to give it credit where credit is due, is way way faster, maybe less than half an hour. Interlink still uses the obsolete conception of separate IMAP and SMTP servers for who the heck knows why, which makes configuration of Interlink/MailNews a total PITA) And it seems the same thing has happened with New Moon as well - EVERYTHING is gone, and I can't even locate where the new profile folder is yet to move stuff from the old one to the new. Okay, sorry, </rant>, but this definitely made for a grumpy morning and in the future - please, please - such ABI changes should really be avoided unless absolutely necessary, this seems like it wasn't to me, changing Binary Outcast\Interlink to OpenSource\MailNews. At least now that it's happened, hopefully it won't change again. On a different note, much thanks as always for your continued development on these awesome forks, hope they will continue to be around for a long time! But also serious question - WHERE did the New Moon profile folder move to??? I can't find it.
  3. That's true, I would never use it myself. New Moon on Windows 2000 can do TLS 1.3, I'd have no reason to use Chromium on an older system. Supported by the Google store is irrelevant, since the entire Google store is irrelevant to old Chrome as it is. chromefill is manifest v2 which is no longer accepting new ones anyways. It's a fact of Google that you are on your own at this point and if you want to make an extension targeting old browsers, it will NEVER be in the store and you'll have to upload it manually from source using developer mode. Does make me think: we should probably save all the important Manifest v2 Chrome extensions locally before they're removed from the Chrome Web store. Or at least, be able to get them locally from source, e.g. uBlock Origin And for me, only NC and OC are red Right, and maybe 49 is a bit too low but I think the 60s are quite doable.
  4. Ideally, I would like for the extension to support those versions that might not work now, such as between 48 and 68. I use 70 since that's the last usable version, but obviously folks on Vista are older will be on 49, and other folks may be on other versions inbetween. The reality is though that I don't have the ability to test all these different versions for breakage, so it's up to the community to report any issues on the issue tracker, otherwise I simply don't know about them. I have tried to keep up with reported issues that way to add polyfills where needed. So officially it should support all of these versions and if it doesn't, that's a bug that would be great if folks could report.
  5. What errors show up in the developer console when you do this? I only test on version 70, so it's entirely possible that there are things supported by my browser that aren't by yours (introduced between 54 and 69).
  6. That's probably a lot better than Babel, yes! You can filter by using data-plugins it seems, but I'm not noticing any performance difference. It still takes about 15 seconds to run on GitHub. The code seems simple enough, but I'm not a great JS dev, nor I am super familiar with modifying JS via Chrome extensions, so it'll probably be a fair amount of hacking to try to figure out how to kludge that in. I dunno, target group is ANYONE to me using a non-screwed UI Chromium version. I use Chromium 70 on Windows 7 and Windows 10. OS and hardware are completely irrelevant. This extension is necessary to get Chromium to work properly on the web these days (and the NC/OC support is unfortunately an almost-must-have at this point). Yup, truly horrible. Shows how much they really care about "open source" and "projects"... when they don't even practice what they preach.
  7. I've finally been able to incorporate automatic transpiling into my extension for Chromium browsers, so a lot of sites theoretically might be unbroken by this. GitHub for example now works fully again on my system. However, there are some caveats, crossposting: Good news and bad news. Bad news: GitHub still has done diddly squat about their use of the evil operators. Thanks to those who have given this a thumbs up, I think personal comments explaining how this has impacted YOU (or how you feel about it) would also be good: https://github.com/community/community/discussions/20973 Good news: I have managed to incorporate automatic transpiling capabilities into the Chromefill extension. This means that GitHub now works fully again in old versions of Chromium. See https://github.com/InterLinked1/chromefill More bad news: Unfortunately, this is not an elegant solution and probably never will be. Transpiling is SLOW. Reeaaaaaaalllllllllllllllyyyyyyyyyyy sssssssssslllllllllllllooooooooooooowwwwwwwwwwwwwww. It takes about 15 seconds to fully transpile GitHub with all the garbage that they use on their site, and this is blocking. Transpiling is also very CPU and memory intensive (think compiling, essentially). It's also page blocking, so you can't interact with it and transpiling is done. In the case of GitHub, since it's mostly a single page app, that actually means you only need to do it once per tab and afterwards everything just works for your browsing session, but still, not pretty. Sites that don't use JavaScript or use minimal JavaScript don't really see any impact. It's only very bloated sites with hundreds of thousands of lines of JavaScript like GitHub that see a significant performance issue. I think it could be sped up if we could incorporate a transpiler that only focused on these two syntax issues rather than everything, but I'm not sure if such a thing exists. I repeat, this is not really a solution, it's more of a hacky last resort that can force things to work when sites like GitHub behave idiotically and moronically and refuse to do the right thing. That said, if this functionality is useful, by all means go for it. Because of the impact this can have on a site, this functionality is not enabled by default in the extension, it has to be whitelisted per domain. Currently, only github.com is on the list, because that's the only site I use that has this issue. If there are others, feel free to let me know or submit a PR to add it to the list. The goal is to not enable that functionality unless it's actually necessary for a site to work properly. Anyways, happy browsing, if you do use this, let me know how it works out for you.
  8. All right, everyone. Good news and bad news. Bad news: GitHub still has done diddly squat about their use of the evil operators. Thanks to those who have given this a thumbs up, I think personal comments explaining how this has impacted YOU (or how you feel about it) would also be good: https://github.com/community/community/discussions/20973 Good news: I have managed to incorporate automatic transpiling capabilities into the Chromefill extension. This means that GitHub now works fully again in old versions of Chromium. See https://github.com/InterLinked1/chromefill More bad news: Unfortunately, this is not an elegant solution and probably never will be. Transpiling is SLOW. Reeaaaaaaalllllllllllllllyyyyyyyyyyy sssssssssslllllllllllllooooooooooooowwwwwwwwwwwwwww. It takes about 15 seconds to fully transpile GitHub with all the garbage that they use on their site, and this is blocking. Transpiling is also very CPU and memory intensive (think compiling, essentially). It's also page blocking, so you can't interact with it and transpiling is done. In the case of GitHub, since it's mostly a single page app, that actually means you only need to do it once per tab and afterwards everything just works for your browsing session, but still, not pretty. Sites that don't use JavaScript or use minimal JavaScript don't really see any impact. It's only very bloated sites with hundreds of thousands of lines of JavaScript like GitHub that see a significant performance issue. I think it could be sped up if we could incorporate a transpiler that only focused on these two syntax issues rather than everything, but I'm not sure if such a thing exists. I repeat, this is not really a solution, it's more of a hacky last resort that can force things to work when sites like GitHub behave idiotically and moronically and refuse to do the right thing. That said, if this functionality is useful, by all means go for it. Because of the impact this can have on a site, this functionality is not enabled by default in the extension, it has to be whitelisted per domain. Currently, only github.com is on the list, because that's the only site I use that has this issue. If there are others, feel free to let me know or submit a PR to add it to the list. The goal is to not enable that functionality unless it's actually necessary for a site to work properly. Anyways, happy browsing, if you do use this, let me know how it works out for you.
  9. All those who are upset about GitHub and various other sites mass-breaking on the web due to the evil nullish coalescing and optional chaining operators: Please take a minute to provide a +1 and thumbs up to this community post, to indicate to GitHub that this is a serious matter for them to consider: https://github.com/github-community/community/discussions/20973
  10. All right, Support ended up telling me to post over on the community forum as well. If you're upset about GitHub breaking on Windows XP or older browsers in general, you can do your part very easily now - take 2 seconds to head over to the page and provide a +1 and thumbs up. https://github.com/github-community/community/discussions/20973 We need all the support we can get to move GitHub towards the right solution here!
  11. Yup... But don't let MS tell you what OS to use. Support is a benefit, but not a requirement.
  12. Wow, first thing Microsoft's done right in years! I look forward to the press release.
  13. Where did you find out about a year 4-6 for W7 ESU? I don't see anything about that anywhere. AFAIK, there are only 3 years, ending Jan 2023
  14. Well, **tell them that** in that case. A boycott that they don't hear about has no effect!
  15. The reason GitHub doesn't work anymore as of the past few weeks is because of nullish coalescing and optional chaining. Unlike everything else, these can't be polyfilled which is why they are a disaster for the WWW. See the bottom of the README for more details: https://github.com/InterLinked1/chromefill (also https://blog.interlinked.us/69/nullish-coalescing-and-optional-chaining) The maddening thing is that GitHub tried this before briefly, realized there was massive breakage, and then went ahead and reverted it. They apologized and said they would not do it again. They actually did the right thing! That was several months ago, earlier this year. Then, without warning, they went ahead and deployed it again, which means **they lied to us** and actively decided to screw us with operators that serve no legitimate purpose in the first place. Their justification is that it allows for a size reduction which increases performances (you know, since you save a character each time you use it). I call BS. The website isn't performant at all if **it doesn't freaking work**! Basically, GitHub seems to have decided that it the small gain in bandwidth reduction (for files that are generally cached anyways) is more important than breaking compatibility with literally most of the web browsers in existence, those that aren't by "the big 3" from the past year or two. I highly urge everyone to take a minute and file a GitHub support ticket. They do read tickets and do engage with people, and they need to be aware that this is not acceptable. Even if you don't actively use GitHub, it still helps as if we lose GitHub, then that is a big loss for open source, diverse browsers in general. You can submit a ticket here: https://support.github.com/contact You don't have to write essays to them like I have - just take 2 minutes letting them know how this has impacted you and how you feel about and how GitHub has let you down by doing this.


×
×
  • Create New...