1890 year. The telephone tower The Telefontornet in Stockholm (Sweden 🇸🇪) connected 5,000 telephone lines.
#sweden #connectedpeople #SaturdayMug #stockholm #telephone #SaturdayThings
Since I just saw yet another developer use '1.2.3.4' in an example configuration, a reminder that you MUST NOT use publicly routable addresses that you do not control in your code.
Instead, use one of the available 'TEST-NET' IPv4 or IPv6 ranges documented in RFC 6890, such as;
192.0.2.0/24
198.51.100.0/24
203.0.113.0/24
❌ 1.2.3.4
✅ 192.0.2.4
Pass it on to all of your fellow developers, documentation writers, and so forth.
Full RFC is here;
This memo reiterates the assignment of an IPv4 address block (192.0.0.0/24) to IANA. It also instructs IANA to restructure its IPv4 and IPv6 Special-Purpose Address Registries. Upon restructuring, the aforementioned registries will record all special-purpose address blocks, maintaining a common set of information regarding each address block.
@timrichards In the opposite direction, something that's new(-ish) is actually grabbing your GPS data when you call 000.
https://exchange.telstra.com.au/triple-zero-advanced-mobile-location/
When you call 000, your phone will now also activate the GPS, grab your lat/long, and then automatically shoot it off to 000 as a text message. On the call centre side, we correlate the phone call and the text message back together, and then hand that location data off to police/fire/ambulance. This is way more precise than using the cell tower information to guess within a few km.
It does go in the opposite direction though of capturing more data rather than less. Again, lots to balance.