robalfonso

I disagree. The com/net zone is 144mm records, thats about a billion dollars per year in revenue. The technical requirements to store 144mm records with metadata and have multiple redundancy, backup datacenter failover etc. does not come close to that in costs even if those costs are 10%. The cost is completely divoriced from the technical requirements, its simply what the market bears and is use to. They have momentum on their side.

Some of the new tld's are very inexpensive right now, but that is only the short term business model to get market share. Their renewal prices are often higher and will stay that way.

I work for a registrar as well. You are right, I hadn't considered ccTLD's What I find really insidious about ccTLD registries is the crazy rules they have (and therefore the crazy business rules I must use to support them) this doesn't fix that, but as you pointed out it might help some of those small ones that are otherwise out of luck.

Not in practice, the reality is most of the new gTLD's went shopping for industry people - you have to, there are so many unique technical, regulatory, and industry specific items you just buy the expertise, trying to learn on the fly is a monumental task.

This is strictly for operating a registry (ie deploying the infrastructure for your own TLD), getting a TLD granted is through ICANN.

Its great that google is open sourcing this, however, its a bit curious as anyone who is going to be operating a registry really has the resources and expertise to manage this kind of thing (both hw and sw). Unless the end game is to get big resource users (like registries) onto GCE, its a bit odd.

A lot of our internal architecture is driver based. So the calls and interfaces are generally the same and the enterprise logic for example is determined in the driver, also helps migrating 3rd party vendors because we just write a new driver to handle that system.

I don't think of my employees this way,in fact I just had one raised to the new "average" because it turned out they didn't negotiate well and were below average ( not my hire, just now my report) - it was a 12% raise.

Play devils advocate and see how a "mega corp" runs things. If you could pay everyone discretionally (ie decided by mid level manager) you'd be out of business tomorrow. Those companies keep cost controls just because they are so large. Larger businesses offer more employee security, but there is also less chance for financial growth. The counter offer is essentially a hack on the system.

Some times office policies prohibit giving employees good raises and precipitate an environment where a counter offer is necessary to get a good pay bump. The act of the employee looking elsewhere usually removes those internal handcuffs.

Its not always about shafting an individual so much as managing the entire business.

This can also be wholly subjective to the company, culture, boss, and employee.

Just to add on to this. The NTIA has never exercised much in the way of oversite/interference. The largest issue I can recall was they got involved when the .XXX tld was being implemented.

As you say the actual running of ICANN/IANA and the internet at large is really managed under a multi stake holder model and is very inclusive and diversified.

Arguments to the contrary are typically FUD.

I just bought a 600 dollar pair of boots, the primary features being quality build,materials, and the ability to re-sole - they will last me 30 years if I take care of them.

Point, however, I think its pretty clear a bluetooth candle is frivolous on its face....that said if you could control over the internet that could be a useful product feature. i.e. left your candle on and ran out? Extinguish remotely. My wife has done this before (the leaving on not the engineering a internet candle...unless she's hiding that from me)

I agree completely with you, I would stipulate one thing. When starting a new job its reasonable to take a short term hit in the hopes of advancement (and higher wages). So its fine to have a room mate and live a less than desirable life time short term. I think the time to pull the plug though is at dumping the stock.

Really its fine, but the first handful of times I kept looking around for "Pull Requests". It was like a slap to the face.

While I agree with you, one thing that absolutely drives me nuts with this argument is scale.

Norway Pop. 5M (approx) Finland Pop. 5M (approx) England Pop. 53M (approx) Canada Pop. 35M (approx) United States Pop. 318M (approx)

The scale is way off from many other countries who have implemented the kind of healthcare reform being talked about.

When you get to hundreds of millions of people all kinds of issues arise that you don't see elsewhere.

China and India are the only countries more populous than the United States and I'd be nervous to experience their health care system. In fact you have to go quite far down the population list to get a first world country where that kind of healthcare is being implemented (happy to be proven wrong here)

No question, I considered that too. But for determining position in 3d space I think its more consistent than having floors. If you get to say the 10th floor with different floor heights the difference could be considerable. Its the problem with whats practicable in daily use and what makes sense from a system perspective.

I think a couple changes would be required to address the shortcomings:

apartments need a z value as you already have a x and y - of course you need to account for height above sea level if you keep to the same type of measurement as lat and long (rather than just saying floor 2). It could be tricky for someone to sort that out for themselves.

I'd think a prefix on the address could indicate a special case that needs to be handled differently to fix APO etc.

I played with the demo, it seemed like the city/county operate as a checksum so you can verify the location you've decoded. Its not needed but nice to have

Any position can be determined from x,y,z, you could just tack on the z coordinate - though you'd need to match that locally, accounting for sea level. If you are using latitude and longitude you should stick with the paradigm for height, since floors can be different heights.

I'd think the smell test for whether he can serve is no different than if a state governor can serve jury duty. The requirements for impartiality are similar.

It looks like governors have served on jury duty as well

https://www.washingtonpost.com/news/local/wp/2015/06/10/even...

I do care, I'd like to know about surveillance (whether I can do something about it is secondary). Knowing may allow me to modify my behavior.

To your point about reasonable expectation of privacy. On the surface, yes, you do not have a reasonable expectation of privacy in public, however, I do not like the idea of having my picture tied to identifying information like a mac address. It starts to provide a fuller picture of a person and would allow more data in which to build up a profile.

At the end of the day I'd like to choose how and when my personal information is exposed (to the extent that I'm realistically able to control it)

Time scale is worth considering here. Certainly over the short term this is a bad move for the company. What remains to be seen is how it will affect the company long term.

