Post help
Presentation
[b]…[/b] — bold type[i]…[/i] — italic
[u]…[/u] — underlined
[s]…[/s] —
[code]…[/code] —
[spoiler]…[/spoiler] — spoiler block
[spoiler=…]…[/spoiler]
[source]…[/source] — colorcoded block, assuming C#
[source=…]…[/source] — colorcoded block, specific language[which?]
[abbr=…]…[/abbr] — abbreviation
[color=…]…[/color] — set text color
[jest]…[/jest] — you're kidding
[sarcasm]…[/sarcasm] — you're not kidding
[url]http://…[/url]
[url=http://…]…[/url]
>>… — link to post by ID
[user=##] — link to user's profile by ID
[quote=…]…[/quote] — "Posted by …"
[quote="…" id="…"]…[/quote] — ""Post by …" with link by post ID
code block[spoiler]…[/spoiler] — spoiler block
[spoiler=…]…[/spoiler]
[source]…[/source] — colorcoded block, assuming C#
[source=…]…[/source] — colorcoded block, specific language[which?]
[abbr=…]…[/abbr] — abbreviation
[color=…]…[/color] — set text color
[jest]…[/jest] — you're kidding
[sarcasm]…[/sarcasm] — you're not kidding
Links
[img]http://…[/img] — insert image[url]http://…[/url]
[url=http://…]…[/url]
>>… — link to post by ID
[user=##] — link to user's profile by ID
Quotations
[quote]…[/quote] — untitled quote[quote=…]…[/quote] — "Posted by …"
[quote="…" id="…"]…[/quote] — ""Post by …" with link by post ID
Embeds
[youtube]…[/youtube] — video ID only please| Thread review | |
|---|---|
| tomman |
Posted by creaothceann "Login", "signin", same meaning. Yes, that's the page that now breaks on SeaMonkey due to JS abuse and a ordinary button literally named "submit". The fact this works on Chrome and its clones means that they decided to do the right thing (for once!) and assume that a button named "submit" is NOT a override for form.submit(), and that older web browsers (including Mozilla/Gecko) has always been doing weird shit there (maybe that weird shit dates all the way back to Netscape, who knows?). But then the web itself is built over foundations made of weird shit, so... Nonetheless, naming ANY element inside a form "submit" is an extremely dumb idea for other reasons. |
| creaothceann | I just googled "imgur login" and https://imgur.com/signin was the first result. It worked from there. |
| tomman |
Mozilla rebrands. AGAIN. https://blog.mozilla.org/en/mozilla/mozilla-brand-next-era-of-tech/ The new logo is even more stupid than the Moz://a era one. But hey, they hired a Very Expensive advertising agency to come up with this abomination, and look how nice it looks at the badges they use at the San Francisco HQ! In the meanwhile, Mozilla keeps losing more and more relevance, and the only thing that can save us from a grim Chromey future is... the US Deparment of Justice. "Next era of tech", AKA "doomed". Stop donating to Mozilla and send your money to other projects that actually need and deserve it: Waterfox, SeaMonkey, Ladybird, and yes, even Pale Moon. -- In other stupid news, the latest one to break their website in our Not Chromey browsers is Dunno how they got this obviously broken junk working on Thy Holy Chrome™, but this renders users like me unable to login directly into Imgur. The workaround, based on that blogpost I found involves running these Javascript lines in your browser console: The second line will trigger the actual real form.submit method, letting me login... for now. Remember me to never send my CV to houses run by clowns, thanks. |
| tomman |
In this episode of Brand Necrophilia: America On-Line revived Netscape Browser... as a Chrome clone: https://wetdry.world/@ipg/113491635810847495 https://xcancel.com/TRX7800X/status/1857791517110530222 I wish I were making up this crap, but no, it's real - apparently the Netscape brand has survived for the last decade as a small ISP, part of the AOL empire (because apparently AOL still has subscribers in USA, mostly elderly people that hasn't realized dialup is beyond useless in 2024), and now AOL hired some Of course, the Father of Mozilla / Emeritus Asshole JWZ has already disowned this abortion of nature. All this dogvomit comes in the middle of the DoJ push to get Google to divest Chrome, something that sadly is not likely to happen after next January in the light of recent political events :/ |
| tomman |
After almost 2 decades of serving me well, I finally retired my trusty nx9010 from active duty, and that includes email. Time to move almost 2 decades of mailboxes that began life many moons ago under some flavor of Outlook Express, then Outlook, then Mozilla Suite, then Thunderbird, and eventually - Download your email as usual on the old system, for one last time. - Backup your email folders (usually at $PROFILE/Mail/) and make a backup of that backup, just in case. - On the new setup/profile, recreate your accounts using the exact same info (login, etc). Setup them as you had them in your old profile (identities, aliases, server settings, etc.) - Close SeaMonkey, go to $PROFILE/Mail/ on the new profile, and for each account you need to restore, enter on its respective mail server dir, delete all the files already there, and copy the set from the same server from your backup in its place. Don't get tempted to do this BEFORE creating the account, as SM will find that the directory exists, and create your account into a new directory as a precaution! - Run SeaMonkey again - your mail should be exactly as you left it last time before the switch. Yay~! Also, good timing because MICROS~1 started threatening me with a good time: starting next September, you need to switch to Modern™ authentication methods to keep your ability to send and receive email from your - 2.53.18.x should work for MS, but better use the nightlies (or at least, the recently shipped 2.53.19 beta 1!) - You need to fix a couple prefs: open about:prefs, and search for "scope". You will find at least two prefs per each OAuth2-capable account: mail.server.server$NUMBER.oauth2.scope For your Outlook accounts, you will notice the value contains a bunch of URLs that begin with https://outlook.office365.com/ - those will NOT work! Edit them and remove all instances of "365" from the URLs (do NOT modify anything else!!!) The pref should look like this now: - Microsoft will identify SeaMonkey as "Mozilla Thunderbird", since they're piggybacking over TB's app ID - getting one issued by MS is already a kafakesque nightmare. Technically, MS also offers app passwords (just like Google), if you have enabled 2FA on your account. But they do not advertise that, they certainly didn't mentioned them on their announcements, and I'm not going to waste a single extra braincell on more security theater. For now. Oh, and MICROS~1 is deprecating the fallback XP-era Outlook web UI that we get on SeaMonkey and other non-Chrome browsers too. You know, the one that actually sips bandwidth and it's SANE (albeit with a very dated style). Fun. |
| tomman |
I never bothered using release versions of SeaMonkey on my daily driver anymore - the nightlies are Good Enough™ for daily usage given the slow pace of changes. You may want to ask frg and folks on IRC for any late-minute breaking changes (and watch out with your addons!), but these days I just upgrade to the latest nightly once or twice a month. From the Chromeisms front, the latest serial offender is Clownflare, as usual - they now have a tradition of breaking any non-Chrome'd browser YEARLY without explanation: https://news.ycombinator.com/item?id=31317886 https://community.cloudflare.com/t/browser-integrity-check-broken/381029 https://community.cloudflare.com/t/broken-in-the-latest-pale-moon-what-does-cloudflare-require-to-work/518036 Two weeks ago, I fell victim to this, and at very sensitive place: one of my banks (to name and shame: a hipster-ish bank that goes under the stupid name of Bancamiga - literally means "FriendlyBank" in English!) decided that it was an AWESOME idea to deploy ClownFart's Browser Integrity Check (which is the most likely reason to get served CF captchas these days if you get caught using a web browser not approved by the Internet Party), and combined with a late minute update by Clownflare, I got effectively locked out from logging in into my bank (where I have, among other things, part of my savings, my one good credit card, and even a international debit card from the very few authorized to be issued in this country, so just closing this account and switching banks would hurt me BADLY). Called the bank, told them that ClownFart got in the middle, got told to pound sand and "upgrade my web browser, clear the cache and cookies, and try again or use a cellphone". Even called Venezuela's banking regulator (got the chance to don my Loyal Party Member™ cosplay), telling them that Clownflare not only was getting in the middle, but also the bank got unresponsive AND CF being a California corporation means that this bank is one Executive Order away from breaking the laws (effectively turning this into a potential national security threat, yay~!). They tried initially to dismiss me with the same pathetic excuses as used by the bank ("y u no cellphone?"), but eventually they told me to file a formal complaint letter to the bank, OVER EMAIL, then wait 20 days... and if the bank doesn't favorably reply, I should call again to escalate the complaint (I'm still in the process of gathering enough legal and historical background to write said letter). After some online research, turns out that I wasn't alone - Pale Moon users were being subject to the same ABUSE by Clownflare's latest deployment of Chromeisms... and even worse, they were dismissing Moonchild's formal support ticket (he is a paid CF customer) under bogus arguments. Users complaining at CF's forum (which uses the abomination known as Discourse, so a double whammy for us not using a Jeff Approved™ browser) were also being shooed away, to file useless claims with site operators for a problem caused by CF. Incredibly, before we were forced to escalate the complaint to Silly Con Valley's complaint department (aka Hackernews), someone at Clownflare realized the fuckup, and 4 days later I was able to logon into my bank again... and to the other half of the Internet relying on Browser Integrity Check, but only after enduring "you are a human, right?" checks on SeaMonkey because I'm a threat to CF's bottom line, it seems. If you work at ClownFart: FUCK YOU. Hope our paths never cross in this life or things will end [censored]. You're a enemy to the Internet and to freedom. Hope you guys get hacked to shreds by [insert your favorite villain here] - mightier evil actors have fallen, and CF won't be the exception! Site operators: STOP USING CLOWNFLARE SERVICES FFS! CF doesn't care about security, they care about being in control of everything - they have the MITM power that many governments around the world drool with... As for Bancamiga... I was happy with the services of this bank, but not anymore - trust takes forever to build, and seconds to destroy. This case is NOT closed yet, I shall get that formal complaint letter filled promptly, to serve as a warning for the rest of the banking system in Venezuela. (I sincerely hope that if The Angry Cheeto wins again, he bars Clownflare from selling services to my country) |
| tomman |
2.53.17 is now on beta... but I'm gonna skip that release. Why? Because I've switched (for now) to the nightly builds, and those are already at 2.53.18, which now implements pretty serviceable support for some annoying Chromeisms, including the latest regex vomit (backported from Waterfox) and Google WebComponents® now being enabled by default (but not Shadow DOM yet!) - those two are MANDATORY for most of the modern web since it relies on hipster JS framenotworks. Seriously, it's that good. Backup your profiles, and monitor #seamonkey for possible breaking changes and pleas for testing the nightlies and betas - we really need that! --- The latest Chromeism of the week is a particularly NASTY one: Web Environment Integrity: https://github.com/RupertBenWiser/Web-Environment-Integrity https://www.theregister.com/2023/07/25/google_web_environment_integrity/ Banks, Hollywood, and other Big Corps are gonna love this shit, straight out of the deeply locked jails of cellphones! If you hated your bank because their mobile crapp wouldn't run on your rooted/custom ROM flashed cellphone, they will also now be able to refuse access to their web portals too unless you're using a Legit™ browser/OS combo! This not only hurts alternate/non-Chrome browsers even harder, it even bars Chrome forks or even local builds of Chromium! Welcome to 1984, this is the future we wanted.... NOT! If you work for Google and don't QUIT NOW, you deserve all the insults you're getting online for horrible moves like this. No 6-figure salary and stock options are worth killing whatever is left from the freedoms of Internet and computing - might as well switch to making murder machines for the military! |
| Kawaoneechan |
Posted by tommanhttps://helmet.kafuka.org/flashblock_fixed.xpi |
| tomman |
2.53.15 broke good ol' Flashblock. Yes, Flash is dead. But Flashblock can also block HTML5 video, which is highly needed nowadays in the era of poor bandwidth and metered fake 4G cellphone networks. Adblockers can achieve the same, but I don't need full-fat uBlock as my current adblocking solution is perfect for my needs. Turns out Flashblock was using some long, LONG deprecated Mozilla-proprietary JS feature: getPreventDefault(): https://bugzilla.mozilla.org/show_bug.cgi?id=691151 But then, Flashblock has been dead for pretty much almost the same time, so noone bothered checking... until today! Simple fix: replace all instances of getPreventDefault() with the standards-compliant defaultPrevented on flashblock.xml/videoblock.xml (inside $ADDON_ROOT/chrome/flashblock.jar!/content/flashblock/). Repack, reinstall, done. Or just use my fixed XPI: https://we.tl/t-uNjyaVA2l9 (link expires in one week - please rehost!) |
| CaptainJistuce |
Posted by tommanYEEEEEEEEEEEEEEAH!!!! |
| tomman |
https://www.seamonkey-project.org/releases/seamonkey2.53.15/ GO! |
| tomman |
Apparently enough stuff has been backported to make Giggityhub more-or-less "work" by just enabling dom.webcomponents.enabled on the latest betas, according to frg. I guess it's time to backup my profile and hop again onto the beta train, but at this stage I wish that a deadly pandemic just wipe webshits from the entire planet so the web standards can go back to being STANDARDS, and not a eternal moving target. Alas, that's not happening :/ If you work with/for the Google Chrome team: DIE. |
| NTI |
Thank you, man!! Once again you just saved the day!!! Was wondering what happened as Garbagehub just stopped working sanely when downloading stuff. While room to maintain functionality gets tighter each day, I'm willing to hold on as much as I can to honour the good job made by the Seamonkey devs in this sick and condemned world. And as a matter of fact, new release out!! Sadly, this one breaks the latest working Greasemonkey addon version, but it isn't much of a big lost, as I just used it to remove URL tracking. |
| tomman |
PSA: If you're using Palefill on SeaMonkey and Giggityhub broke for you (AGAIN), do this: 1) Downgrade to Palefill 1.23 here 2) Disable addon autoupdates for Palefill 3) Pray ...this is because Palefill has never really supported any browser other than Pale Moon (and UXP-based web browsers up to some extent), and not anything else. Some changes the way it loads polyfills were introduced recently, leveraging on Pale Moon-isms (gross hacks gated behind PM-specific user prefs), breaking things on SeaMonkey because it doesn't implement said hacks: https://github.com/martok/palefill/issues/67 So... yeah, that renders Palefill unusable for us in the near future. And the progress for implementing the Chromeisms required for most of the modern web on SeaMonkey is marching slowly, so I guess the road has become bumpier than usual :/ |
| tomman |
Posted by NTI And here comes the problem, as the "web standards" these days are largely designed, written, approved and implemented by Google these days. The W3C just rubberstamps them for Google, and Mozilla these days are even lifting Chromium code wholesale to keep up with the latest Chromeisms. You may even say that there are no web standards anymore, but the "standard" is what Chrome does. Posted by NTI Welcome to modern IT in a nutshell: nobody cares about efficiency, or how it works under the hood. People only care how fast you go from zero to app. This same crapola is killing native development in favor of more Electron abominations, just because "move fast and break things" and "web is the new native". Quality costs money and it's even a bug, not a feature. After all why are you even using a budget Android phone and a 6-year old laptop instead of a iPhone 14 and a M2-powered Mac? |
| NTI |
New beta!!! https://www.seamonkey-project.org/releases/2.53.14b1 Despite web pages getting worse each day (two-thirds of the internet broken because of poorly written javascript garbage or other not compatible crap stuff), it's nice to have a sane browser which in fact follows web standards. For the most part, I will always judge a website and their developers if it works or not on SeaMonkey. (But sadly, I will have to resort to Mozilla Crappyfox because of online tools used at work and important gov services stuff, and even then, they are still half-broken on latest Firefox because it uses exclusive Chrome shit) Damn... I have no ideia how mankind got itself so deep down into this hole... Very hard to see any light of hope at seeing web developers to actually care about the quality of their profession, altough neither the market cares about it. At least over here, no company at all gives a damn about good engeneering, they just wanna see things "to work" and are not worried at how it's done, which probably helped to infest web development with this bunch of web con artists. They are paid very well for the garbage they vomit and are even encouraged to learn "react" or whatever is trending nowadays in "career courses", as it is what "the market is after for". |
| tomman |
It seems the GiggityHub WebComponents® polyfill addon for our beloved browsers has been largely abandoned, and GiggityHub now breaks every other week because of course the Microsoft-payroll crapcoders are too busy pushing hot new untested stuff to production. Instead, there is a new kid in the block: Palefill. Don't let the name fool you - it will not only work on Pale Moon, but also on many XUL/UXP-based browsers, including SeaMonkey. It's also designed to be easily extensible via rulesets: just add the domains and required Chromeisms to the ruleset, reinstall (sadly the ruleset isn't user-editable yet), and done. Works fine for GiggityHub... and Pixiv. Mostly. The War Against The Googlenet™ marches on... |
| wertigon |
Posted by tomman Sounds like it is time to bring out the old user-scripts and user defined CSS again. |
| tomman |
Nearly every single Discourse-powered forum is now - iDevices - High end Android cellphones - High end computers bought in the last 2 years Everything else severely disrupts The Vision™, and therefore should be barred from ever accessing a Discourse forum. But since this is Asswood, a simple "your browser is too old, please install Chrome" banner isn't enough - the guy and his staff engages into dirty warfare sabotage tactics: - CSS sabotage: html {overflow-y: hidden !important;} kills scrolling. - Even if you manage to get past that CSS trap, you'll find that you can't click links because of yet another JS booby trap: jQuery bogus click event handlers! This. Is. WAR. Dear Jeff Atwood, the Discourse "cutting edge" development community, and operators of Discourse-powered boards: FUCK YOU VERY MUCH! GO BACK TO FACEBOOK, YOU DIPSHITS! CLOSED WONTFIX USECHROME BUYAMAC NOLONGERWELCOMEHERE |
| tomman |
https://www.seamonkey-project.org/releases/seamonkey2.53.13/ GO GO UPDATE NOW GO GO GO~!!! > Adding initial optional chaining [...] Sweet! (this is the hideous ?. operator that breaks the other half of the Web not broken by Google WebComponents™) |
