HN user

zacwest

1,617 karma

https://zacwe.st

zacwest@^^domain^^

Posts50
Comments109
View on HN
domainincite.com 2mo ago

Verisign to delete .name 3LDs and email addresses

zacwest
5pts1
domainincite.com 2mo ago

2026 new gTLD round has opened

zacwest
2pts0
lwn.net 3mo ago

A more efficient implementation of Shor's algorithm

zacwest
16pts0
cacm.acm.org 4mo ago

A decade of Docker containers

zacwest
366pts260
datatracker.ietf.org 4mo ago

IPv6-Mostly Networks: Deployment and Operations Considerations

zacwest
7pts1
cacm.acm.org 11mo ago

Understanding Mobile App Reviews to Guide Misuse Audits

zacwest
2pts0
domainincite.com 1y ago

.free, .hot, .spot domains to arrive as Amazon reveals gTLD launches

zacwest
13pts2
domainincite.com 1y ago

ICANN is to ban new gTLD applicants from paying each other off

zacwest
4pts0
circleid.com 2y ago

Does Renewing a Domain Name Count as "Registering" a Domain Name Under the ACPA?

zacwest
2pts0
domainincite.com 2y ago

ICANN insists it is working on linkification

zacwest
1pts1
www.icann.org 2y ago

Proposed top-level domain string for private use: ".internal"

zacwest
323pts229
circleid.com 2y ago

Universal Acceptance Issues with .TUBE, ASCII and IDN Domains

zacwest
9pts3
circleid.com 3y ago

50 Years of Ethernet

zacwest
2pts0
domainincite.com 3y ago

Verisign WILL get .web, ICANN rules

zacwest
2pts1
domainincite.com 3y ago

Google to Drop Eight New GTLDs

zacwest
31pts12
circleid.com 3y ago

Verisign’s Role in Securing the DNS Through Key Signing Ceremonies

zacwest
1pts1
circleid.com 3y ago

AFRINIC “In a Bad Situation”, Has Not Been Able to Constitute Board; Has No CEO

zacwest
43pts7
domainincite.com 3y ago

Verisign Loses Prestige .Gov Contract to Cloudflare

zacwest
3pts1
stablediffusionlitigation.com 3y ago

We’ve filed a law­suit chal­leng­ing Sta­ble Dif­fu­sion

zacwest
208pts461
circleid.com 3y ago

Removal of Price Caps for .ORG and .INFO Found Improper by IRP

zacwest
60pts5
blogs.fangraphs.com 3y ago

Effectively Wild Episode 1932: The Best of Baseball Twitter

zacwest
1pts0
arstechnica.com 3y ago

Cable company’s accidental email to rival discusses plan to block competition

zacwest
6pts0
circleid.com 3y ago

Achieving Multi-Stakeholder Progress on DNS Abuse

zacwest
2pts0
domainincite.com 3y ago

ICANN to “Stand Up” to Russia at the ITU

zacwest
1pts0
www.internetgovernance.org 3y ago

ICANN’s Accountability and Transparency: A Retrospective on the IANA Transition

zacwest
2pts0
www.sfchronicle.com 3y ago

How landline telephones became a must-have in old San Francisco

zacwest
2pts0
cacm.acm.org 3y ago

The Road to 6G

zacwest
4pts0
matthewbutterick.com 3y ago

Power, Corruption and Lies (or how I became a typographer, pt. 1)

zacwest
2pts0
www.techdirt.com 3y ago

New Jersey Cops Are Using DNA Drawn from Newborns in Criminal Investigations

zacwest
28pts1
circleid.com 3y ago

How Safe Is Your Fiber Network?

zacwest
2pts0

The historic information in here was really interesting, and a great example of an article rapidly expanding in scope and detail. How they combatted corporate IT “security” software by pretending to be a VPN is quite unexpected.

If you want to get location accuracy lower than 500m without significantly impacting battery life, you can use region monitoring. There's two paths:

1. Set up a region around the user's current location. If they exit it, note the location and set up another one around that location. This will give you around 100m accuracy, which is the minimum diameter of the monitored region.

