Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Alphabet selling Google Domains assets to Squarespace

bloomberg.com

Post reply on HN
Print view View original

461–470 of 623 posts

Re: Alphabet selling Google Domains assets to Squarespace

#461

Post by hfkwer »

fomine3 wrote: post #401
dingusdew wrote: post #304

Earlier quoted context omitted.

Exposure Notifications is probably already dead. It's dead in Washington state, which is also where it was originally developed alongside Google. If it's not being used in the state that it was developed in initially, it's doubtfully being used nationwide. Perhaps other parts of the world still use it, but the US no longer gives a rats ass.

Exposure Notifications was a great try by Google and Apple. If it weren't a thing, most big government would develop more privacy invasive contact tracing app. It seems that it wasn't worked well, but still a great try.

I trust my government much more than I trust Google and Apple not to invade my privacy.

Re: Alphabet selling Google Domains assets to Squarespace

#462

Post by wdb »

b112 wrote: post #419
pcurve wrote: post #292

Earlier quoted context omitted.

They've killed off almost 300. They have ~100 left. https://about.google/intl/ALL_us/products/ What do you think will go next? I'm sure some of these will bite the bullet this year. 1. Exposure Notifications (maybe in 2-3 years) 2. Google Arts and Culture <- this one has to be expensive to maintain 3. Keep 4. Scholar 5. Tilt Brush 6. Google Lens 7. Google Groups 8. Google Drawings

Google once tried to setup a 'smart' community in Toronto, including wanting control over police and laws and all sorts of other absurd blather. Can you imagine living in such a community? I can't believe people rely upon gmail for anything . Integrate anything . When I see a business using gmail for a backend, I question their entire business model, because I question their judgement .

They tried a Disney Reedy Creek on Toronto?

Re: Alphabet selling Google Domains assets to Squarespace

#463

Post by rootw0rm »

hackmehoff33 wrote: post #347
DLA wrote: post #204

Yet another business Google bails on. Add that to the pile. Gee wonder why Google Cloud is getting smashed by AWS and Azure—maybe because nobody trusts Google to not flake out on that business or key products within it. They need some management changes!

This! Google has a history and present strategy of making reactive moves to please shareholders. I’m shocked the masses trust them with email. When can we go back to decentralized self-hosted?

i haven't self-hosted email in the last decade, but last time i did...self hosting email sucked. every aspect of it was a pain in the ass.

Re: Alphabet selling Google Domains assets to Squarespace

#464

Post by galactus »

b112 wrote: post #419
pcurve wrote: post #292

Earlier quoted context omitted.

They've killed off almost 300. They have ~100 left. https://about.google/intl/ALL_us/products/ What do you think will go next? I'm sure some of these will bite the bullet this year. 1. Exposure Notifications (maybe in 2-3 years) 2. Google Arts and Culture <- this one has to be expensive to maintain 3. Keep 4. Scholar 5. Tilt Brush 6. Google Lens 7. Google Groups 8. Google Drawings

Google once tried to setup a 'smart' community in Toronto, including wanting control over police and laws and all sorts of other absurd blather. Can you imagine living in such a community? I can't believe people rely upon gmail for anything . Integrate anything . When I see a business using gmail for a backend, I question their entire business model, because I question their judgement .

Live+

Re: Alphabet selling Google Domains assets to Squarespace

#466

Post by dmnthrowaway »

Hopefully a good place to ask:

My family name .com is still available. That should be very rare in 2023. The name has only 4 letters.

It is also a word that is hard to pronounce in the english speaking world and I hope to get a reasonable price with that argument. Chances for a company with that name are slim and I also have no company or business in that name (normal employed software dev that I am)

The squatter in question has a form up asking for contact details and initial offer.

How would I go about doing that and what should I expect price wise?

Re: Alphabet selling Google Domains assets to Squarespace

#467

Post by minitech »

dmnthrowaway wrote: post #466

Hopefully a good place to ask: My family name .com is still available. That should be very rare in 2023. The name has only 4 letters. It is also a word that is hard to pronounce in the english speaking world and I hope to get a reasonable price with that argument. Chances for a company with that name are slim and I also have no company or business in that name (normal employed software dev that I am) The squatter in…

Pick a different TLD and don’t fund squatters.

Re: Alphabet selling Google Domains assets to Squarespace

#468

Post by jmabeebiz24 »

jiveturkey wrote: post #341
TX81Z wrote: post #272

Earlier quoted context omitted.

This makes zero sense, you could previously buy a domain, email hosting, and a web host in a single shopping cart more or less.

That will apparently still be the case. > Upon closing, Squarespace, a long- time reseller of Google Workspace, will become the exclusive domains provider for any customer purchasing a domain along with their Workspace subscription from Google directly for a minimum of three years.

I have a weird feeling that since they sold the domains to Squarespace, Google might sell off Workspace to them too.

Re: Alphabet selling Google Domains assets to Squarespace

#469

Post by anuraaga »

jorams wrote: post #446
cobertos wrote: post #226

Earlier quoted context omitted.

DNS is not registrar services. Comparing Google Domains to Google Cloud DNS is like comparing apples and oranges. Though it's true you'll usually want both if you're working with domains OR DNS. _Needing_ to interface with a 3rd party for a critical part of any web app or service feels like a step backward for Google's commitment to Cloud.

There's also Google Cloud Domains. It's entirely unclear if that's also being sold off, but the sale would make a bit more sense if it's not. It's insane how bad Google is at communicating things like this.

I had never heard of this service but indeed, it seems to be a registrar builtin to GCP. I suppose this is not going to be killed, and presumably the reason they aren't migrating domains users to it is awkward mapping to GCP projects? It would be great to at least have a button to copy it over for people that do have a GCP project for it...

Edit: it looks like there may indeed be such a button / command. Really strange they wouldn't communicate the option to keep customers on their services!

https://cloud.google.com/domains/docs/import-domains

Re: Alphabet selling Google Domains assets to Squarespace

#470

Post by dumpsterdiver »

Dalewyn wrote: post #444
dumpsterdiver wrote: post #428

Earlier quoted context omitted.

Fair enough. If you're only playing local files that were obtained from a trustworthy source then you wouldn't be affected. With a complete RCE like that though, I would definitely not advise playing music downloaded from peer-to-peer networks. While I'm not familiar with the exact requirements to exploit the vulnerability, I would err on the side of caution and assume that music files can be crafted that contain mal…

The details are all right there: It's a vulnerability with the in_mp3.dll plugin (it's the decoder for playing MP3s), specifically with insufficient checks against malformed name and artist tags (probably ID3 tags?). It's fixed in Winamp v5.52 and above, and the version I use is v5.531 so I'm not affected as it turns out. I'm sure there are other bugs that I'm affected by, but again: Not really concerned about it.

Yeah, to clarify, the part I wasn't sure about is if it was required to somehow integrate your local Winamp installation with the streaming service, or if it could be exploited simply by playing a downloaded music file. It sounds like it could indeed be exploited without being connected to the service.
Post reply on HN