binaryturtle

Pixels. You can watch it as video (some old-school animated "QR Code" type of stuff :) )

I still have some old Amiga backups on VHS. Worked too… :)

Why do you need to send a password when using their Autodiscover API? Would Outlook send the respective passwords for each email account to Microsoft?

Stunnel is an important part of my setup here.

Back when Apple's Mail on a more outdated OS X setup stopped to be able to connect to various mail servers because of Apple's own outdated SSL/TLS implementation (security.framework?) I just plugged stunnel in the middle to make things work again: Mail connects to localhost and stunnel then safely connects to the remote mail server.

While this was an important fix at that time it also provided surprisingly additional benefits. Now it was much easier to entirely block outgoing connections from Mail with Little Snitch. Instead having numerous allow directives per mailserver, just one full block. E.g. no more random config changes that break everything, because Apple decided to push some auto-config changes for well-known mail providers. No more accidental tracking pixel triggers. Also all the accounts are now just vanilla POP3/SMTP accounts rather than those with "special handling". Finally Mail became much more stable for some reason. No more long lockups when I want to open the Account settings, no more random lockups when launching the app, etc.

Now I really do not want to miss this extra layer anymore because all the bonus benefits (even if it shouldn't be needed any longer just to make SSL/TLS work again).

Over time bunch of other things (Mail unrelated) got plugged into the stunnel config too. :)

This is an older Firefox, so this is probably all "normal", but also may be entirely unrelated to the actual cause for nothing showing up?

    WebGL warning: drawArraysInstanced: Framebuffer not complete. (status: 0x8cd6) COLOR_ATTACHMENT0: Attachment has no width or height. ascii_clouds.astro_astro_type_script_index_0_lang.iEVYfoCC.js:274:3430
    WebGL warning: drawArraysInstanced: Framebuffer must be complete. ascii_clouds.astro_astro_type_script_index_0_lang.iEVYfoCC.js:274:3430
    WebGL warning: drawArraysInstanced: TEXTURE_2D at unit 0 is incomplete: The dimensions of `level_base` are not all positive. ascii_clouds.astro_astro_type_script_index_0_lang.iEVYfoCC.js:274:3980
    …
    [repeat]
    …
    WebGL: No further warnings will be reported for this WebGL context. (already reported 32 warnings) ascii_clouds.astro_astro_type_script_index_0_lang.iEVYfoCC.js:274:3430

It dies with lots of WebGL errors here, so I only see a white page. So that's definitely not ASCII in my book. Would be more fun to have an actual text based output indeed.

Sometimes hundreds per day. Tabs come and go here. People have different workflows.

Yesterday just shy over 50, according to entries from `login` in the system log.

I do launch multiple interpreters just to get a fancy coloful cowsay on each launch. Which involves the fortune program, lolcat (via ruby) and cowsay itself (via Perl). I probably should optimise that into a single C binary for better startup times! :)

Outch… and I though an ~8KB "Hello, World!" here on my rusty Mac is HUGE already.

Just look at Japanese television… most channels get broadcast at 1440x1080i for 16:9 content instead the full 1920x1080i (to save bandwidth for other things, I assume), so it's still very common with HD too.

A square pixel has a 1:1 aspect ratio (width is the same as the height). Any other rectangular pixel with widths different than their heights would be considered "non-square".

F.ex. in case of a "4:3 720x480" frame… a quick test: 720/4=180 and 480/3=160… 180 vs. 160… different results… which means the pixels for this frame are not square, just rectangular. Alternatively 720/480 vs. 4/3 works too, of course.

"Bins"? :)

IMHO it's very misleading to claim that some LLM wrote all the code, if it's just a compression of thousands of peoples' codes that lead to this very LLM even having something to output.

I fully agree. It's not only the waste of time when you have to confirm you're a human (that adds up to multiple hours per month).

It's also the entire blockage of older or less mainstream systems that no longer can access, sometimes critical, websites at all when the Cloudflare check blocks things entirely because the "browser is out of date" or not on their whitelist. Therefore causing excessive discrimination of poorer folks that can't afford upgrading to never/ other systems that still are legible to pass Cloudflare's "grace".