2. Set up regions in various cardinal directions that nearly-or-just-barely overlap. If they enter one of those regions, note the location and set up another set around the current location. This can give you something closer to 50m accuracy.

For (2), this is how I did it in the Home Assistant iOS app, largely for zones that people wish to monitor which are smaller than 100m. You can find some of the annoying math here[1] (and there's tests all over for it), the logic for setting up regions here[2], and computing them here[3].

[1] https://github.com/home-assistant/iOS/blob/master/Sources/Sh... [2]: https://github.com/home-assistant/iOS/tree/master/Sources/Ap... [3]: https://github.com/home-assistant/iOS/blob/2dfbe3c0e52a30417...

You then use `restic` telling it to use rclone like...

    restic ... --option=rclone.program="ssh -i <identity> user@host" --repo=rclone:
which has it use the rclone backend over ssh.

I've been doing this on rsync.net since at least February; works great!

These are the changes that Apple was forced to make, specifically referencing 3.1.3 (Other Purchase Methods) and 3.1.3(a) (“Reader” Apps):

3.1.3: The prohibition on encouraging users to use a purchasing method other than in-app purchase does not apply on the United States storefront.

3.1.3(a): The External Link Account entitlement is not required for apps on the United States storefront to include buttons, external links, or other calls to action.

The bit about the (formerly required in the US) entitlement is:

Reader app developers may apply for the External Link Account Entitlement to provide an informational link in their app to a web site the developer owns or maintains responsibility for in order to create or manage an account.

They required you use a trackingless, generic URL that was unvarying per user, so you probably didn't run into it super often. Offhand, the Kobo app did use it.

Facebook never federated so their implementation was just an API they couldn't control to them:

Facebook Messages are evolving to allow people to share rich content beyond text: photos, videos, audio and even stickers. We want to ensure the best possible send and receive experience where all these rich forms of content are reliably and consistently available on every platform. XMPP doesn't support all these (and future) content types, and it's difficult to ensure an XMPP client is rendering them appropriately. As such we've decided to sunset the XMPP Chat API.

Fish is such a great shell. More often than not it reads my mind about what to do (e.g. with its fantastic history autocomplete), but I’m really excited for this minor breaking change note:

alt-left and alt-right will now move by one argument (which may contain quoted spaces), not just one word like ctrl-left and ctrl-right do.

You can somewhat work around this using Karabiner Elements. I map caps lock to esc (when tapped) and ctrl (when held) with a 'complex modification' rule that looks like:

    {
      "description": "caps_lock to left_control or escape",
      "manipulators": [
        {
          "from": {
            "key_code": "caps_lock",
            "modifiers": {
              "optional": ["any"]
            }
          },
          "to": [
            {
              "key_code": "left_control"
            }
          ],
          "to_if_alone": [
            {
              "key_code": "escape"
            }
          ],
          "type": "basic"
        }
      ]
    }

I agree some of the stations are somewhat repetitive, especially those stuck intentionally in an older genre like Lithium or one of the decades channels. I think the mix tends to still be less than surface level in those. They also have DJ-hosted segments; I think Tom Morello has a lot more flexibility in what he's playing, for example. It's still their superpower compared to the algorithmic track selections.

I love SirusXM. They are a truly unique offer in the modern music landscape of algorithm-driven music listening experiences. The human curation of shows and stations is why I listen. That said, they have a lot of problems: I have to complain yearly to keep my $8/mo rate, and they seem to be slowly moving toward wanting more algorithmic content with their Pandora merger.

I wish they'd focus more on growing their technology (e.g. a macOS app). They just did a big rewrite on all the platforms, seemingly toward this goal; I hope they keep going down that path.

If the government forces them to adopt more modern subscription practices, I think _more_ people would use their platform, not less.

Generally on Apple platforms the move here would be putting the shared binary into a dynamic .framework rather then trying to eliminate the shared dependency. Is this a limitation of authoring it in Go that it has to be entirely static?