701 karma · joined October 13, 2012
I've thought before about trying to render skies on the web as a series of gradients overlaid on top of one another. I expect I could have had some level of success and gotten some mediocre results, but it would be nothing compared to what you've created.
Thank you so much for sharing this; it's inspirational, must have taken you a very long time to put together, and I'm blown away by your results.
<h1>Unavailable Due to the UK Online Safety Act</h1>^I find that turn of phrase to be particularly pleasing in this context.
Parsing dates with anything other than fromisoformat feels totally backwards in comparison. We were using ciso8601 until fromisoformat was in the standard library. And now things are incredibly simple and reliable.
I've curated a list of 500+ critically acclaimed albums, which I continue to add to as the Mercury Prize nominees are announced each year, Rough Trade releases its albums of the year, etc.
It picks 12 a day and that's that; it's the same 12 for everyone. If you see something familiar, you might want to go for that. Or if you're in the mood for something new & different, you can give something unknown a try.
I suppose I was thinking about the app responsible for getting the data into, say, Leaflet's local database in the first place. For that app, the data structures you describe are the APIs that it consumes, for the sole purpose of populating its own database.
That gets my cogs whirring about how good a use-case this would be for SQLite. I suppose it would be somewhat appropriate for a small, private, PDS? Although, if I understand correctly, I wouldn't need to worry about that anyway if I'm using some off-the shelf PDS software, e.g. https://atproto.com/guides/self-hosting
To your "This is not done by hitting an API" point; if I understand correctly, I'd argue that the _endpoints_ that you detail in your post _are_ the API. The whole point is that there's no single _central_ API, but each server that wants to be part of the network participates by hosting an API that meets the standard outlined in the protocol.
In a way it's semantics, but I'd be interested in yours thoughts on that. To either correct or confirm my understanding.
That's not true. A long sentence of your choosing is easy to memorise and plenty long enough to not be able to be guessed by a computer (brute force).
In other words, there are fewer low quality results which raises the average quality of the results you’re presented with
Gone are the days of sketchily using a hairdryer, apparently.
There was a post here recently about anonymising the IP addresses in the logs to be absolutely sure that you don’t end up collecting any personally identifying information (PII).
It otherwise looks great but the side scrolling is too much of a compromise for me.
I’m using Safari on iPhone.
> Use this design system to make *government* services consistent with GOV.UK
Emphasis mine. Are GDS aware of this work? I am in no way affiliated with GDS by the way.
--
I'm always wary of this kind of thing not being on a gov.uk domain, which in this case is entirely appropriate because it's not in anyway official or endorsed by GDS. Not for any direct phishing/crooks concerns as raised above, but because it waters down the impact of this kind of thing always being on gov.uk domains.
--
Edit: I'd be _very_ surprised if GDS don't take issue with you having "GOV.UK" in the name given that it is no way associated with gov.uk
1, 1, 2, 3, 5, 8, 13, 21, 34, 55 …
21 km is ~13 miles, 13 km is ~8 miles, etc.
A 26 mile marathon? Must be ~42km.
Same for speed limits too; 34 mph is ~55 kmh
ipv6 yadda yadda yadda
https://img1.wsimg.com/isteam/ip/da3386ad-a465-4e41-834e-354...
Also, Cheshire is a county in the north of England so the whole article was very confusing from the get go as to where this station was located. Here it is on Google Maps: https://maps.app.goo.gl/aEWT2L6QYqntYDDz5
Bolton, Kensington, Oxford, Coventry, and—slightly left field—Berlin are also nearby.
The README links to the Homebrew install script, relevant lines highlighted here: https://github.com/nikitabobko/homebrew-tap/blob/main/Casks/...