0 users browsing Discussion. | 6 guests | 4 bots  
    Main » Discussion » Mozilla, *sigh*
    Pages: First Previous 25 26 27 28 29 30 31 Next Last
    Posted on 22-03-01, 23:11 (revision 1)
    Dinosaur

    Post: #1058 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    FUUUUUUCK YOU VERY MUCH, DANBOORU!
    https://danbooru.donmai.us/forum_posts/206763

    Fucking awesome, the only site in the entire Internet that I actually care these days just shat a smelly JavaShit on our non-Chromeist™ browsers: not only me, but also folks on "can't believe you're still using a 2015 iShiny" iOS users! All in a few hours. Everything is broken - from autocompletion on searches to being able to edit forum posts to actually post lewd drawings images to reading soft translations (which is single-handily the absolute best feature of Danbooru). There is limited interactivity that you would get by disabling JavaScript, but most of those nice perks are gone unless you use the one and only browser certified for ero drawings cute fairy mangas high quality Japanesey art: Chrome. Or its follow-the-leader slave, latest Firefuxed.

    This "bad method definition" bullshit is not unique to Danbooru - apparently it's yet another fine Chromeism™ that should not work according to the standard, but since Google imposes the standards these days a-la Put-it-in/Xinnie, well, we're fucked. I found about this from the competition which shares the same pains: https://forum.palemoon.org/viewtopic.php?f=70&t=27913

    Yes, even FOSS-evangelism sites are guilty of sucking the ChromedTeat™ :/

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-02, 06:15

    Post: #388 of 453
    Since: 10-29-18

    Last post: 15 days
    Last view: 1 hour
    Posted by evazion
    Should be working again, although unhiding hidden comments will still be broken on these browsers.


    ---

    Anyway, in case danbooru doesn't work one day, there's also

    - anime-pictures
    - e-shuushuu
    - gelbooru
    - konachan
    - safebooru, same as danbooru but not (as) lewd
    - sankakucomplex
    - yande.re
    - zerochan

    Plus countless subreddits.

    My current setup: Super Famicom ("2/1/3" SNS-CPU-1CHIP-02) → SCART → OSSC → StarTech USB3HDCAP → AmaRecTV 3.10
    Posted on 22-03-02, 06:45 (revision 1)
    Dinosaur

    Post: #1059 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    Relevant commit notes

    js: fix Javascript failures in Seamonkey/Palemoon.

    Fix site Javascript failing to load in Seamonkey, Palemoon, and other
    older browsers.

    The @alpinejs/morph library uses public instance fields, which is ES2022
    syntax not supported in older browsers. This is the code:

    var DomManager = class {
    el = void 0; // `el` is a public instance field
    }
    // => SyntaxError: bad method definition

    The fix here is to separate the Alpine code into a separate bundle so
    that a failure to load it doesn't cause the rest of the site's
    Javascript to fail to load.

    A better fix would be to either transpile the @alpinejs/morph library to
    ES5 (which seems difficult to do in webpacker), or to fix the library
    upstream to not use this syntax.

    * https://inspiredwebdev.com/everything-new-in-es2022/
    * https://blog.saeloun.com/2021/10/21/ecmacscript-public-instance-fields-and-private-instance-fields.html
    * https://caniuse.com/?search=public%20class%20fields
    * https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Public_class_fields#public_instance_fields


    > ES2022

    Yeeeeeeeah, nope. Not happening anytime soon on our "non-mainstream" (BUT NOT OLDER EITHER!) browsers.

    At least sanity got restored, instead of the usual CLOSED WORKSFORME WONTFIX USECHROME crapola, and I'll be thankful for that, just like that time with SteamDB.

    I still insist that "modern" JS should be considered a very severe war crime, but we all know that the UN and friends are beyond useless these days :/

    In any case, we'll be getting more of this shit all around the web, there is no going back, and I prefer to go permanently offline and drop off as an active society member rather than switching back to braindamaged Firefox. Expect more ranting and angry bug reports in the future, as Google destroys whatever sanity is still left on webdev!


    ---

    In more positive news from the NOT OLD browser league, SeaMonkey 2.53.11 is now shipping, yay~!
    (The release builds are now live, but the site is not yet updated - gotta wait for ewong to do his magic there)

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-02, 09:10
    Custom title here

    Post: #1063 of 1155
    Since: 10-30-18

    Last post: 41 days
    Last view: 1 day
    Posted by tomman


    > ES2022

    Yeeeeeeeah, nope. Not happening anytime soon on our "non-mainstream" (BUT NOT OLDER EITHER!) browsers.

    Older browsers is no excuse anyways. Degrading gracefully is what's supposed to happen, and you adopt new things because they let you do new things instead of because they are new things.

    --- In UTF-16, where available. ---
    Posted on 22-03-04, 19:52
    Dinosaur

    Post: #1062 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    And of course, fucking Google keeps pissing me off every time I have to use the Googlenet® Internet (and the week isn't over yet!): today I received a ridiculous message from them on GMail threatening me to cut off access to my email if I don't use a sanctioned mail user agent:
    https://support.google.com/accounts/answer/6010255
    http://forums.mozillazine.org/viewtopic.php?f=39&t=3087883

    After running this nastygram over my bullshit decoder ring, it seems that starting May 30th (so less than 2 months from today), you can't fetch your email over POP3/IMAP with only your Google username/password, as this is considered to be "DANGER MINES UNSAFE PUTIN ALREADY HAS YOUR PASSWORDZ!". Instead, these are your options:

    - OAuth2: basically every MUA must shoehorn a web browser (or invoke your system default, whenever possible/practical) so you can perform a web logon on your mail provider website.
    - App-specific passwords.

    I still use my ol' XP/Debian 8 laptop these days exclusively for email, both for GMail (which is about to render my setup useless because I AM A DINOSAUR WHY AM I NOT EXTINCT YET!?) and Hotmail (which could pull the same shit Soon™ as MS is now Google/Apple's puppet for webshit). So yeah, I need to take a decision, now:

    * Enable OAuth2: not an option for the last XP/old Linux-friendly SeaMonkey release, 2.49.5, sadly. I would need to move my mailboxes to another of my OAuth2-capable SM2.53.x machines, but that involves Effort™... including reminding how in the hell I did my current Windows/Linux shared mailbox setup years ago!

    * Generate an app-specific password: Google really doesn't want you doing that because "DANGER MINES UNSAFE XINNIE ALSO HAS YOUR PASSWORDZ!!!", but this is still supported... for now. Unfortunately you need to enable 2FA on your Google Account, which requires either:
    1) enrolling an Android cellphone into the Googleborg™ (oh hell NOPE THE FUCK OUT!),
    2) installing Google Authenticator (which also most likely requires 1), plus risking getting permanently locked out of your email if you make any wrong mode, judging by the lovely truckload of 1-star ratings),
    3) using Winauth or friends (already experienced the pains of recovering a forgotten Steam accounr that way NEVER AGAIN!),
    4) using SMS codes, which suck (unlike what sekuritah paranoid nutters would believe, SIMswap hijacks are not of concern here as our telcos aren't THAT stupid, but our Soviet Venezuelan telcos are notoriously unreliable for everything else, including timely delivery of SMS OTP codes - already experienced that shit with Hotmail last year when it suddenly flagged my account for spam because I rarely send email these days)

    * Ditch MUAs and use webmail. Do I look like a masochist?!

    * Degoogle myself and pay for my own email. Of course, the only email account worth owning is the one you pay for, but sadly that's (currently) not an option for me as a citizen of this shithole. Not only that, but it will be also oh-so-convenient to spend weeks chasing down long-forgotten website registrations to get my email changed, also walking into my banks (oh dear, BANKS!!!) to update my email on fine, in the middle of a neverending deadly pandemic. I'm really fucked, it seems...

    Fuck my life. IF we survive the Mutual Assured Destruction between Put-It-In and the rest of the world, spare a couple nukes and direct them towards Mountain View and Cupertino, pretty please?

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-04, 23:35
    Dinosaur

    Post: #1063 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    Ended going with the SMS OTP codes option (also printed a backup codes card, for emergencies), just to create a app-specific password for SeaMonkey.

    The day Venezuelan telcos get shitlisted by 'murica (or fucked harder by Maduro), I'll get locked out of my email. But then, if that day ever comes, getting locked of my email will be the least of my worries... Either that, or Movistar/Google will find the way to get me screwed up hard. Oh, and Google still complains that "app-specific passwords are DANGER MINES UNSAFE TRUMP IS COMING FOR YOUR SOUL!!!", but at least it's no longer threatening me to get me locked out... for now.

    The authenticator apps are riiiight OUT of the question. Getting a hardware key is also a non-starter here. Migrating my mailboxes to a newer SM setup is still on the table (after all, that XP laptop will eventually die, plus I'm out of spare PATA 2.5" HDDs!), but that's something I can't be bothered to do right now.

    Degoogling is theoretically on the table, as soon as I can sort out my web hosting/domain situation (no money + my preferred hosting provider no longer offers email for personal hosting accounts, and all other "local" hostings are resellers for 'murican ISPs, soemthing I want to avoid for many reasons), but for now it's back to the drawer.


    ---

    Our friendly Fedora guy and extremey boring bug researcher, buc, has shared his SeaMonkey builds with the world - check them out!
    https://buc.fedorapeople.org/seamonkey/

    buc's builds have some very neat features:
    - Test patches implementing supports for some Chromeisms™
    - All localizations built-in, with automatic detection according to your system locale (and if you're not on Spain, it should default to es-AR!)
    - Site-specific UA overrides
    - Optimized build flags with newer compilers
    - And if you're using RPM distros, well, .rpm packages

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-08, 20:10 (revision 2)
    Dinosaur

    Post: #1066 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    Pixiv now fully drank the Chromeisms kool-aid, with a healthy spoonful of "fuck you, baka gaijin":

    - Google WebComponents® is now a mandatory requirement, which means Chrome, "recent Firefuxed", or maybe Safari.
    - You can no longer logon with a ordinary Pixiv ID - you must instead log on with Google/crApple/Twatter/Farcebook. Unless you are Japanese, of course: if you switch the page language to Japanese, you get a Pixiv ID logon form on top of the social network logon crapola.
    - Even then, if you're on a non-Google-blessed browser, said logon form will misbehave, trying to authenticate/redirect to URLs with "/undefined" on their paths, returning HTTP 400/404 errors.

    So yeah, if you wanna watch weeb porn cute Japanese art, it's Chrome or nothing.

    While I'm glad Japan is finally leaving the 1997 web behind, the replacement is even more horrible (Googleisms and cellphones), and very un-Japanese to me.

    Oh, forgot the mandatory FUCK PIXIV!

    UPDATE: Found a workaround - there is minimal, broken, very preliminary support for Google WebComponents™ on current SeaMonkey releases - nothing actually useable, but enough to fool Pixiv: you need to turn on the following prefs:
    - dom.webcomponents.enabled
    - dom.webcomponents.customelements.enabled
    Switch the logon page language to Japanese (sadly that's mandatory now if you still want to keep using your Pixiv ID), logon, done. The whole site will revert back to English (or to whatever language you've setup on your prefs) afterwards. Pixiv doesn't even seem to be using WebComponents® beyond the login page, so you should turn off those prefs after you're done (in order to not get other sites' hopes high!)

    The whole place works fine sans that logon page disaster, but overall it feels laggy as hell as Pixiv has gone full-on SPA since at least 2021, and their JavaScripts are... well, what you would expect from modern webshit, but with some Japanese hellstew thrown in for good measure.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-09, 03:53
    Custom title here

    Post: #1064 of 1155
    Since: 10-30-18

    Last post: 41 days
    Last view: 1 day
    Posted by tomman


    While I'm glad Japan is finally leaving the 1997 web behind, the replacement is even more horrible (Googleisms and cellphones), and very un-Japanese to me.

    Personally, I wish more sites were stuck in 1997. Simple, practical, low-bandwidth designs that offer everything you need and nothing you don't.

    --- In UTF-16, where available. ---
    Posted on 22-03-09, 05:01
    OBJECTION!!

    Post: #578 of 599
    Since: 10-29-18

    Last post: 38 days
    Last view: 8 hours
    Posted by CaptainJistuce
    Personally, I wish more sites were stuck in 1997. Simple, practical, low-bandwidth designs that offer everything you need and nothing you don't.
    Big same, really. But we all already knew that.
    Posted on 22-03-14, 00:57
    Dinosaur

    Post: #1070 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    My latest FUCK YOU AND ROT IN HELL goes towards MercadoLibre, the shittiest, unrivaled eBay clone we have in Latam. And unfortunately they don't have competition here in Soviet Venezuela (aside of Meth™ crapps AKA "Get Scammed, Robbed and Even Hurt zone").

    Three days ago I went to list some random junk I need to sell, everything went fine from my shiny new SeaMonkey 2.53.11.

    Today, I went to list some other random junk I also would like to sell, and... was greeted with more Chromeist regex vomit:
    "SyntaxError: invalid identity escape in regular expression"
    ...pointing to a one-liner, several megabytes vendor.js which seems to be highly rotten Node.js manure (did I forgot to mention that MercadoLibre is now a big fat blob of bloat that only causes pain for web browsers not named Chrome these days?). The offending regex seems to be this:
    /[\p{Lu}]/u


    And of course, I can't even use their fancy cellphone webshit crapp, as it's crippled by design (can't "clone" an existing listing there to modify as a new listing, which was what I was trying to do today), so it HAS to be a Chromeist web browser on a Real Computer™. Had to fire the testing Firefox setup while I used all of my willpower to not punch my laptop display (as I can't afford a new one... and it's not even fault of the poor ol' laptop that Google has become the Vladimir Fucking Putin of the web!) because I actually want to sell stuff online.

    If you work for MercadoLibre: DRINK POISON, NOW. I don't care about which poison, just drink poison and die.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-14, 02:56 (revision 2)
    Dinosaur

    Post: #1071 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    This is why we're getting more and more random sites breaking: since the Internet is now built over a pile of shitty JavaScript frameworks built over another pile of shitty JavaScript frameworks, you only need for one of their dependencies upstream to bring the Chromeisms™ (which have been decided by decree that no browser other than Holy Chrome™, its clones, and "latest Firefuxed" shall not be supported, EVER) to bring collapse to anyone deviating from The One True Browser, which is of course, Holy Chrome™:

    https://github.com/emberjs/ember.js/issues/19968

    Yes, it's Manchild screaming to the clouds again, but the guy has a serious point there: webshits DO NOT GIVE A DAMN these days, and use lame excuses ("it's not frameworks' fault that we break 'older browsers'", "developers decide which browsers to support"... except that 99% don't care) to defect their obvious responsibilities into this webshit pandemic.

    The day I finally drop off from the Internet is getting near for me, sadly. But hey, apparently digital ostracism is fun because "we must be disruptive! Disrupt All The Things!!!" in Silly Valley...

    ---

    In other less terrible news, it seems Asshole Master Tobin has dropped off the radar, due to unknown reasons (although I know that the relations between him and Moonchild have been a bit frosty at times) - he hasn't been insulting people (or even posting anything) on any public forum for at least the two months that have elapsed since 2022 began. GOOD. Hope he takes this timeout to become a better person, or at least to not behave like a dick in public, alienating more and more of the potential user base of any product where he is involved.
    On the flip side, Moonchild is working overtime to fill his void by being more snarky than usual...

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-15, 10:00 (revision 2)
    Post: #183 of 204
    Since: 11-24-18

    Last post: 77 days
    Last view: 12 days
    Posted by tomman
    This is why we're getting more and more random sites breaking: since the Internet is now built over a pile of shitty JavaScript frameworks built over another pile of shitty JavaScript frameworks, you only need for one of their dependencies upstream to bring the Chromeisms™ (which have been decided by decree that no browser other than Holy Chrome™, its clones, and "latest Firefuxed" shall not be supported, EVER) to bring collapse to anyone deviating from The One True Browser, which is of course, Holy Chrome™:

    https://github.com/emberjs/ember.js/issues/19968


    This problem has been known for a long time, but here is the obligatory XKCD (Dependency):

    Posted on 22-03-25, 02:04
    Dinosaur

    Post: #1075 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    So, Moz://a is trying yet another desperate plan to depend less on Google Alphabet's allmighty checkbook, by monetizing MDN:
    https://hacks.mozilla.org/2022/03/introducing-mdn-plus-make-mdn-your-own/

    Yes, the same Mozilla Developer Network where management sacked almost all of the department during the last major purge, with the excuse to giving it to the community (read: lrn2git). Apparently you can now pay Moz://a's to get notifications, article collections, and even a fancy PWA for offline browsing, while funding the SJWs and art school dropouts in charge of the UI/UX asylum.

    Needless to say, Hackernews' reaction on it is split:
    https://news.ycombinator.com/item?id=30792365

    - Half of the Hackernews believe that Mozilla is doomed and that we should all be praising Apple to be the last standout in the browser wars.
    - The other half thinks that Mozilla is tanking because their CEO salary is not big enough as Silly Valley has even more inflated salaries for CxOs and rockstar develpers is a "highly competitive environment". I wish I were making this shit up, but sadly money is what drives most software development these days...

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-25, 20:16 (revision 2)
    Dinosaur

    Post: #1076 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    Aaaand.... Tobin finally snapped off and went nuclear!
    http://web.archive.org/web/20220322141859/https://forum.palemoon.org/viewtopic.php?f=65&t=28003
    (archived link: the original thread now requires a login)
    UPDATE: The official fallout: https://forum.palemoon.org/viewtopic.php?f=1&t=28044

    ...and don't let the door hit your ass in your way out, asshole!

    Wow, "frosty" isn't enough to describe the relationship between Tobin and Moonchild. This dude is not just toxic - he is RADIOACTIVE! No wonder why many people (including me) ran away as fast as we could from Pale Moon. But seriously, comparing the leader of your project with 4chanisms is low, even for you. Guess you won't be welcome on any other software project (be it FOSS or proprietary), EVER - Tobin's ego is as large as Moz://a's CEO salary, and that benefits noone. Oh, and be careful to who you trust your root credentials, as you WILL get royally fucked should things go the Putin way!


    I'll stay with Team Seamonkey for my sanity, thanks.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-03-25, 23:38
    Custom title here

    Post: #1066 of 1155
    Since: 10-30-18

    Last post: 41 days
    Last view: 1 day
    Yeesh. Hopefully Moonchild's able to right his ship and undo the damage Tobin did both to the software and the reputation.

    --- In UTF-16, where available. ---
    Posted on 22-03-30, 18:05
    Post: #414 of 426
    Since: 10-30-18

    Last post: 341 days
    Last view: 15 days
    Posted by tomman
    Aaaand.... Tobin finally snapped off and went nuclear!
    http://web.archive.org/web/20220322141859/https://forum.palemoon.org/viewtopic.php?f=65&t=28003
    (archived link: the original thread now requires a login)
    UPDATE: The official fallout: https://forum.palemoon.org/viewtopic.php?f=1&t=28044

    ...and don't let the door hit your ass in your way out, asshole!

    Wow, "frosty" isn't enough to describe the relationship between Tobin and Moonchild. This dude is not just toxic - he is RADIOACTIVE! No wonder why many people (including me) ran away as fast as we could from Pale Moon. But seriously, comparing the leader of your project with 4chanisms is low, even for you. Guess you won't be welcome on any other software project (be it FOSS or proprietary), EVER - Tobin's ego is as large as Moz://a's CEO salary, and that benefits noone. Oh, and be careful to who you trust your root credentials, as you WILL get royally fucked should things go the Putin way!

    I'll stay with Team Seamonkey for my sanity, thanks.


    Temporarily Offline

    Internet Archive services are temporarily offline.

    Please check our Twitter feed for the latest information.

    We apologize for the inconvenience.


    AMD Ryzen 3700X | MSI Gamer Geforce 1070Ti 8GB | 16GB 3600MHz DDR4 RAM | ASUS Crosshair VIII Hero (WiFi) Motherboard | Windows 10 x64
    Posted on 22-03-31, 00:55
    Dinosaur

    Post: #1078 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    Works fine here, might have been temporary.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-04-03, 02:08 (revision 1)
    Post: #415 of 426
    Since: 10-30-18

    Last post: 341 days
    Last view: 15 days
    Yup working now.

    AMD Ryzen 3700X | MSI Gamer Geforce 1070Ti 8GB | 16GB 3600MHz DDR4 RAM | ASUS Crosshair VIII Hero (WiFi) Motherboard | Windows 10 x64
    Posted on 22-04-12, 00:33
    Dinosaur

    Post: #1084 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    https://ircbot.comm-central.org:8080/seamonkey/20220410#c193723
    https://ircbot.comm-central.org:8080/seamonkey/20220411#c193772
    (ignore the self-signed cert warnings)

    Oh boy, Tobin is still roaming around...

    (Apparently all his bad blood towards Mozilla-derivative projects began years ago when he couldn't get along with some SM devs, namely frg... and it has gone downhill since then)

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Posted on 22-04-15, 21:33
    Dinosaur

    Post: #1089 of 1295
    Since: 10-30-18

    Last post: 1 day
    Last view: 4 hours
    Starting late March, Google WebComponents® is mandatory for Pixiv, not only for logon:
    https://forum.palemoon.org/viewtopic.php?f=3&t=28107

    So yeah, we lost the Japanese Internet to Google too :/
    In the case of SM/PM/non-Chrome-or-latest-Firefuxed, dom.webcomponents.enabled is enough to make Pixiv work again, but dunno what other features of this quasi-proprietary ever-unfinished spec they require. Also, it's a bad idea to leave that pref always on considering that it may break more sites (if they aren't already broken, that is!).

    The Internet is just a "git pull" from a webshit crapcoder away from becoming the Googlenet™, yet people insist into only blaming Google and folks. Nope, webdevs are also guilty of this shitfest, either by omission (by not knowing what the fuck that fancy JS framework is doing under the hood, and updating willy-nilly without even reading the release notes, much less testing before pushing to Production) or actively willingly ("old browsers are UNSAAAAAFE DANGER MINES WORLD WAR III!!! Why don't you just use Chrome?"). Next time you're considering updating a website/webapp, STOP, use your brain, and look at the world around you, which is populated by ordinary people, not artists/"innovators"!

    As a minor positive note: you can now logon to Pixiv with an ordinary Pixiv account without having to switch the whole site to English first.

    Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
    Pages: First Previous 25 26 27 28 29 30 31 Next Last
      Main » Discussion » Mozilla, *sigh*
      Yes, it's an ad.