We're launching Bitcoin payments available to every Square point of sale with 0% transaction fees for next year. 1% after that. Available Nov 10th. [https://squareup.com/us/en/releases#bitcoin]

My sincere hope is it catches on and helps out small business. The difference in fees can really add up, and with near instant settlement to dollars on the backend, the merchant doesn't even need to hold or think about Bitcoin unless they want to.

The fine article talks about stablecoins, but in my biased opinion those are much more complicated than Bitcoin to deal with right now.

Whatever wallet you use did need to have liquidity on the network that can reach our routing node, c=, but we worked hard to make sure we had plenty of liquidity to all major wallets. I definitely recommended cashapp without shame at the conference, but I did a lot of testing with other wallets too. I never had much trouble, even with non-custodial lightning wallets.

I am also slightly paranoid as a security engineer, and admit that whole heartedly.

When I was an intern 15 years ago I worked on a software library for this https://www.embeddedts.com/products/TS-IRIDIUM Board that does a similar thing (though you would need to stack on a cellular board if you wanted cell modems).

We used them to help Arizona Department of Transportation collect traffic data in remote locations.

We had big plans at that company to make a much smaller, much cheaper 9602 transceiver replacement, but the company got bought out before that could launch.

https://btcpayserver.org/

https://typer.tiangolo.com/

If you use Poetry and a pyproject.toml, you can even make your package installable with something like pipx straight from Github. Its a trick I use often for little command line utilities.

https://python-poetry.org/docs/pyproject/#scripts

Please bring this display technology to larger formats if it ever makes sense economically, this is like the dream for a wall calendar.

Comments URL: https://news.ycombinator.com/item?id=39862054

Points: 1

# Comments: 0

The wikipedia link above explains it well:

""" Orbital velocity of the satellites is approximately 27,000 km/h (17,000 mph). Satellites communicate with neighboring satellites via Ka band inter-satellite links. Each satellite can have four inter-satellite links: one each to neighbors fore and aft in the same orbital plane, and one each to satellites in neighboring planes to either side. The satellites orbit from pole to same pole with an orbital period of roughly 100 minutes.[8] This design means that there is excellent satellite visibility and service coverage especially at the North and South poles. The over-the-pole orbital design produces "seams" where satellites in counter-rotating planes next to one another are traveling in opposite directions. Cross-seam inter-satellite link hand-offs would have to happen very rapidly and cope with large Doppler shifts; therefore, Iridium supports inter-satellite links only between satellites orbiting in the same direction. """

The 'seams' have interesting implications for latency when I was working on Global Data Broadcast.