Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
Posted on 21-01-13, 11:29 in I have yet to have never seen it all. (revision 1)
Dinosaur

Post: #881 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
http://www.newsdzezimbabwe.co.uk/2021/01/new-banknotes-for-zim.html
https://banknotenews.com/?p=31890

- Soviet Venezuela, current world champion of hyperinflation: "We have the highest inflation rate IN THE WORLD!"
- Good ol' Zimbabwe, former world champion of hyperinfation: "Hold my beer~"

The return of the ONE HUNDRED TRILLION DOLLARS banknote is near, I tell you! When your central bank says "we're going to print larger bills so you can make your transactions more efficiently", they actually mean "you're fucked, so here is your stack of fresh, worthless bills".

But what makes Zimbabwe different from Venezuela is that they can get the printing presses started at short notice whenever they want - they can literally keep printing banknotes and redenominating their currency several times a decade if they want, sanctions or not. In the meanwhile, our largest banknote is still stuck at the 2019-vintage four-zero 50000 bolivar note... which is currently being printed at the fuckin' Soviet Union because nobody wants to risk selling supplies to our dilapidated Central Bank, whose fancy mint has been sitting idle for months (if not a year by now!). Either you're American-owned and can't sell supplies to us due to the sanctions, or you're not American yet don't want to end like De La Rue (which had to take a $MANY_MILLIONS hit due to unpaid bills for all those Sovereign Bolivar notes that are now sitting at bank vaults or brutally shredded, littering our streets). No word yet on reviving the 100K note, despite the 50K one being only worth 3 cents* (it was worth $8 when it launched on mid July '19, and yes, you still need those to catch COVID-19 and die on a crowded bus because you can't afford gas pay the bus fares) and the countless Bloomberg rumors of the thing actually coming... because who would be willing to print it for free?

Oh, and Zimbabwe is a clear example of how a bunch of authoritarian assholes can ruin a working dollarization ("bond notes" my ass). Take note, Maduro!


*(as of today, January 13th 2021, 07:28 VET)

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-14, 11:22 in I have yet to have never seen it all.
Dinosaur

Post: #882 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by Nicholas Steel
Posted by tomman
For data recovery labs around the world, 2021 just started with a BANG!

The moron that did that to that Toshitachi deserved to lose all his/her data. At least the DR guy got a nice Moto Racer CD case :D
Note that Google/Firefox is marking the sites image host as dangerous.

Which is a very good reason to fucking DISABLE "Google SafeSearch", as it has been false-flagging HDD Guru for WEEKS yet Google doesn't give a damn.

The only dangerous thing here is Google meddling with every URL you visit.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-14, 22:02 in Stupid computer bullcrap we put up with. (revision 4)
Dinosaur

Post: #883 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
So I went through what it would call the Longest Reboot EVER.

