595 karma · joined January 12, 2017
The whois information is masked, because that's what we do to protect customer privacy.
https://domaininvesting.com/godaddy-whois-records-no-more-co...
It's registered to someone in New York, not to GoDaddy.
Registrant Organization: Registrant State/Province: New York Registrant Country: US
https://domaininvesting.com/godaddy-whois-records-no-more-co...
It's registered to someone in New York, not to GoDaddy.
Registrant Organization: Registrant State/Province: New York Registrant Country: US
The whois information is masked, because that's what we do to protect customer privacy.
https://domaininvesting.com/godaddy-whois-records-no-more-co...
It's registered to someone in New York, not to GoDaddy.
Registrant Organization: Registrant State/Province: New York Registrant Country: US
The whois information is masked, because that's what we do to protect customer privacy.
https://domaininvesting.com/godaddy-whois-records-no-more-co...
It's registered to someone in New York, not to GoDaddy.
Registrant Organization: Registrant State/Province: New York Registrant Country: US
https://domaininvesting.com/godaddy-still-not-frontrunning-d...
The whois information is masked, because that's what we do to protect customer privacy.
https://domaininvesting.com/godaddy-whois-records-no-more-co...
It's registered to someone in New York, not to GoDaddy.
Registrant Organization: Registrant State/Province: New York Registrant Country: US
Bad actors in different nations than consumers shouldn't be able to leverage sovereignty or agreements like NANP to be bad actors with impunity.
Its not just "kick everyone out of the US country code", it's protect consumers by principle of least surprise sorta. But again, this only protects against toll fraud and not all of the other "Appear to be in a nation you aren't" scams.
Heck, we constantly receive calls with invalid phone numbers. And it's not always on purpose, sometimes it's just crummy or small-time carriers in rural areas (no disrespect intended, this is just an honest statement from experience). If we ingress filtered all invalid numbers, it would almost certainly be devistating to our customers.
This is like with email. First we need an integrity mechanism, then we can start doing reputation and identifying bad actors.
Distrusting one of them and the calls that come from them is something of a non-sequitur since you chose them and intentionally became one of their customers and pay them to receive those calls.
TL;DR This isn't like email or IP traffic where you're interacting with other IPs in a purely untrusted network model. Merely analyzing the previous hop doesn't tell us anything valuable.
Of all of them, I think T-mobile is the most willing to actually improve the industry for everyone's benefit.
When we receive a SIP invite (incoming call) from one of our upstream carriers, the amount of metadata information they're able to provide us is often very limited (largely due to interop issues in my opinion). If you think about IP spoofing, BGP, and the state of egress filtering on the internet, it's a very similar situation.
Since this is related to my work, obviously all of the above is just my personal opinion.
Your thoughts in light of that?
Otherwise, we need to set the rules and pricing conditional for being a part of +1 to mitigate this issue.
No disrespect to Canadians, but I wonder if most Canadians are aware of how much fraud operates out of Canada and takes advantage of the +1 area code plus the protections of being in another nation. This isn't just Carribean Island nations as people tend to stereotype.
(Please miss me with the whataboutism, I'm not throwing stones simply sharing information and experience.)
There are plenty of non-technical consumers who have had a very unwilling education in what latency is and how it differs from speed.
Listen kids. A colossal amount of the software engineering that takes place on this earth is paid development for closed source apps and services. It's not on GitHub. It's not written in JavaScript. It's not done on Node.js. A great deal of it doesn't happen in California. And it dwarfs the amount of software on GitHub or GitLab.
It happens in Java and C++ and C# and Visual Basic and other not-sexy languages and involves writing crappy enterprise interfaces and tons of backend code.
The great thing about TIOBE is its a good indicator of what jobs are being hired for. That's why it doesn't match whatever trendy expectations most people expect to see in a languages ranking. That's why Visual Basic is always ranked so highly. Because the actual world of paid software engineering and your mental view of that world are wildly different.
Personally I think TIOBE is very valuable for what it's for. I tell young developers to use its top 10 list as a guide for where to invest your time IF you're taking a "safe" approach to career skills and employability. If you use one of the other guides for that, you may decide that learning new and exciting languages might be optimal for employment. Generally speaking that's not the case.
If one wants filter bubble expectations met, I recommend sticking to language rankings that are solely based on GitHub and other publicly available source code.
I believe there's a lot of potential for CDNs and major sites to offer anti-censorship pass through traffic with HTTP/2 via CONNECT. By having a multiplexed protocol with multiple streams that spans "normal" traffic and tunneled traffic, it should be harder to identify. This would allow major sites or CDN providers to provide service to those people behind such bans and possibly require governments to break a significant portion of the web in order to institute those blocks. I think it's valuable to increase the damage done by government blocking so we can ensure that mainstream persons are sufficiently upset by this conduct. I also think CloudFlare and other major CDN providers should be the ones to provide this type of VPN access either as a product or as a special case offering for people in countries who censor the web.
I realize there are many businesses who wouldn't damage their primary offerings to provide such a secondary service. But it only takes one or two companies to increase the collateral damage of the bans, and thus make them much more costly for the governments imposing them.
I ended up using StartMail from the StartPage people. It's not perfect, but I was actually able to migrate to it and use it effectively.
1) Propose API changes with blatantly obvious impacts on some of the most popular extensions. Include no explanation of how these extensions can rationally adapt to these new APIs and provide the same or adequately similar functionality.
2) Don't bring any timing data to justify the performance claim that ad blockers are taking an irrational amount of time implementing their content filtering. When others run these same tests they find no performance issues.
3) Characterize any strong reactions to such a suggested change as inappropriate. Feign surprise and dismay at the fact that such reckless API changes, which would drastically change the status quo on the web, are invoking.
4) Condemn those who didn't react the way you expected when you threatened to vastly change their web browsing experience for the worse. This helps diminish user input in the future, by tying everyone with honest opinions to those who express their opinions in an inappropriate or unprofessional way.
5) Act insulted when people point out that your employer, who is in control of the situation, happens to financially benefit from the changes.
The above experience was so distastefully handled across the board, I really think it justifies a unified and community supported "ungoogled-chromium" project without any of their trademarks in the name. That way we the users of the web can determine our relationship with the browser. It's the user's agent, not the browser vendor's agent.
But most importantly, use Firefox with containers and uBlock Origin.
PS. Despite the above, kudos on the port of NoScript. Never give up, never surrender.
>Sellers can use “Fulfillment by UPS,” so UPS handles shipping of its products through its vast logistics network. But UPS also charges for that privilege.
Spooky!
The counterargument, maybe their license doesn't block us from using their work in the way they think it does, and until it's proven in court we won't know is extremely offensive and self-serving.
This is the same argument raised by many GPL violators. "The GPL hasn't been proven well enough in court in my jurisdiction so I'm just going to use your code in violation of your license terms."
This is theft, an open source license violation, and lawyering to defend that theft. It violates the principles of open source. We are literally discussing an OSI approved license. I believe that any responsible member of the open source community would respect the authors license and not try to lawyer their license out of your way so you can have their code on your terms.
If this was Linux devs and GPL, rather than Solaris devs and CDDL, everyone would be on the other side of this argument. It's hypocrisy and it should be called out.
TL;DR ITT: "Link auditing / ping will eliminate the disadvantages of tracking!" - Ad Industry and sites that serve tracking: "What disadvantages?"
You can't be someone who loses their mind over GPL violations, but then willfully misinterpret someone else's open source license because they have something you want. The developers involved specifically picked CDDL because it wasn't GPL compatible. That was their desire / intent, and so that's the license they went with. By ignoring the license and the clearly known intent of the developers in choosing that license, simply because they made something you really want, I believe that ZFS on Linux is really a form of theft in the open source world. It's the same sort of attitude that leads to GPL violations.
I don't agree with making things CDDL to be explicitly GPL incompatible, but I do believe in respecting the author of the software in question and the license he or she chose. If people choose licenses I don't agree with, I don't use their software. I don't just use it anyway and pretend like there's no license issue.
You don't have to be RMS to see that these people who are ignoring the licensing issues (not just shipping user mode tools like a FUSE implementation which is legit) honestly don't care about open source and licensing and copyleft. They just see something someone else made that they want and they take it and ignore the licensing and developer intent. How can we hope to enforce the GPL successfully but then ignore other OSI approved licenses when it suits us?
This is why big names in Linux kernel development aren't remotely interested in ZFS.
Not to mention the fact that the users of ZFS on Linux are all setting themselves up for Oracle to bring the licensing inquisition.