Hacker News: Joel_Mckay

New comment by Joel_Mckay in "GPT-5.6 Sol Pricing Cut by 50%"

Joel_Mckay — Tue, 18 Aug 2026 06:23:06 +0000

The e-waste recyclers are pretty low on the pecking order, as the creditors will be first to strip these places for assets as Leopold Aschenbrenner discovered. =3

New comment by Joel_Mckay in "GPT-5.6 Sol Pricing Cut by 50%"

Joel_Mckay — Tue, 18 Aug 2026 06:19:16 +0000

Won't have to wait very long... as they are eating their own already.

https://www.youtube.com/watch?v=rE75WvOtcu8

The Shrek movie market correction correlation may be due again in July 2027. =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Tue, 18 Aug 2026 05:05:48 +0000

Ok, if YT pays $1k to $8k for 1m views, and has a minimum $100 check payout.

Than that is approximately 100k to 12.5k views to see even $100.

That exposure incurs around a 1% psychopathy rate for approximately 125 to 1000 users that would have no problem stealing your stuff.

I find it unbelievable people would actually sign up for that experience. =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Tue, 18 Aug 2026 01:35:46 +0000

Don't worry about it... =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Tue, 18 Aug 2026 00:47:04 +0000

Would unlikely do YT content unless I needed a cheap video CDN or RTMP service.

Do people still make actual money competing with Slop clips? I wonder how often Alphabet actually cuts a meaningful check for long-tail content. =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Mon, 17 Aug 2026 18:15:06 +0000

Sealioning will not help folks either. Best of luck. =3

https://en.wikipedia.org/wiki/Sealioning

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Mon, 17 Aug 2026 18:01:06 +0000

Maybe, a rickety stack of volunteers relying on uncoordinated hobby projects may have regression tested coding standards above a multi-billion dollar market-cap corporation.

Or... is relying on installation obscurity for security theater.

Both options are likely to have kernel and other exploits published. A disposable phone for traveling into hostile territory is still recommended. =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Mon, 17 Aug 2026 06:40:54 +0000

There are companies that are specialized in cracking phone logins with unpublished zero-click $370/unit product exploits. An LLM will not help you kid.

Also the joke meme: https://xkcd.com/538/

The only indication of a remote-compromised system is apparently a slight drop in battery life, and higher than normal background data. Privacy is dead. =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Mon, 17 Aug 2026 05:31:33 +0000

Every iPhone and Android device can be cloned in a few minutes with physical access. Others with standard base-band cell LTE/G5 modem devices are remote tapped in seconds without user knowledge.

The fact is technology can never fix legal policy, privacy protection, or societal issues. =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Mon, 17 Aug 2026 05:17:07 +0000

Probably meant Alphabet and Facebook ad marketing telemetry service embedding. =3

New comment by Joel_Mckay in "How do I permanently disable random Google Photos popup to backup photos? (2024)"

Joel_Mckay — Mon, 17 Aug 2026 05:13:20 +0000

Currently there is a guy in court for giving a duress-password to border guards. From nuisance to a real problem in 30 seconds. =3

https://www.youtube.com/watch?v=_2rokxux5cU

New comment by Joel_Mckay in "RISC-V: They Should Have Known Better"

Joel_Mckay — Sat, 15 Aug 2026 12:20:17 +0000

Until people admit they made the same mistake as ARM6 fragmenting the architecture focus, its adoption will probably continue to stall under each firms hubris. =3

https://en.wikipedia.org/wiki/Second-system_effect

New comment by Joel_Mckay in "RISC-V: They Should Have Known Better"

Joel_Mckay — Sat, 15 Aug 2026 05:08:54 +0000

Sure, the constellation of features is no longer a general purpose computer in the retail context, but rather an ASIC appliance the ends up incompatible/useless rather quickly.

Maybe Gentoo could tame that level of chaos... or people just buy ARM64 again knowing the software ecosystem already works. =3

New comment by Joel_Mckay in "RISC-V: They Should Have Known Better"

Joel_Mckay — Sat, 15 Aug 2026 00:00:36 +0000

Some are already on RVA23.1 even before the standard made it to more than 4 manufacturers product lines.

The meme joke about standards is sadly relevant for riscv. =3

https://xkcd.com/927/

New comment by Joel_Mckay in "an ambiguity in C89 which will never be fixed"

Joel_Mckay — Fri, 14 Aug 2026 22:41:01 +0000

Indeed, every C compiler including gcc is slightly different. Especially in the embedded space where pseudo-standards become a small subset of GNU compatible code very quickly. To be honest, gcc became the unofficial standard even with the GNU extensions.

Good C follows the 10 rules, uses old compatible macro language features, and is boring to trivially port. The "hold my beer" folks often go back to Python where the abstractions hide the foot-guns.

https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Dev...

New comment by Joel_Mckay in "an ambiguity in C89 which will never be fixed"

Joel_Mckay — Fri, 14 Aug 2026 19:54:43 +0000

It had to do with the lack of helpful warning/error messages while porting over a C project. Switching out for libstdc++ was helpful in narrowing the scope of where to look for the issue, and a better idea of the failure mode.

Given the Sealioning problem on YC, trying to remember an edge case issue from years ago would not go well. If your work habits aren't pushing into the compiler standards gray areas, than one probably won't ever encounter such issues. ymmv =3

https://www.youtube.com/watch?v=T4Upf_B9RLQ

New comment by Joel_Mckay in "an ambiguity in C89 which will never be fixed"

Joel_Mckay — Fri, 14 Aug 2026 16:28:13 +0000

The key logical jump here is "should", but in practice standards compliant C may still behave in unintuitive ways in edge-cases. It is not a compiler "bug" if functioning as defined, but rather a self-discipline issue to avoid shitty coding practices. =3

New comment by Joel_Mckay in "an ambiguity in C89 which will never be fixed"

Joel_Mckay — Fri, 14 Aug 2026 07:51:55 +0000

Google Gemini? =3

https://www.youtube.com/watch?v=X6WHBO_Qc-Q

New comment by Joel_Mckay in "an ambiguity in C89 which will never be fixed"

Joel_Mckay — Fri, 14 Aug 2026 07:38:29 +0000

The 'g++ -x c ...' will parse portable source just fine (compiles code as C, but links against libstdc++), and tends to identify poorly structured code with verbose checks. If people default to gcc file extension inference, than it is likely to remain silent when people do something silly.

Best of luck, =3

https://www.man7.org/linux/man-pages/man1/g++.1.html

New comment by Joel_Mckay in "an ambiguity in C89 which will never be fixed"

Joel_Mckay — Fri, 14 Aug 2026 04:19:41 +0000

Most people build C in g++ before gcc, as it tends to have a better chance of catching most oddities. Then run it past valgrind to double check if something looks suspect or is slowly leaking. =3