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 |
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™) |
| desudesu |
http://pigeonsnest.co.uk/stuff/webshite/index.html Reminds me of a lot of the sentiments in this thread about JS, CloudFlare, TLS and whatnot... here's hoping he does something about WebComponents lol |
| tomman |
How to integrate SeaMonkey with your Debian desktop: 0) Install SeaMonkey to /opt/seamonkey, make sure your user owns that folder if you want for autoupdates to work. 1) Integrate with the alternatives system: 2) Make a .desktop launcher, either at /usr/share/applications/seamonkey.desktop (systemwide), or ~/.local/share/applications/seamonkey.desktop (per user) 3) MATE will behave stupid when letting you select SeaMonkey as your preferred web browser/email agent. I guess this should solve itself after several logons/logoffs, or whatever. YMMV on other DEs. 4) Obviously, don't forget to run SeaMonkey and click that magical "I want to be your default web browser and everything else" button when prompted. |
| tomman |
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. |
| tomman |
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) |
| Nicholas Steel | Yup working now. |
| tomman | Works fine here, might have been temporary. |
