bbrks

Don't blame yourself too hard... No recurring subscription emails are such a huge dark pattern that I didn't even realise it was legal!

Surely a receipt or an invoice is the bare minimum they should do. Awfully scummy of them.

A typical single lane road in the UK under national speed limits (60mph) have dashes that look like these - if not opposite (longer lines with shorter gaps)

Based on some other road details, like the barriers, bollards and road signs, I'd say it was modelled fairly realistically on UK roads.

https://maps.app.goo.gl/r2ZfKdv9eVUPm4H89

A tool like Dash/Zeal to have a searchable local copy of dev documentation.

I use it even when online because it's simply much quicker and a coherent UI across many languages.

Use one of the notification websites to grab a $5.99/mo KS-1 from kimsufi (OVHcloud) - it should be in stock multiple times a day

It's a tiny dedicated server that should be plenty sufficient. I run all my personal infra on these (and the higher spec ones) and they're great for the price.

Intel ATOM N2800 2c/4t 1.86GHz 4GB DDR3 1066MHz 1TB 100 Mbps

Does that vague "bypassing 'technical limitations'" clause also cover tweeting messages more than 250 characters by screenshotting your notes app I wonder?

Many young European countries reliant on tourism, like Croatia, introduced digital nomad/remote working visas mid-COVID to encourage people to stimulate their local economies when tourism suffered the most.

Couchbase Lite offers delta-sync and P2P replication over any transport. Has client libraries for all mobile OSes, Java, and recently C.

CBL is backed largely by Sqlite with features layered on top. Local query support, server replication and a bunch of other nice features useful for an offline/P2p database.

Disclaimer: Employee working on the server-side Sync Gateway component for Couchbase Mobile.

This is how MacOS presents thermal throttling in the Activity Monitor - there's a visible "kernel_task" process taking up CPU.

The downside is of course, that users see this process name chewing up 500%+ of CPU, google "kernel_task cpu", and find the commands to disable the thermal throttling to "fix" the issue!

https://eclecticlight.co/2019/02/25/playing-with-fire-dealin...

For those who may be wondering why 88x31px?

https://www.quora.com/How-did-the-odd-size-of-88x31-become-a...

You might want to check the CI history of vim too if you want to compare meaningless metrics.

https://github.com/vim/vim/actions?query=workflow%3A%22GitHu...

As somebody new to both, are you able to elaborate on what telegraf/TICK provides that the collection of programs in the post does not?

I see lots of posts complaining about the stack in the post, but all of the alternatives posed don't really explain why.

The real value in unit tests comes when you need to refactor a codebase. Especially if you're not the original author. Unit tests are a codified API contract.

It's easy to write something small and correct from scratch (like a greenfield microservice). It's far harder to maintain that over several years and several changes of hands.

Sure, that satisfies the uniqueness aspect if that's all you're looking for in an ID. But it doesn't satisfy the predictability aspect.

You can't know what the ID will be ahead-of writing the item to the database, nor store the item in a shopping cart without retrieving the item via a different piece of information (which is pretty likely to be SKU in this case)

A foreign key is a hard-constraint that must be enforced.

There's no stopping you from storing item IDs in a theoretical shopping cart table without FK constraints though. It's just that the onus is on your application to provide the guarantee that the item exists.

This becomes a little clearer if your item IDs are not simply auto-incrementing IDs (which have their own challenges in a large distributed system), but instead are SKUs, or things which have actual meaning.

They did. M87* was the widely publicised "first" photo, but they also got images of Sagittarius A* (the supermassive black hole at the center of our galaxy).

The difficulties with Sgr A* are twofold:

- The black hole moves too much during an observation (because it's much closer, and parallax is a thing)

- Sgr A* is much smaller than M87* by mass, so even though it's much closer, the angular diameter is almost the same, and the accretion disk is dimmer.

I think Zoom now has a preference for holding down space to temporarily unmute your mic. But I fully agree, push-to-talk should be absolutely mandatory for any calls with more than 2 people in them.

Listened to the first two and it's now on my quite varied pool of podcasts to listen to on my commute. Thanks!

My old place uses Gin. Works well enough, but had some problems with URL param handling causing our API design to eventually become a mess.

Stuff you should know No such thing as a fish - random trivia/comedy The infinite monkey cage - scientific trivia/comedy Sawbones - Medical history/trivia Go time - golang community IRL - Internet cultured topics by mozilla

A little bit "out there" but I've been impressed with 'Dry Erase: Infinite VR Whiteboard'[0]. You get far more space to play with in a virtual environment than you can get on a screen. This would be killer if it supported multiple users over the internet, which is possibly being considered by the dev.[1]

[0] http://store.steampowered.com/app/585040/Dry_Erase_Infinite_...

[1] https://steamcommunity.com/app/585040/discussions/0/14584554...

15" rMBP 2013 here. Glad I went for the expensive 16GB option, doing that seems to have held pace with even today's laptops.

A shame I can't easily put Linux on it though for further longevity.

Seems OK here in the UK. A few years out of education and focused on Golang in which demand is outpacing supply, especially in London.

The first paragraph mentions it's using Hyperledger's Fabric[1] blockchain implementation. I assume they're building their own smart contracts on top of that.

[1] https://github.com/hyperledger/fabric

I've been writing Go for the last 18 months, and seeing it dissected side-by-side with C [0] is causing some epiphanies that I wouldn't normally get to see in day-to-day programming.

Excellent resource.

http://hyperpolyglot.org/c

In the UK, Tesco have been running a 'Scan as you Shop'[0] thing for a couple of years now. Customers pick up a scanner as they enter, scan their items as they go into their cart, and they have special checkouts which read your scanner.

There's a random chance that your scanner will be audited by a human against the contents of your shopping cart. Usually the first time you use it, then it backs off.

[0] http://www.tesco.com/scan-as-you-shop/

jq uses empty square brackets as a way of accessing all of an arrays elements. Not sure if this tool uses the same syntax?

E.g. users[].id

I've been using Atom for almost a year in Ubuntu and OS X without this problem.

LastPass works fine for me in this scenario (plus a mobile device).

I'd rather be on an Open Source password manager, but I've found the sync is always too painful to do yourself.

Spam calls are a nuisance in the UK too. Especially on landlines.

If you threaten them with reporting to the TPS (Telephone preference service) and they're not just a robot, they sometimes stop bothering you.

I was about to ask some questions about exactly what gets sent to Kite and what you do with it. Your privacy page[0] answered my thoughts and concerns quite nicely.

[0] https://kite.com/privacy