Live data from Hacker News

Why We Should All Dump Yahoo

dumpyahoo.com

91–100 of 102 posts

Re: Why We Should All Dump Yahoo

#91
post #58

Earlier quoted context omitted.

The form action appears to use https. But yeah, it is 2016 and https should be the norm for even just loading pages with forms.

I host 20 sites from simple vps box with nginx. AFAIK i need an ip per domain to have ssl, unless I use something called sni, but I don't know how to set it up with nginx + let'sencrypt It's not that easy. Of course I could just throw cloudflare in front of everything, but no thank you.

You don't need to set up anything specifically for SNI, nginx does that out of the box. Unless you have to serve really old clients (some WinXP and android <2.3 I think?) SNI is no problem at all.

Re: Why We Should All Dump Yahoo

#92
post #14
post #12

Earlier quoted context omitted.

According to a statement given by yahoo to techcrunch it is a temporary problem. See: https://techcrunch.com/2016/10/10/yahoo-makes-it-difficult-t...

Right, something so basic to mail software that in 2016 it's still under development? I'm glad Engadget saw right through that too. It's pretty obvious they're doing whatever they can from losing users.

With the rise of DMARC, forwarding it trickier than it used to be. I understand why people want to dump it.

Re: Why We Should All Dump Yahoo

#93
post #4
post #2

While I agree with the sentiment. Here's why you should not delete your yahoo account. Once you delete your account, yahoo will make it available again to everyone. This means that if you have not unlinked everything it can be used by others to reset accounts on services you forgot that you linked to your yahoo account. Instead of deleting it, forward it all to another account and stop using it. Do not forget to log…

You can no longer set up mail forwarding with Yahoo. When Yahoo released a ton of unused accounts, I grabbed my last name (which I use on every service). I occasionally get mail for that email address. My Yahoo email is several years older than Gmail. It would take a LONG time to migrate to another service.

> It would take a LONG time to migrate to another service.

Why, exactly? mbsync (isync) between the two services, done.

Re: Why We Should All Dump Yahoo

#95

Earlier quoted context omitted.

Hmm? I run multiple https sites from a single Linode box without any issues. Nginx + letsencrypt.

So you are using SNI?

https://forums.freebsd.org/threads/57447/

Shows working sni with nginx and let's encrypt. You've probably done the same config error

Re: Why We Should All Dump Yahoo

#96
post #62

If we wanted to show that we weren't letting them do this without consequence, we'd be suing Yahoo and the Gov't like real Americans. We'd be suing for such an egregious amount that our national debt would look like a bit of pocket change. We would threaten the very life and livelihood of this country if we TRULY cared about our rights and privacy. But no, instead you want us to sign a petition. Give me a break.

Okay, so go find a lawyer willing to make it a class-action and start the suit. Find a list of damages and try to justify the large cost, then file. Or is angrily commenting on Hacker News easier? Give me a break.

You don't need money. If you've ever bothered to read the paperwork to file a suit, you'd notice a spot that says "I cannot afford the fees for attorney nor filing. Waive them."

Then you prove that, make it a class-action suit, and you watch as lawyers scramble to make their name representing you and the class.

This is how America works. If you haven't figured this out, I hope you do very soon, as it will be the only way you can defend yourself in eventuality.

Re: Why We Should All Dump Yahoo

#97
post #73

Earlier quoted context omitted.

The issue I have is that Yahoo evidently didn't even fight the order. Even if they thought they would lose, they should have at least attempted it. Or maybe they decided it was better to make money selling us out?

How would they make money?

I do believe they are allowed to charge the government fees for what they did; although I don't know how the amounts are determined.

Re: Why We Should All Dump Yahoo

#98

Earlier quoted context omitted.

I just checked LastPass; 324 out of 770 of my accounts use an email address as the username.

770 accounts?!!! I think this whole "set up a service for everything" concept ain't workin'. I'm trying to think how much storage just the TOS and Privacy Policies for those would run.

Many of them are old, and there are services for which I have multiple sign-ons. (e.g., four sign-ins for Hipchat, five for Slack, two for Amazon.)

There are also a lot of one-off things that require registration to try out whatever they're offering.

Some appear to just be security notes or stored keys from previous employers; others are imported from 1Password and haven't been used in the entire time I've used LastPass (5 years.)

Some are just fucking baffling, to be honest. What the hell is vodka-hoop.com, and why do I have an entry for it?

Anyway; what's the alternative to "set up a service for everything" that's not a single point of failure? (Although, I guess LastPass is that already.)

Re: Why We Should All Dump Yahoo

#99

Earlier quoted context omitted.

Hmm? I run multiple https sites from a single Linode box without any issues. Nginx + letsencrypt.

So you are using SNI?

Honestly, I don't even know. I'm not familiar with SNI.

All I know is I didn't have to do anything special to get the 2nd domain running ssl on the same box. It just worked right away as expected. I wasn't even aware that there might be complications.

Re: Why We Should All Dump Yahoo

#100

Earlier quoted context omitted.

770 accounts?!!! I think this whole "set up a service for everything" concept ain't workin'. I'm trying to think how much storage just the TOS and Privacy Policies for those would run.

Many of them are old, and there are services for which I have multiple sign-ons. (e.g., four sign-ins for Hipchat, five for Slack, two for Amazon.) There are also a lot of one-off things that require registration to try out whatever they're offering. Some appear to just be security notes or stored keys from previous employers; others are imported from 1Password and haven't been used in the entire time I've used LastP…

The alternative I've been leaning toward increasingly is to have user-controls-data as the model. Rather than pop up to a particular vendor, supply auth tokens, and have them pull up their information on you, you show up, they provide their tokens, and you provide your information (in their formats).

Combine this with a strong regime prohibiting inter-enterprise transfers of personal data. So that if Firm A want to talk to Firm B about User X, Firm A submits User X the request, Firm B confirms, and User X either complies or doesn't.

This would ... change certain dynamics of use of personal data.

Avoiding data loss: mumble, mumble something PKI key escrow trusted parties distributed encrypted data. Some form of personal data server as data origin, with re-shares distributed around social infrastructure. It may be a pipe dream, but at the very least it's a different model for considering pervasive data. If the user's Personal Data Stick or Home Server Box is destroyed in fire (or stolen or the cat eats it, or ...), then they and a trusted set of key escrow holders if necessary can reconstruct the data from shards spread amongs some n other systems, no one of which could individually reconstruct the whole.

"Services" in this model would be applications distributed out to operate on the user's own data directly.

Among other implications, the concept of coming up with a common base universal data format seems like a possible outcome. That could still be modified for individual service use, but the transforms would still have to map back to the core.

Post reply on HN