Dell laptop spent last 3 days unusually running Windows 7 ("unusual" because... I don't boot to Windows lately) without issues. The same Dell with the flaky GPU that manages to upset Radeon kernel driver under Linux every now and then (sometimes Xorg would freeze after waking up display, sometimes the whole machine would freeze during display sleep). Then I reminded I had to scan something so I had to reboot. Windows would happily shut down and... the machine never came back!

Trying to powercycle it just led to a dead display and no POST attempts whatsoever.

Removing the CMOS battery didn't helped (there is no "clear CMOS" jumper on laptops!). Removing the main battery didn't helped. Reseating RAM (this Dell has a flaky RAM slot) didn't helped. Pressing a bit over the video card (there seems to be a flaky contact on the proprietary PCIe x16 slot on this Dell that often leds to missing red on the VGA port) didn't helped!

Shit~!

Long short story: I had to take the Dell apart, clean some dust (it wasn't that much, except for a minor dust "carpet" over the fancooler exhaust fins), wipe some minor corrosion under the CPU socket (for the Eurotards that imposed over us the RoHS soldering plague: go catch COVID and die, plz), then reassemble it and try. And of course the thing came back to life. Then died again during reassembly. Then had to remove the display panel and WLAN card until the thing booted again. Reassemble everything again, and we're back to action. Phew! And it only took me TWO HOURS to reboot to Debian just to scan a piece of paper!

It's my IBM TV box all over again! These two rigs now have the nasty habit to die during a reboot, something I used to think it wasn't possible (except due to a failed BIOS/firmware flash)

My computers HATE being fingered too much, or too little, that's a fact I learned over a decade ago with Saki. Either that, or they're like my aircon or my $FORMER_BOSS's cars: when they smell a few bucks on my bank accounts, they decide it's a good time to break.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-16, 21:54 in Board feature requests/suggestions
Dinosaur

Post: #884 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Sooooo... Seamonkey is telling me the site is DANGER MINES UNTRUSTED CONNETION GO AWAY YOUR LIFE IS IN DANGER!!!

SEC_ERROR_EXPIRED_CERTIFICATE

At least Seamonkey still treats me as a grown up man who can take responsibility of his own actions, so I can just "Let's Encrypt, *sigh~*" and go.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-16, 22:17 in Stupid computer bullcrap we put up with.
Dinosaur

Post: #885 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Bonus: every time you take apart one of those modern half-plastic half-guts, something is bound to break after repeated cycles of heat-cold-heat-cold-heat.

This time I had my aircon serviced (I still manage to do it yearly: it's far easier to gather $20 than $2000 for replacing overheated electronics). This is a split unit, and the outer half is outside, at the mercy of the elements (which are anything BUT kind with the huge external box full of pipes and gas). When the technician went to unhook the power wires, the wiring panel (which is a thermal resistant plastic) cracked. Oops~! (The guy managed to resolve the situation with electrical tape, cardboard (!!!) and zip ties, in awesome Soviet McGyver style). Last year, the inner half cover air vents cracked too because the thing has those stupid snap-on hooks which are tricky to hook because they were invented solely to piss off both experienced technicians and aficionados.

Same with my Dell: the hinge cover does not hook up properly anymore, one of the top case screwposts is pretty much reduced to random bits of cracked plastic, there are a couple seized screwholes on the display hinges (!!!), and while testing bootability with the battery, I managed to break the battery removal latch! (A fingernail or flathead screwdriver must now be used to operate the broken latch.

Despite all that, I still have a working air conditioner (the Samsung-made compressor can still do ~5.5ºC despite being receiving abuse during the last 8 years in suboptimal conditions!), and a working laptop (which can still run everything BUT AAA+ bugfests and Electron/React abominations), but yeah, this leads me to understand two things:

1) No device made prior to RoHS/"send all the production to China" will disintegrate into your hands every time you need to service it!
2) When your device starts disintegrating, maybe it's time to let it go and buy something new... maaaaaaaaaaaybe. Or at least, keep the hot glue and zip ties ready at any moment!

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-16, 22:24 in I have yet to have never seen it all.
Dinosaur

Post: #886 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
https://www.theregister.com/2021/01/14/hellabyte_si_prefix/
https://news.ycombinator.com/item?id=25788993

Californians are trying its hardest to push their fancy new unit prefix to SI units, "hella", which equals 1027. Suddenly, stuff like "hellabytes of porn" starts making sense. Except that the SI guys already had other plans, which involves names taken from their grandmothers, it seems: "ronna" for 1027 and "quetta" for 1030, so those pesky North Californians have a uphill struggle to get those SI folks to change their minds.

I myself would suggest standardizing "fuckton" and "assload" instead.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-18, 19:28 in Mozilla, *sigh*
Dinosaur

Post: #887 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
The day Giggityhub (and by extension, Microsoft/Google) sent Pale Moon (and by extension, each and every non-Chrome browser that isn't "latest Firefox version") to eat a bag of dicks:

Posted by "J.J. - GitHub developer support"
... it would be disingenuous of us not to recognise that there is clearly a difference of opinion where our use of custom elements is concerned. GitHub considers this open specification part of a diverse and healthy set of modern web standards. As these standards continue to be adopted and supported by web developers and browser maintainers (Chrome, Firefox, Safari, and Edge), we will continue to make use of them. For browsers {sic: without support for WebComponents} ..., further degradation is a likelihood.

I appreciate that this is disappointing and frustrating for you, as the lead developer of one such browser, but we would like to be upfront and honest about the future implications here.


In other words: "fuck you browser outcasts - Google sez we must chase shiny, and we love shiny so it's Chrome or DIE, so GTFO"

Related thread: https://news.ycombinator.com/item?id=22604070 (roughly half of the replies goes with the "alternate browsers are obsolete junk and nobody uses them, so why bother?" meme, which is expected from the HN crowd)

If you need a big reason to NOT host your sources on Giggityhub, I hope that one is heavyweight enough. Unfortunately most (if not all) source code forges/repos have assumed the same "shiny Javascript" disease as GiggityHub, because that's the Silly Valley 'tude for you (even if said code comes from outside the Valley). Apparently bloating the web with complexity is a signal of a "diverse and healthy set of modern web standards".

And yet, when all of us "browser outcasts" should unite and tell SV to GIT OUT, the community gets more fragmented than ever due to ego wars. Just like The Year of the Linux Desktop™ meme :/

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-20, 10:22 in Mozilla, *sigh* (revision 1)
Dinosaur

Post: #888 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by Nicholas Steel
The day Giggityhub (and by extension, Microsoft/Google) sent Pale Moon (and by extension, each and every non-Chrome browser that isn't "latest Firefox version") to eat a bag of dicks:

Posted by "J.J. - GitHub developer support"
... I appreciate that this is disappointing and frustrating for you,


WHAT??!?


Yes, they appreciate that you're suffering punishment because you chose to deviate from the Holy Way Of Chrome. SV turds are that nice.

Found another "opensource" bugtracking software you will want to avoid, and it had to be a serial Webcomponents abuser Google product: Monorail.
Relevant log:
[11:30]   tomman  https://bugs.chromium.org/p/chromium/issues/list fun, more Google Webcomponents blast! (does not work on Seamonkey)
[11:31] robobox they could have done that in 50 lines of css and another 30 of javascript
[11:31] tomman Well, I guess I'll add Monorail to my sh*tlist
[11:31] tomman what's the point of a bugtracker if you can't use it because it's broken?
[11:32] tomman oh, they have a "View in the old UI" link
[11:32] tomman ...that it's only a list of projects that redirect you to their borked Webcomponents junk
[11:33] robobox file a bug on monorail
[11:34] tomman "Monorail supports all browsers defined in the Chrome Ops guidelines."
[11:34] tomman OK, they do allow to do that
[11:34] tomman log me with my Google account.... fine
[11:35] robobox I only use those for google mail and youtube (although not much worth watching there execpt music)
[11:35] tomman https://chromium.googlesource.com/infra/infra/+/master/doc/front_end.md "Chrome, Chredge, whatever browser ships on iDevices because Apple, and I guess latest Firefox"
[11:36] robobox wonder what they say about SM, if anything
[11:36] tomman lovely, their compatibility list for Monorail is their "Chrome Infrastructure" list, aka what Google cares
[11:36] robobox it seems to work in ESR 78
[11:40] tomman https://bugs.chromium.org/p/monorail/issues/detail?id=8963 HA! I can't even read my own bug report!
[11:40] tomman LOVELY
[11:41] tomman so yeah, I guess I'll stick to Trac for when people ask me for a simple, modern bugtracking solution
[11:42] tomman I can feel myself channeling my inner jwz


If anyone can tell me when they "appreciate my disappointment", here is the ticket. Not that I can read it because I am one of those "browser non grata" outcasts.

A broken bugtracker. I thought I had seen everything in this life, but computers remind me every day that suckage has a sub-basement.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-20, 20:31 in Mozilla, *sigh*
Dinosaur

Post: #889 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by funkyass
It also doesn't work on FF 60 ESR, which was from 2 years ago, and what Seamonkey is currently based on.

This is like complaining about doom not running on a 286.

Except that there is a difference: Doom was state of the art when it was released, a groundbreaking game for a whole genre, designed to push hardware of the era to its limits, so if you wanted the best Doom Experience, you had no option but to upgrade that 286 to something GOOD, like a 486DX2 or something. It's a videogame, it's designed to give you pleasure to all your senses (except for taste, and definitely not smell!), but there is a price you have to pay, and if you don't agree, you can still play Commander Keen on your EGA dinosaur while all the other kids in the block beg mom and dad for money for a new sweet cool rig (which also will let them do more).

Monorail is something more mundane: a bug tracking software. By its very nature, you want your bugtracking solution to be as robust as possible (maybe even more than the software projects you're tracking with it), the very last place where you want to push tech to its limits. Why in the hell a freakin' bugtracker requires WebComponents? What's the benefit other than locking out people using non-Chrome non-mainstream browsers? While it makes sense for Google to dogfood their own software, they actually offer Monorail as a solution you can use for your very own software projects (be it public or private), so locking out "ooooooold" browsers (which actually they aren't old - they just can't keep with their mindless "living standard" webshit crapola) is a very odd (read: disrespectful, assholeish) way to interact with your users. Thankfully, Monorail has plenty of competition (Bugzilla, Trac, Redmine, JIRA -which comes from the Atlassian bloat factory, now with more cloud!-, and nearly every GiggityHub clone) that aren't deeply into this web standards sabotage AKA the endless chase for change for the sake of change.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-20, 22:36 in Mozilla, *sigh* (revision 1)
Dinosaur

Post: #890 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Posted by funkyass
Doom required and designed around the memory model of the flat model of 386's protected mode. You could rewite the memory management to work on with 286's PM, but it would be next to unplayable, and you'd need to reboot the machine afterwards.

And the funny thing, support for web components was fully enabled in FF 63, added in FF 59.

does seamonkey's about config have dom.webcomponents.shadowdom.enabled somewhere?

Seamonkey has dom.webcomponents.enabled and dom.webcomponents.customelements.enabled, but not that one.

Anyway, they don't work (I've tested them during the GH saga) as the support is simply not yet there, and there is barely any manpower left to please the Googles. I guess things might improve when 2.57 (which is based off FF60) gets released, but they're far away from anything resembling a beta, much less an stable version. When that happens, most likely Google may have added something new and shiny to the "living standard" (because the W3C has become little more than a rubberstamp for Google's silly additions to the standards), and Webcomponents may have become old news, half the web would still be broken on alternative browsers, and I would still be ranting about the same because the world is fucked up :/

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-21, 14:44 in Computer Hardware News
Dinosaur

Post: #891 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
This rumor is now doing the rounds at the news:

Intel to outsource 5nm Core i3 production to TSMC

But it doesn't seem to end there: Intel has already outsourced some percentage of non-CPU parts (i.e. chipsets, NICs) to outside fabs. If these rumors turn out to be true, it means not only Intel gave up when trying to appease to the <=10nm gods, it also means the planet now relies on a SINGLE manufacturer for all of its cutting-edge state-of-the-art integrated circuits: TSMC. Which if you forgot, the T is for TAIWAN, y'know, the country our deal Xinnie the Pooh want to get erased from Earth ASAP. Sure, TSMC is now building a factory in Arizona, but that one won't be coming up online until 2024 at the earliest, which means any asshole move by The Pooh can suddenly cut off the supply of fast Ryzens, cellphone SoCs for iDevices (Apple has bought nearly every single production slot on TSMC's 5nm for late 2020 and most of 2021, so those 5nm Ryzens have to wait), and now, even cheap Core CPUs.

Needless to say, this is Bad™, with a capital B. I can't believe I'm now rooting for Intel to get their shit together again, but TSMC is getting too powerful for its own good. There could be hope at the end of the road, given Intel's current reverse Boeing CEO change, to a former engineer that already knew Intel CPUs down to the transistor (apparently Pat Gelsinger is known as the "father of the 486", and has significative input during the design of the very first Core architecture, which as we can remember, quickly became a game changer). All this guy needs is to re-rail the <10nm train, and stay the hell away from the SJWs outside scandals, and I guess the x86 CPU wars will heat up again, instead of losing ground to heavily locked down ARMs.

Doing <10nm seems to be hard for everybody across the board: it doesn't help that you need EUV for that, a process that is buggier than any recent Ubilol AAA game Cyberpunk 2077, and it also doesn't help that there is a sole OEM in the world for the Very Expensive Lithography Machines you need for EUV (that's the dutch ASML, which has become another strategic target for the nukes). So far here is the situation:

- TSMC: The kings of the hill, except that you can only get their latest cutting-edge chips on crippled appliances by Apple :/ Their 7nm is not bad either - that's where AMD is baking their latest hotness. And they will be the first ones at 3nm!
- Samsung: The only other one that can do production quality 5nm, but not with TSMC volumes. The bulk of their output is reserved for internal use (Exynos, DRAM), and the scraps are already monopolized by nVidia.
- Intel: Jinxed, can't do 10nm at anything but "barely over engineering samples" level, can't do <10nm AT ALL.
- UMC: The best they can do is 14nm. Nobody makes powerful/efficient processors here?
- GlobalFoundries: Officially gave up. Stuck at 14nm forever? Due to contractual reasons (remember: GloFo was the AMD fab arm!), AMD is still obliged to source a percentage of their parts from there, so I guess chipsets and obsolete/garbage-tier APUs.
- SMIC: HAHAHAHAHAHAHAHAHAHAHAHA--wait, is Xinnie The Pooh for real!?--HAHAHAHAHAHAHHAHA! How naive are those CCP cadres, believing they can play with the big boys. Even their souped-up VIA Nano clone, Zhaoxin is fabbed at the enemy, TSMC! Anyway, they're not even at 10nm yet.
- Everybody else: Discounting flash memory dedicated players (Kioxia, SanDisk) which are always a couple nodes behind due to the specific intricacies of flash, the <=10nm club remains a very exclusive one where the cost of entry is impossibly high, so nope, for our effects nobody else exists.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-23, 16:05 in Mozilla, *sigh* (revision 1)
Dinosaur

Post: #892 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Seamonkey 2.53.6 was released just a few hours ago GO GO GO

https://blog.seamonkey-project.org/2021/01/22/seamonkey-2-53-6-has-been-released/
https://www.seamonkey-project.org/releases/seamonkey2.53.6/

Just a few bugfixes (some security patches backported from FF78ESR), and if you live in Greece it's a good time to switch as they now have a Greek (el) locale. And some internal source plumbing changes to align with SM2.57 build tree in order to ease build transition, I guess.

No, we aren't Google WebComponents®™ yet!

UPDATE: The Monorail guys answered to my browser compatiblity ticket!
Unsurprisingly, their answer was basically following the Party lines:
Sorry, this website does require web components support. We aim to support the two latest stable versions of Chrome, Edge, Firefox, and Safari as per our browser support guidelines: https://chromium.googlesource.com/infra/infra/+/master/doc/front_end.md#front_end-development-guidelines

"Go away, you don't exist!"

Welcome to the shitlist, Monorail! Get cozy with other abominations like JIRA (product that you can't own anymore because Atlassian went full-Clown).

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-24, 16:58 in Mozilla, *sigh* (revision 5)
Dinosaur

Post: #893 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
For those out there that don't get what is this "Web Components" thing, here is a quick introduction detailing all you need to know about this new shiny hotness:
https://www.soubai.me/post/whats-the-heck-is-web-components
Wikipedia page is quite barebones: https://en.wikipedia.org/wiki/Web_Components

Basically it allows webshits webdevs to define custom HTML tags client-side, unlike the usual (and IMHO proper) way to do it, that is, server-side (relying on your framework to generate the corresponding HTML: a good example is JavaServer Faces custom components). It also allows the dev to define templates you can use at runtime (again: something every half-decent server-side framework had for decades). Oh, and it relies heavily on client-side JavaScript to do the Magic™, because that's the only language that matters in the web community these days.

Custom client-side HTML tags components aren't even new: Microsoft has prior art on this, but of course that went nowhere as it dates back to the dark ages of the Trident monoculture (IE5.5!). Years later, Mozilla tried it with XBL and failed. But they say the third attempt is the good one, and we can thanks this asshole to introduce his version of what we know today as Web Components. Google liked it so much they started investing heavily on it (Polymer being the first popular implementation), and suddenly when Chrome became the new IE, they also forced the W3C to bake Web Components into the (already extremely bloated) standards. But Google WebComponents™® didn't became widespread until the last 2 years, where nearly every webdev under the sun wents pants-on retarded in their dumb chase for shiny. Welcome to the new "server-side", where your computing device is treated as an extension of Someone Else's Backend!

Yes, I'm well aware that the workaround for non-WC-capable browsers is to include MOAR JAVASCRIPT!!!!11!!! the relevant polyfills on demand, but since webshits now assume everybody runs Chrome, noone bothers doing that anymore (because users like me don't exist). This is why GiggityHub breaks horrendously on SeaMonkey and Pale Moon, and what that addon does is to forcefully include the required polyfills to make the thing work, but that only fixes ONE website, while the rest of the Internet is now broken for those that decided not to follow the Way of Chrome (oh, and it also breaks your screen readers! Because blind people doesn't exist either). Embrace, Extend, Extinguish at its finest... and this time we can't even blame Microsoft!

tl;dr: Google WebComponents™® exists because modern webdevs are lazy morons that don't really know what a "server" is anymore :/

UPDATE: I now died inside after reading this repository.
"YO DAWG I herd u liek components so we put web components on your custom components so u can haz components everywhere!"
WHYYYYYYYYYYY?!?!?!?!

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-24, 23:17 in Hardware/Product Recommendations Thread (revision 1)
Dinosaur

Post: #894 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
E-ink by its nature (it's made of opaque material, unlike LCDs which are slabs of semi-transparent glass) doesn't play nice with backlights. Some devices may fake it with creative LED placement, but then that's not backlighting anymore - it's frontlight! More here: https://old.reddit.com/r/arduino/comments/7tdzn8/are_there_any_eink_screens_with_backlight/

Think on e-ink like a good ol' fashioned paper book, because that's what it is, basically.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-27, 19:12 in Computer Hardware News
Dinosaur

Post: #895 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
MOAR INTEL!!!!!1111!ONEELEVEN!!!

The rumoured Intel discrete GPUs (now branded as "Xe Graphics", "Iris Xe", or simply "Xe" are finally finding its way to the market... timidly. But the reality is that it seems Intel is half-assing things, AGAIN:

- The very first Xe parts to hit the market are laptop GPUs, built into ultra-thin soldered-down-everything laptops, like this Acer model.

- Yesterday, Intel announced through its partners the very first desktop PCIe Xe cards, that is, the class of hardware you and me are itching to buy, if only so we can finally say the final "Fuck You nVidia!", and/or ditch the ATi/AMD driver hell (that despite countless improvements in the last decade, the spectre of broken drivers still haunt each and every new generation of Radeons, mainly for those of us running Linux). But there is a catch. Well, several gotchas to be precise:
0) Only low end parts will be available at launch, some of the fanless variety. Might be good picks for those looking to beef up their HTPC setups, but not so much for those seeking for the ultimate GeForce/Radeon killer. OK, I can get behind this: Intel needs to test the waters and whatnot, but this isn't exactly the BANG! the industry has been waiting for...
1) Initial parts are destined to "system integrators", so basically only for prebuilts/OEM, not for the retail market!
2) In what I would call a incredible act of self-sabotage from Intel, said cards will only work with "select CPUs and motherboards". Some Sekret UEFI Sauce™ is also required for enabling support for Xe GPUs - basically, Intel doesn't want YOU using these babies on anything other but 9th/10th gen genuine Intel Core CPUs, which is outrageous when you consider that you can take a Radeon (made by a company that also makes x86 CPUs no less!) and put it on nearly everything with a PCIe slot!
3) Even if you're willing to give more money to Intel on a blessed CPU/GPU/mobo trinity, the Linux support (which is usually great if not stellar at launch day) is kinda unusable right now, on many fronts.

Hopefully we're watching an overly cautious (if kinda ill-conceived) launch strategy, and not the born of another overhyped i740 fiasco. But at least this time we are getting something, instead of the broken promises of the sad story known as "Larrabee" :/

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-27, 20:26 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs) (revision 2)
Dinosaur

Post: #896 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
How to enable SSH X11 forwrding, 2021 edition.

You need to do this:
#/etc/ssh/sshd_config
# ...blah blah blah...
X11Forwading yes
X11DisplayOffset 10
X11UseLocalhost no # the commented default is "yes"!
# ...blah blah blah...

Restart sshd on the host (restarting sshd over SSH is quite the chicken-and-egg solution, so the easiest way is to reboot the remote host if you don't have physical access), then "ssh -X user@host" will work, despite the insistence of those newfangled nerds to exorcise X11 because it's OOOOOOOOOOLD, DANGER MINES UNSAFE!!!, and Wayland is going to save us tomorrow, for real this time!.

For extra scariness level: say you need to run some remote X11 app with superuser privileges (before you scream "DON'T DO IIIIIIT!!!!", for a legit case I've got this):

sudo xauth add $(xauth -f ~/.Xauthority list|tail -1)


Older distros didn't required to do any of this (except maybe for the xauth bit?), but we're living in horrible times so I've already went through that pain for you. You're welcome~

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-28, 02:51 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs) (revision 1)
Dinosaur

Post: #897 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Access Denied
You don't have permission to access "http://download.virtualbox.org/errors/otnembargoed.html" on this server.

Reference #18.4f7b0660.whatever.meh


The time to get my shit off Orrible® VirtualBox has come.

WTF, even the "Your shithole is embargoed" error is embargoed to me!

[GAH!Politics]The Angry Cheeto is gone, but his legacy persists. And I guess that the new Democ-rat at charge will change nothing because all USAian presidents are the same garbage who can do nothing but token acts that only screw up everthing. And due to such fucking useless token efforts, Maduro is still a murderer dictator that will not go away anytime soon, yet I -the poor lowlife scum- end paying the price. Can't the planet just implode already!?[/GAH!Politics]

Any libvirt/QEMU-for-dummies guide I can follow to migrate my stuff, pretty please?

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-01-31, 03:01 in (Mis)adventures on Debian ((old)stable|testing|aghmyballs) (revision 5)
Dinosaur

Post: #898 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
pgAdmin III got booted off Debian sometime last year

This is because it has been abandoned upstream years ago, and it has already been unusable with PostgreSQL versions later than 9.6 (Buster ships with PostgreSQL 11, current version is 13). Their intended replacement? You've guessed it: pgAdmin 4, which is some unusable webshit abomination for Silly Valley's most beloved OS: Google Chrome web browsers! It's slow, bloated, SLOW, broken, hides essential info (like pg_dump/pg_restore logs which are often eaten by a grue) behind its flashy dashboard that it's SLOW AND BROKEN, and it even suffers of the Electron pandemic on its "desktop" version (as it is nothing but yet another Chrome-in-a-can™ webshit, ready to assrape your CPU cores and eat all of your RAM before breakfast). Even worse: when they initially released pgAdmin 4, they never came up with a plan to sunset pgAdmin III (something sensible would have been develop both in parallel until the newest shiny reached feature parity with the old stale, while maintaining the latter to add basic compatibility with new server versions until a date set in stone). Instead... they quickly killed pgAdmin III after releasing the first 4.x versions (which were even less usable than the current ones!), following the latest UX trends (does that remind you of someone? Like a certain desktop environment whose UI toolkit was formerly developed by a now former cellphone maker...)

Yes, I've tried to embrace pgAdmin 4. As expected, it didn't worked for me. When you have your tools actively getting in the way, you know it's the time to look somewhere else. But with regards to PostgreSQL GUI-based management tools, your options are... not great:

0) pgAdmin is the official management tool, endorsed and developed upstream. But while pgAdmin III was a lightweight TRUE desktop application that rarely got into your way, pgAdmin 4 seems to be designed to be as obnoxiously unusable as possible.
1) There are other bigger, badder and better GUI tools, but none of them are FOSS, can cost some good money (which you're expected to pay if you are a professional developer making a living out of PostgreSQL, it's the fair thing to do... but not an option for inhabitants of communist countries, hobbyists, or FOSS purists)
2) Use Access/LibreOffice... as long as you stick only to tables and nothing else. Forget about messing with stored procedures, triggers, views, or any of the cool features for big boys. Like being able to backup your database, or maintain it. Been there, quickly ran away as soon as Office ate my first table relationship, never got the T-shirt.
3) Be a Troo UNIX® Way caveman, forget about GUIs, and do everything through the console. While having some CLI skills can save your life every now and then, expecting to become a 24x7 CLI freak is my idea of "oh fucking hell NOPE!".
4) Resist. There is still hope for having sane, free tools. You've got the code for that, amirite?

