1,094 karma · joined October 14, 2014
BTW, the paid accounts provide TOTP code storage, more comprehensive password health reports, emergency vault access for others, hardware key support, someone to call with problems[0], and encrypted file sending.[0]
One day, the company that makes this hammer says that they will be updating it to automatically tell the company a bunch of information about the hammer's use -- when it's used, where it's used, what the environment is like around the hammer, how many times it's used, what it's used for. They assure you that they don't care about who is using the hammer, but obviously it will be YOUR hammer reporting the information, so at some level it will be associated with you.
Why are they doing this? Well, they know that sometimes their hammers break. They only know this, though, because sometimes their hammers break for their own employees and sometimes customers tell them hammers break. They would really like to know ALL the times their hammers break, though, so that can try to fix all the problems with their hammers, and not just the ones they see or get reported to them. They say this will be best for their customers and that's why customers should be on board with the change.
No one would ever buy that hammer again, right?
Regardless of the privacy implications of the company knowing everything about your usage of the hammer, the company is basically saying that their hammers break so much that many of their customers don't bother telling them and just go use someone's hammer. In other words, their product is bad and their customers don't value it enough to deal with it.
Don't even get me started on paying monthly for that hammer ...
1. It put the marketing might of one of the largest corporations behind its brand-new, niche product. The deal created an incentive for this corporation to market the product on Apple's behalf.
2. It created a forced scarcity. Only /some/ people (those on AT&T) could get the iPhone, which immediately created a brand distinction necessary for a luxury product. On day 1, there were haves and have-nots.
3. It provided an out for Apple not ramping up production too fast (whether they could or not). If the iPhone failed, they wouldn't have product everywhere. If Apple couldn't make iPhones fast enough, they would only be affecting a subset of the market.
4. It limited Apple's engineering requirements. They only had to support AT&T's network on day 1, and not the network technologies of the other carriers. Limiting exclusivity to AT&T meant that they could focus on the product while delaying the technical challenges of supporting multiple cellular networks.
[0] https://hbr.org/2021/10/what-if-central-banks-issued-digital...
Note, this was not an "unexpected" change (it's been in the code), but it WAS unexpected that the provision was not extended.
Note that this affects not just startups. My wife's firm is a small, employee-owned, non-tech S-corp. This hit them as well. It resulted in tax bills for the shareholders approximately 25-30% greater than the firm's accountants expected them to be. The shareholders are on the hook for those higher taxes, although the company did the right thing and distributed extra cash to them to offset the higher taxes.
If you had told me 3 months ago that Bing would be a serious threat to Google, I still would have laughed. That's how much impact the ChatGPT integration had for Bing -- overnight.
That said, I agree with many professional golfers that the way to address the distance issue is through the clubs and course design. It's a simpler solution for the game.
The same is not true for Trump today. Even if Biden pardoned Trump, establishment politics would continue to have to deal with him moving forward. He has shown no indication that he would stop attacking everything around him.
Not all VPN providers sell data (DNS or otherwise). Some operate for privacy-driven reasons and actively seek to be good stewards for their customers.
And the broader community (i.e. the city in which the housing would be built) is fighting it because they don't want affordable housing to hurt the values of homes that already exist in the area. Everyone supports the teachers -- until it affects their home values.
[0] https://www.dailymail.co.uk/news/article-11812901/New-images...
If you were an ISP, you had to support everything. For the 56.6k stuff, I remember us having two separate dial-in pools for X2 and K56flex.
One of the things we used to do when I first started was shuck modems. We would buy the consumer models, break open the plastic cases, pull the circuit boards out, and slide them into slots of custom enclosures. Then we would hand-assemble DB-to-ethernet adapters and plug them into serial controller banks.
We bought any and all modems, but the cheap models from US Robotics and Supra were really a game changer. The only tough part was that dealing with the slight differences in command differences on the client side needed to connect to the different modem types.
I will throw one more into the mix. A few years ago, a core system at our company went down. The system was very old and several times IT leadership had investigated replacement solutions, priced them out, and sought approval to execute on them. For one reason or another, it always got punted. Then one day, the system had a major hardware failure and took some parts of the business down. The core services that customers paid for continued to operate as-is, but it was still a giant black eye. It took a few days to stand-up an emergency solution, and several more weeks to stand-up a more permanent solution.
So, maybe Dish just didn't invest properly in a core-but-not-critical area of their technology and it finally gave up the ghost.
In addition, your traffic will be the only thing coming from that VPS, so tying network information to you will be easier.
The key thing to remember about VPNs is that you are re-positioning your trust. Instead of trusting your ISP with your traffic, you are trusting the VPN provider. A hosting provider is about as trustworthy with your traffic as an ISP, and offers the same amount of pseudo-anonymity. It's a lateral move at best.
[0] https://d3lcr32v2pp4l1.cloudfront.net/Pictures/780xany/5/2/3...
While it may signal some cooling, housing is still substantially less affordable than it was pre-pandemic.
* edited to correct the time frame, 36 months not 24 months.
I don't want to respond to part of your comment and not the other, so I'll just say: I don't know, because exactly defining the specifics is not my goal.
> Fundamentally any decisions a site makes to filter and sort content to show, including HN ordering by vote count and mixing in new content to allow it to make the top page, is an explicit choice they are making that cannot be differentiated from "promotion"
This is the part of your comment that actually matters to me. This statement is so definitive, and yet there are people arguing just as definitively that some ways of prioritizing content for users create liability while others do not. I think there is a difference between "elevating when it otherwise wouldn't be elevated" and "providing a moderated list", but those two states are probably separated by a grey area, not a bright line. I think how YouTube identifies content for users is distinguishable from what HN does, but I also don't know if that difference matters with regard to liability, especially with regards to Section 230, which makes no attempt to legislate HOW content is made discoverable.
In my language, I say HN does not "promote" content because the view for me is substantially the same as the view for everyone else. Contrast that with YouTube, where Google's algorithms elevate content specific to individual users, thus leading me to conclude that Google thinks I "should" watch the content. I would argue that far more than automated filtering, signals from other users, and human moderation goes into YouTube's recommendations -- particularly a calculation of the revneue to Google of you watching the video.
But again, this concept that Google "promoted" the content that harmed the plaintiffs and should thus be liable for that action is the heart of the case, not that Google should be liable for the content itself.
When YouTube recommends content to me, the original author did not target that content specifically to me, and YouTube alone is making the decision to put it in front of my eyes.
Hacker News does not directly promote content (aside from prioritizing content based on non-content factors [age, voting, etc.]). It does moderate, but that is not the same as promotion.
The crux of the argument in this case is that the plaintiffs want Google held liable for promoting content, not hosting it. The difficulty the Supreme Court seems to have is understanding what the boundaries are between promoting content and simply delivering a usable view of content choices to consumers, and whether Congress intended for that difference to matter with regards to Section 230.
Is Hacker News default feed that promotes highly-upvoted, newer stories to the front of the list and example of HN promoting those stories? If so, should HN be held liable if that algorithm pushes content that harms others?
A point not made in the PM episode is that in markets with a lot of waitlists, charging for a position on the waitlist increases the likelihood that the families on the waitlist will be available when their turn comes. If waitlist membership is frictionless, then the daycare cannot count on that future backfill as strongly.
Yes, they could raise their rates, but if they did, many parents would have had to go elsewhere. It was a balancing act to charge enough for the quality they wanted to provide while also being able to be affordable for the community they served. Most teachers were younger, and did not last very long (two years at most).