I'm working on same for my family since I want to properly degoogle a bit. One thing I think long term - if I give my kids first-name @ last name , that means that I forever hold power over their email. Which isn't great. But what's the alternative? Register one full domain name per kid? Even ignoring the cost, the ergonomics are awful.
Imho email is missing a feature for nameless email addresses for when somebody just buys their full name as a domain name. If I get "firstname-lastname.name", having the email be "firstname@firstname-lastname.name' kinda ruins it.
A child born today sees email like we see the telegraph...
they'll grumpily sign up to gmail just so they can get a verification email, and that'll be all it gets used for. Messaging their irl friends will be done in apps like Discord.
lol I ran a sizeable team around 2020 and I had to educate a couple of our new hires straight from college that they actually needed to check their work email, after they missed important HR related stuff and they had just completely not realized it was an avenue for company communication, with an assumption that everything was available on our heavily used slack.
tbh I'm with the zoomers on this one. Work email is 99% junk. Newsletters from every SaaS product we use, "A meeting started", invitations for calendar events that I can just accept ON the calendar, notifications for every transaction on every system ("X posted a comment on Y,") and spam from salespeople, recruiters, etc. And then 1% of it is actionable important stuff that I don't get through Slack.
Email died because of the junk/spam issue. And it's self-fulfilling - when most emails are junk, nobody sends a love-letter or party invitation by email because the recipient probably won't notice it, which in turn lowers the usefulness even further.
If email was a commercial product, the company would have done something about that. Email died because it was an open platform, with nobody to address this systematic issue.
They probably didn't realize why they needed multiple apps to communicate inside the company.
I was in a situation where we had slack for communication between teams, email for corporate stuff similar you described, zoom for calls, personal messengers like WA for communicating with people in the company who didn't have slack, SMS/phone calls for alerts and various on-call staff. Total nonsense. No surprise I missed something.
Funnily I did exactly this, so the {lastname}.name is now legacy for me and nobody else of my family ever picked up the offer to have {firstname}@{lastname}.name adresses anyway.
Later (but before my name change) I managed to secure {lastname}.de which I stupidly missed during the early internet due to being a stupid teenager with stupid convictions. If I had secured this back in the day I think they would happily started using it but now they are all too settled in their provider/free webmail addresses.
Nice twist: The father of my wife owned {newlastname}.de since the dawn of the internet. So I'm still fine on that front. ;)
Aside: I'm honestly bewildered that Google doesn't have the ability to handle that in gmail accounts. If somebody gets married or otherwise needs to change their name, their answer is "just make a new google account" when all your stuff is still tied to the old account.
They rolled this out in March this year in the US (and December last year in India).
I've successfully renamed an old account with an email address I no longer liked. It works quite well on everything 1st party, but does have the potential of causing issues with OAuth on poorly-coded websites that key on email instead of user ID (ie. most of them). You do get to keep your old email address though, so it still ends up working fine in practice.
The feature is about fifteen years too late for me, unfortunately. By this point I need this feature to let me "merge Google accounts". But then I barely use Google anything anymore anyways.
Agree that the .name 3rd level domains are silly, disagree on .co.uk being a problem.
If .gov and .mil and .com make sense, then .gov.cc and .mil.cc and .com.cc make sense.
Of course, I think having more than one non-cc TLD was a mistake, but that's just me. If it makes sense to have topical TLDs for international and US institutions, it make sense to have national ones.
Nominet and therefore .co.uk has been around since 1996.
.co.uk is not going anywhere, and neither is Nominet.
The only "problem" is the original poster did not do their homework. I suspect they were inferring `uk.co` which is a completely different kettle of fish. The original poster should urgently correct their post.
This isn't about people who just happened to make it big in a market rally, though. You're talking as if I'm speaking about people who just happened to buy some Bitcoin in 2012 rather than leaders of some of the most successful corporations on Earth.
They're not infallible, but modelling them as complete idiots that just happened to get lucky is also... Not really consistent with reality, as far as I can tell. These people might not be good people, but they're good at playing a certain kind of game.
I don't think of Zitron as a journalist, I think of him as an entertainer, no different from all the columnists paid to tell people that what they already think is right.
The fact that you're holding him to a higher standard than fabulously compensated professional c-suite officers whose products are used in matters of life and death is... kinda weird?
Newspapers and magazines didn't sell ad space to obvious crooks back in the day. Scammers didn't have tv ads. Obviously there was somebody watching them. The trashy scams were reserved for the real scummy publishers: comic books.
I'm wondering, I haven't used the gmaps API. Is this because they're proxying maps requests through the US, or is there a specific header request to request the US version of the map, or is it just that they've a US-based GApps account?
Many of these are telcos that use "Buy Canadian" patriotism to get governments to protect them from international competitors. It should be scandalous if they're getting all their web front-end services from US companies. I know Google is the big name in maps, so that may be unavoidable and hard to shift, but if it's also the middle web-hosting providers... that's a lot less excusable for companies that love to wrap themselves in the Maple Leaf.
One kicker is how many sites leveraging Google Maps API in Canada are showing "Lake of America". I'm not sure if that's because they're proxying the Google Maps requests through a US server, or they're using an API call to specifically request the US version of the map. But either way, it's a pretty bad faux pas, especially for oligarchic telcos that wrap themselves in the flag when they're begging for protection from international competitors.
We just got a bug in our app for this, you basically have to add `region=CA` when instantiating maps API, otherwise it defaults to something hmm, else
(some says US, but in EU we clearly see Ontario, so there is some geoguessing or other mechanism behind)
This is where my position gets more nuanced. The default value should still be Lake Ontario, because that's what most of the world recognises it as. It's the most neutral name for it.
In general, I don't like that the world defaults to the Silicon Valley version of reality.
I mean is it the API or is it the website provider's metadata? I don't know anything about the gmaps API. I would assume the default locale would be that of the requester, not US (but then I know MS has the "Invariant locale" which is often best-practice, which is de-facto US... not sure if Google has similar).
reply