@ekes That rendering was available as a layer on the OSM site for a while, and then removed. No idea why! It's definitely better, though the shades of blue for tram and metro are far too alike.
Is there a concept in #programming for whether an #API is inward or outward? For example, suppose I have an interface whose intention is that other code can implement it, but it's only supposed to be called by the internals of my code: it's public for implementation, but internal for callers.
@jbutz Yes, Drupal plugins is where I've encountered this. My module consumes the plugins, but other modules can implement further plugins to extend functionality.
@aaronfc APIs can go in both directions as well though - for example, a service that you can call and whose class you can replace is an API that's both inward and outward. You can call it and you can implement it.
@rupertj@internal is the total opposite of API though - it means the whole thing can change at any time. A plugin interface isn't internal, it's a one-sided API.
@aaronfc Some interfaces are meant to be called and implemented. Some are only meant to be implemented and not called. There might be cases (I can't think of any) that are only meant to be called and not implemented.
The thing is, if I wanted my computer to record me, I'd want it to record the three sentences I typed without noticing that my app had crashed and whose text has vanished because I was typing into an unresponsive window. How the fuck is a screen recording going to get me those back, huh Microsoft? #Recall