You guys knew what option I'm picking on this one. Luckily for dinosaurs like me, I wasn't alone back then: while some randos out there figured out what patches were required to bring pgAdmin III in compliance with PG10+, one of the PostgreSQL "partners" releasing commercially-supported versions, OpenSCG (now part of the Jeff Bezos' empire of doom) realized that while the fate was already set on stone for III, the way upstream handled it was a dick move, so instead they moved to implement their own gradual phaseout, and their custom PGSQL distro (under the "BigSQL" brand) was born, complete with their own fork of pgAdmin III. They never made standalone Linux versions of the latter, so for years I was using a hackjob of Debian's final pgAdmin III packages with some shoddy patches that somehow managed to not break things that much (my database only have 50 stored procs, not over 1000!)

Fast forward to yesterday, where I finally got fed up of navigating into a list of hundreds of sprocs that are not mine and decided to take a look of what happened with good ol' pgAdmin III. While BigSQL is no more (although their GiggityHub is still active, but as expected their pgAdmin3-lts repo has been archived since 2017), the legacy lives on, and other dinosaurs are still keeping the flame alive. I found this fork of pgAdmin3-lts which brings things in sync up to PG13.1, and seems to work fine in my end. No more system sprocs littering my schema listings! No more mysterious error messages about some pg_internalvomit aborting all and any attempts to view a table! And best of all, NO FUCKING WEB BROWSER REQUIRED!

But... I don't want it living as a mess of files stashed at either /usr/local or /opt. I need it integrated with my desktop. I need a Debian package. Long short story: here is how you can bake your very own pgAdmin3-lts Debian packages at home (WARNING: it's not the Debian Way®, but pretty close, and more patchy than poor ol' Patchouli Knowledge, but it Works For Me™):

1) Clone AbdulYadi's repo. Make a tarball of it, just in case you screw up something.