The simple website doesn't work. Everything seems to be driven by incompatible/broken JavaScript, even what should be straight simple links. I'm too lazy to fire up Chromium to find out if it works there.

That requirements.txt is HUGE.

In my experience the small projects with actual volunteers have no trouble helping out here. They are happy to accept a patch too, f.ex.

It's the big "open source" projects with company backing (or other larger organisational structures) behind them which supposedly have a lot of "volunteers" (probably some paid folks, and IMHO lots of people that just slave away for free for someone else's gain) that often have trouble keeping 3 or 4 code lines for backwards compatibility.

I wrote hundreds of GitHub issues, send in patches too, etc., and most discrimination you get is from the bigger projects (not saying this is the case for Rust here; I simply haven't managed to get Rust going at all, so I couldn't even report an issue or send in a patch to fix something.) I do not use the term "discrimination" lightly either. Not everyone can afford to buy new hardware when Apple decides to abandon specific machines, often w/o true technical need (see OpenCore which proves this point). So this is essentially a discrimination of a poor minority.

For "infrastructure" projects like Rust and Go where a lot of other projects depend upon I generally would prefer a more conservative approach here, which doesn't seem to happen for some reason or another… "for the sake of 'progress'", I guess.

I got my AdSense account disabled because "fraudulent click activity" or how they worded it (someone clicked my ads frequently, I assume?). Google then kept all the my hard earned 16++ EUR or so.

I'm on a slightly older version than 10.12. I'm out of this limited support range. The problem is that as soon Apple cuts off older systems by heavy force all of the Mac developers running in circles like lemmings and cut off their projects from the older versions too: feeding right into Apple's policy to deprecate older systems for their own greed.

For comparison… I have zero problems bootstrapping a recent gcc with all bells and whistles on my setup. I probably even could bootstrap it still on my even older G4 Mac with 10.6.

But so called "modern" language compilers like Rust of Go… no luck. There's a slight hope for the gcc rust support someday, I guess.

I stopped scrobbling many years ago when they messed together my top artist at the time (the lovely "alan", spelled with all small letters) with other entirely unrelated artists by the same name (but with different letter case, e.g. some "Alan" this, and some "Alan" that.) It didn't represent at all what I was actually listening to, so what was the point?

For those who get blocked by gnu.org with a 403 (older Firefox) or an even sillier "Too Many Requests" error (older Safari) need to override their user agents strings to "curl" to make the site load again.

Doubtful. I can't even get Rust to work here on my slightly older Mac system. So with TOR switching away from a well supported language like C it's simple another project lost to me (unlikely you can stick with an older version for long in this case as they regularly break backwards compatibility in their network.)

I'm not even from the UK (EU here).

The following is what I'm seeing exactly, and because it still happens it seems deliberate, not a temporary issue where I was "snake-joking" about earlier. Well… no cute snakes for me.

--- Error 403 Forbidden

Forbidden Error 54113

Details: cache-fra-etou8220097-FRA 1765473610 1384447547

Varnish cache server

"Error 403 Forbidden"

I guess that's this new UK laws in effect? How can I prove I'm old enough to watch some giant snakes? :)

The PAL release is already the bad copy (starting with season 4 I think). You already had odd stuff in view that wasn't supposed to be visible.

The only way to watch this show properly now is the 4:3 NTSC DVD release.

I think the recent streaming releases also have the music altered in many places. The show just got <bleep>ed up basically. It's a real shame.

I wonder too. I don't trust SSDs/ flash for my archives, hence I'm stuck on max. 18TB drives atm.

A browser basically is like a really dumb trojan, pulling a whole herd of wooden horses into the city.

It still matters when you try to keep your components truly portable (aka you're not just targeting the big 3).

And here I'm still trying to get an up-to.date Rust running on my outdated OS X (10.10). No luck (though I may not try hard enough).

There are (older) OSes where this is NOT the case. Leaving things un-freed would leak memory after the application has terminated.

Doesn't load here at all, I had to change my User-Agent to "curl".