The company in this case also generated a lot of good will, something that is hard to get, hard to value, but very important none the less.

Too many corporations are so focused on quarterly performance they fail to account for the long term.

I've only ever had one dev do that and I paid it (I ended up not hiring him but because of his code, I was impressed he asked about payment!). I have no problem valuing someones time and desire to be compensated for it.

Some companies do all day interviews or at least 3-4 hrs, what is really the difference between spending the day in an office or at least few hours versus at home with your tools and setup?

Are you less offended if I give you 2 hrs of problems to whiteboard while I watch?

There is no situation in which a company can not spend at least some time evaluating your skill set. For me the best would be to hire you based off your resume and see how it goes for 90 days. However, its often unfair to the employee - especially if they have a position currently.

Hiring is a skill for both parties. some people are good at the process naturally, other people put time into being good at it, the third group has no clue and has no interest in learning.

You miss my point, I simply mean a forum post is not ideal for support. In my case I would want a ticket, something concrete I know can be sent and seen. A forum does not engender confidence my issue will be seen and also I would not want to put private info into a forum.

Also I gave a poor example. I run a Es cluster so my thinking is at the point of my cluster is unavailable i know it's all red and it's not between my service and the endpoint.

Thats a Gouda idea!

Agreed, however, their model should include a base level of direct support for straightforward things. Like "my cluster is unresponsive" right now thats a forum post and seems a really poor experience.

I operate a registrar, I'll outline a couple pieces of the puzzle here and the justification for the price. ( I couldn't read the stack exchange article - redirect issue)

First its recognized these are digital goods where the incremental price is very nearly approaching 0. Technical aspects of domain registration have very little to do with the price.

That said ICANN has various requirements for registrars and registries that do require more than just keeping an entry in a database. For registries, you have to not only have a hot failover data center location for your registry but you are contractually obligated to test it (I believe every 6 mos. but its not my part of the industry). For registrars you have to escrow your entire domain settings both incrementally and fully (daily and weekly) for all domains, this way if you disappeared as a business tomorrow they could recover everything. This is audited regularly and swift action is taken for those who are delinquent.

Those are the technical issues, the rest of the cost is highly related to the administrative burden of domain management.

Some of these are:

  DMCA takedown requests

  Generic legal requests

  UDRP Claims

  Governmental abuse claims

  NGO abuse claims (i.e. other hosting firms etc)

  WHOIS verification claims

We get these kinds of requests on a very regular basis (ie hourly/daily), it takes a team of people to manage them and its a never ending torrent. Some of them can be disposed of quickly others take a lot of time.

There is also a huge amount of what I'd term "misguided requests". For example:

A company who makes a ICANN complaint because after the UDRP ruling saying they won a domain and access to the domain was provided, they failed to renew it, let it expire and another company got the domain. This happened and turned out as you would think. This still took 1 person a week of investigation and back and forth to dispose of.

Complaint that a domain registrant did not receive expiration notices when in fact there is no history that they'd ever been a registrant of the domain.

People who file false WHOIS complaints with ICANN because they don't like the domains owner, whois complaints MUST be verified or the domain is taken offline. These complaints create a huge burden.

All of these requests have rules about procedure, deadlines that must be complied to and a form of investigation that must be adhered to.

While many domains are nice and quiet and don't need much attention. The legal, abuse and governmental drivers that run the modern internet create a ton of overhead for registrars. That overhead is manifested in your fees.

This is only about normal fees. Premium domains are strictly market driven and the "scarcity" of a domain/tld is highly subjective. Costs are less about overhead and more about what the market bears.

Hope this has been insightful for anyone who read this far!

Most domains can have up to 13 name servers assigned at the registry, most domain registrars will let you setup 6 or more (mine does 6). Ideally you'd have your registrars and another source hosting your dns and keep them synced up.

Unless you have a weird edge case most of the time its set it up once and forget it. This way even if you registrar has problems you have another dns that is still up. Do a dig on some popular domains (like google,cnn,etc) and you'll see they have multiple dns entries by different providers.

If your website is important enough to keep up in case your registrar is not, then you need it hosted by multiple providers including your registrar (its usually free, why not right).

I get your point, but consider any household with higher income and you'll see all kinds of specialty appliances. (Central vaccums, wine fridges, warming drawers) so a dedicated folding machine would fit right in.

To your point about tops, if you watch the video I could see it being capable to do pants, you may have to fold them over once when you hang them.

Thats interesting. I wanted alerts as my primary reason for getting a wrist device.

I agree the garmin was very sharp but mine for whatever reason lost bluetooth connection constantly.

The pebble on the other hand has been great for notifications.

I really wished the garmin had been better about that. YMMV.

The process doesn't care that there are 200 bidders, the high bidder wins. The risk is in too many people bidding, and then you paid 185k and escrowed a amount of capital to do so. Now imagine you are participating in lots of auctions, it would be a substantial amount that is tied up for this process. In reality everyone who bids has a business model to actually sell the tld should they win. Not too much speculation going on here. What I don't recall is if you get your fee back if you lose, I want to say yes.

How this process actually works is you apply to carry a gTLD (ie .blog) this application fee costs $185,000. If no one else applies for the same string, you are good to go. If they do there is an auction. The auction works like this. N parties participate and must provide an escrow account (to bid in good faith) they may bid up to what they want (and whats in escrow) and the winning bid pays out to the auctioneer (a minor fee) and the losing parties.

IE 3 parties to this auction (making this up)

automattic - 19 million paid Party 1 - 9.5 million earned Party 2 - 9.5 million earned

You are essentially paying off your competition to go away. There are some other details and this was the initial process a few years ago, I have not heard if there are any significant adjustments now.