3np

You already have .internal reserved, you know?

The entire thread:

>>> This is a fuzzy recollection of something I believe I read, which might well be inaccurate, and for which I can find no corroboration. I mention it solely because it might spark memories from someone who actually knows:

>>> A company used 192.168.x.x example addresses in some early documentation. A number of people followed the manual literally when setting up their internal networks. As a result, it was already being used on a rather large number of private networks anyway, so it was selected when the RFC 1597 was adopted.

>> sun

> Wasn't 192.9.200.x Sun's example network?

of course you are correct. sorry. jet lag and not enough coffee.

---

So no answers.

Upstream reporting: https://www.nytimes.com/2025/09/05/us/navy-seal-north-korea-...

Remote send/recv can be frustrating due to the need for root.

It can be helpful to remember that while less efficient, for scenarios where ssh as root is a no-go you can ship snapshot syncs (including incremental ones) as files:

    zfs send [...] tank > tank.zfssnap
    cat tank.zfssnap | zfs recv [...] bank

- Classic centralized social media with no story around decentralization or federation

- First-class experience only via walled and gated Google Play and Apple Appstore. They brand as "human first" but it's unclear if it will even be available/supported outside of human-hostile platforms. Looks pretty "corporate first".

- No public API

- No source

- External presence exclusively on: Twitter, Instagram, Youtube, Tiktok

- https://docs.digg.com/privacy

- https://docs.digg.com/terms

Hard pass. The only possibly attractive thing would be the name.

Looks neat but wish it wasn't sending user data to Google Analytics of all places.

GitHub Support tickets are private and not publically sharable.

I did mention it in this Discussions thread a while back (which the support agent at one point in July hilariously linked me to asking if I had read, making it clear they hadn't done so themselves).

https://github.com/orgs/community/discussions/147437#discuss...

Initial support response mentioned here:

https://github.com/orgs/community/discussions/147437#discuss...

It's been normalized already for, idk, a decade or two?

Humans gonna human.

Not near an account right now but literally just "View Source" when signed in and search for "copilot" and it's there along some other feature-flags for the user in a JSON blob inside a script tag.

I've had an ongoing support ticket with GH for several months now asking them to actually disable Copilot, as there is Copilot all over and it's clear from inlined JSON on github.com pages when signed in that my account is actually opted in to Copilot features despite Settings page saying features should be disabled. I've never ever opted in to anything related to GH AI and am not a vscode user.

They keep closing the ticket and saying it's "with the engineering team". I keep reopening and asking for resolution, escalation, or progress.

GitHub did have working and professional support in the past but in 2025 they are just malicious.

It's surreal.

> Not sure why this is getting down votes

Guessing unrelated to the comment itself, prolly got a minor downvote army on my back after a different recent comment on Gaza matters.

Downvotes are just a noisy signal in general and I wouldn't read that much into a few here and there, it comes with the territory.

Oh and yeah, this meta makes for tedious threads so site guidelines and all that.

I imagine coverage is sparse enough to not be worth it.

Building the software you rely on from source by default is one way to reduce the impact these events have on you and shift the power dynamic. If you're installing binaries/images from a vendor (free or otherwise), transitioning to a fork may be an undertaking and a sweaty risk-assessment.

Switching your existing build-infra to sync sources from a new remote should be a snap.

Also no major need to hound maintainers to ship a release or merge that neglected bugfix or feature you desperately need - just cherry-pick it.

Not the first time Israel bombs a hospital with large casualties in order to kill journalists. They've being quite brazen about it, too.

https://www.reuters.com/world/middle-east/israeli-strike-gaz...

https://www.thejournal.ie/israel-strikes-gaza-hospital-killi...

Part of a pattern.

https://www.ohchr.org/en/press-releases/2024/12/pattern-isra...

Perverse incentives. I don't think education should be optimized for future financial profitability of the student.

In very specific and rare circumstances (like your PG example) it can make sense for post-grad adults.

Reminds me of Meta mobile data partnerships in Myanmar. Same arguments and similar playbook. That did not go well for people in Myanmar.

https://erinkissane.com/meta-in-myanmar-full-series

I suppose it doesn't run 100% locally? Where's the privacy policy? Also your "Support" link is broken.

What an utterly pointless and disrespectful NPR article. She's 80. Give her some grace and don't run this story with all the personal details while she's alive?

Sloppy reporting: The LeMonde link 404s, the "BBC" link as actually to Yahoo News and why bother to include a reference to the Wikipedia page about Paris zoning but not the original reporting of the incident?

If what you are saying is true, you can not trust Microsoft, Apple, Google, Meta (and especialluly including whichever service you say related accounts keep popping up at)... Avoid them. Avoid giving them any more of your personal information and metadata.

Anything beyond that is probably related to your IP address being tracked (so change internet provider to get a fresh start there and if you currently use a VPN: switch or stop).

Dispose of all devices and abandon the accounts. Maybe save some for evidence and but do NOT turn them on or use them again. Get new devices. Starting from scratch is the only way to be sure.

If this is not satire you really need to take the name back to the drawing board...

This line of thinking is increasing and dangerous (and no doubt intentional from at least some of the popular examples that come to mimd). It will make it that much harder for authentic candidates to talk about legitimate change and ideology.

Presumably the ISPs and vendors will be forced to block you/Proton there via regular means, so no.

NSMB source code never leaked, or did I miss something?

So assuming they're looking at a decompiled ROM, the actual sources probably look completely different so it's pretty inane to complain about ugly loops and lookups and hardcoded numbers.

The weird looping in the beginning might as well be an attempt at obfuscation meant precisely to annoy and distract readers like OP. Or if it's an artefact of some dev/debug feature left in the build: Big deal, really got them there.

Entropy is what matters, not length. OP gets this part right.

"qwertyuiopasdfghjkl" or "aaaaaaaaaaaaaaaaaabc" are not stronger than "kmY7$®f0V".

I did get that mixed up, thanks for correcting.

Also https://valkey.io/topics/history/

Today? Use their .onion address[0] over Tor and TLS. The TLS certificate is secured by the tor secret service key. No WebPKI or centralized CAs required.

For tomorrow we should keep exploring and adopting improvements. Pick your poison.

[0]: Discovery left as excercise for reader

Somehow it feels like this is more about data derived from payments and the license system than actual revenue. It could have been $0 (but still charged) if it weren't for optics.