2) Get Debian's pgAdmin3 source package. You really only need pgadmin3_1.22.2-5.debian.tar.xz, but if unsure, just get all three files, put them on a new directory somewhere, and dpkg-source -x pgadmin3_1.22.2-5.dsc - we only want the /debian directory, which contains the recipe to build the .DEBs.

3) On the pgAdmin3-lts sources dir, run ./bootstrap, to invoke some mandatory arcane autotools dance which usually already has been done on release tarballs, but not on code freshly cloned from trunk/master. Neglect this, and the build will die with mysterious errors at first, followed by "can't find branding/Makefile.in" on subsequent attempts.

4) Copy the /debian directory from Debian's pgAdmim3 sources into pgAdmin3-lts sources (you can throw away the rest of the source tree). We can't use it as-is - we need to fix some stuff before attempting a build. In order:
- 4.1) Go into /debian/patches and delete pg10 and pgversion patches (they aren't needed anymore, and will break the build!). Don't forget to edit series to remove those from the patch sequence too!
- 4.2) There is a README that it's now README.md - that one will go into the pgadmin3-data package, so we must fix that or our build will die somewhere at 98%. Edit /debian/pgadmin3-data.docs and add the fancy .md extension to README there.
- 4.3) Since this technically is the unreleased pgAdmin III 1.23 version, we need to set that too on the package to not conflict with the Debian version. This is (kinda counterintuitively) defined on /debian/changelog, which has a very specific format for that. Here is how mine looks now:

pgadmin3 (1.23.0-1) UNRELEASED; urgency=high

* Non-maintainer upload.
* Switched to patched pgAdmin3 LTS by BigSQL.
* Added compatibility with PostgreSQL 10-13.
* Post-BigSQL compatibility patches from AbdulYadi/pgadmin3.

-- Tom Maneiro <tomman@himawari.tomman.net.ve> Sat, 30 Jan 2021 13:44:00 -0400

pgadmin3 (1.22.2-5) unstable; urgency=medium

* Mark pgadmin3-data Multi-Arch: foreign.
* Remove obsolete Build-Depends on devscripts.
* Move maintainer address to team+postgresql@tracker.debian.org.

-- Christoph Berg <christoph.berg@credativ.de> Wed, 06 Feb 2019 15:48:33 +0100
...snip...

I'm sure Debian packaging toolchain has a tool or two to automate that. I don't care. I just obey the format and don't get into troubles, so you do too!

5) We're ready to go! Ensure you've got installed all of the required build dependencies (libwxgtk3.0-dev being the main one, and yes, pgAdmin III still relies on the good ol' GTK+2 :), and invoke the build: dpkg-buildpackage -b -us -uc -tc -j4. Those switches are for the following:
-b: Build binary packages only. We need that one because we don't have a true Debian source package anymore, and omitting it would cause dpkg-buildpackage to bitch and refuse to build from a source tarball that doesn't exist!
-us, -uc: Do not sign sources/changelogs/whatever. Omit those and your build may abort at the end for some stupid reason regarding digital signatures you don't have (and don't want)
-tc: Cleans the source tree after build, to not leave hundreds of megabyte of temporary object code junk lying around your filesystem!
-j4: Adjust this for the number of cores/threads your computer has.

6) Go eat something, water the plants, walk the dog, play something on your other PC - surprisingly, building pgAdmin III is a very taxing process: on my i5-2450M it takes over 30 minutes!

7) You should now have 3 .DEBs outside the sources tree dir (alongside some other bunch of noise): pgadmin3, pgadmin3-data, and pgadmin3-dbgsym (this one can be safely ignored, unless you want to be able to debug crashes). Install them and enjoy one of the last bastions of sanity on desktop database management GUI tools!

As for Debian and pgAdmin 4... that's just not happening anytime soon, due to the culture clash between old-school conservative distros like Debian (where every dependency has to be a package, and bundled libraries are a serious no-no) and the new kids on the block, the JavaScript Frat Boys (where everything is a moving target and they would put their mothers inside a Docker container if they could do so!). Yes, you've heard it from me first: current and next Debian releases have absolutely NO usable PostgreSQL GUI management tools! (Buster has a very broken pgAdmin 3 which doesn't really work with its companion PostgreSQL release, while Bullseye has NOTHING AT ALL) Progress!

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-02-02, 21:03 in I have yet to have never seen it all.
Dinosaur

Post: #899 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
A Problem For Days: Blocked Toilets On A Boeing 787 Dreamliner
(All you need to know about toilets on airplanes: https://simpleflying.com/aircraft-toilets-2/ )

Taking a dump on an airplane is Serious Business™. Sadly for us, you can't call your favorite fat Italian plumber to unclog the toilet on a $300M jet.

Reminds me when the Mythbusters debunked the myth when airplane toilets could suck your ass and your brains out of the plane.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Posted on 21-02-05, 14:44 in Computer Hardware News
Dinosaur

Post: #900 of 1318
Since: 10-30-18

Last post: 9 days
Last view: 2 hours
Oh man, the semiconductor shortages shitshow keeps going on.

It's not only Apple still hogging hi-end production lines at TSMC leaving no room for AMD to grow while nVidia fights for scraps at Samsung, and certainly Intel giving up with <10nm doesn't really help. The AMD head says shortages will continue for the first half of 2021, so getting a next-gen console or even a new CPU or GPU will be tough for months to come (and unfortunately scalpers only are making things worse).

But this mess is also starting to cripple other critical industries, like automobiles. And if you're in the market for new expensive audio gear... we just got the classic "factory burned down, expect shortages" straight from Japan's AKM (which might be already present inside at least one of your electronics, as they make DAC/ADCs by the truckload).

2021 already has the potential to be even worse than 2020 for everybody around the world, no matter where you are.

Licensed Pirate® since 2006, 100% Buttcoin™-free, enemy of All Things JavaScript™
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
    Main » tomman » List of posts
    This does not actually go there and I regret nothing.