How many non-technical readers are a) going to see that HN post, and b) have any idea what the gobbledygook in those first few posts means?
Yahoo sent out email notifications to every group owner and member. I got mine on November 1st. Yahoo is definitely handling this badly: they should have offered an export tool, given a longer window, and been clearer in their messaging. But the claim that they didn't notify people (and just put the information up in a place no one would see) is wrong.
November 1st? That's barely a month ago. The Vogons broadcast to the world what they were doing just before they did it, too.
I think one of the unintended consequences of privacy legislation is it will support the burning the library of Alexandria over and over again. The default corporate posture will be : Delete all the data! It's a liability and figuring out what we can keep is an enormous headache.
Note that "deleting" is problematic in itself, especially for "cloud" data, considering how storage works, especially transistor one like SSD's !
Mark it inaccessible and write the new data over it in the next write cycle.
A lot of people are going to groups.io, but I certainly wouldn't want to suggest anyone move to another centralized system. The best thing to do is probably just to get a VPS and install phpBB or something. For group owners, importing our Yahoo archives there is going to be the next task.
It's simply way too much work. Dying projects generating no revenues don't get the luxury of having tens of people assigned to work on them.
How is it too much work to tar up that shit, put it on a big ass drive or two, and ship it to them? I can't imagine it's that hard.
`rm -rf /` is objectively free from Verizon's perspective.
Paying lawyers to examine the fine details and determine what liability may arise from publishing a database dump or the software that can view the dump's contents is not free.
And this is the dangers of relying on a private, corporate, for-profit law-bound organization. They're susceptible to abiding by the laws and of course, there is a cost attached to all of this. Exploiting a free resource, as we all do these days (reddit, youtube, facebook, hackernews itself etc) is all well and good but maintaining history is expensive (content needs moderating, you are required to abide by the GDPR…
We can still read Fidonet messages decades after BBSs died. The power of decentralized networks.
disclaimer: I'm a Member of Archive Team who's helping coordinate the joining of Yahoo Groups in preparation for archival. Yahoo's banning of a large amount of the accounts we were using is a huge setback for us. In total we lost over access to over 55,000 Yahoo Groups, many of these will now not be archived and will be lost when Yahoo deletes everything on December 14. Particularly disastrous was the loss of access…
It went pretty good for the first 10-20 or so groups but now I get the multiples of the really annoying captchas (click until none remain) per group... Damnit yahoo...
update: just enabling the vpn was enough to 'reset' captcha to the simple level, seems like yahoo does not take into account whether your IP is 'residential'.
It went pretty good for the first 10-20 or so groups but now I get the multiples of the really annoying captchas (click until none remain) per group... Damnit yahoo...
update: just enabling the vpn was enough to 'reset' captcha to the simple level, seems like yahoo does not take into account whether your IP is 'residential'.
I also noted that for yahoo changing IP, even changing continents, allowed me to use the same cookies as long as I kept my original browser window open.
It depends on the size of the codebase and how shitty your programmers are, but if you aren't greedy or scared of over-litigation, it isn't hard at all. I have written great contributions to a python API library that could be of benefit to the community around it. The code has nothing to do with my company's core competency, and the code is used for internal orchestration, so "exposing insecure code" is an unlikely c…
For new code it is indeed "simple". Old code however likely contains third party provided code, be it from libraries or code provided by contractors, where no (clear) license permitting relicensing of the source is available. This can be quite complex historic work as version history might not exist (which code come from where?) and documentation is limited (paper contracts lost in archives) and so on.
First, to Hell with whoever downvoted me, probably lawyers (not you, johannes). Second, I get there are occasionally complicating factors, BUT - licensing can't be difficult at most times, since the company often owns what the worker produces - for better or worse, it's simple that way. As for third party work, are you talking about library imports, or copy and paste? The logistics of solving those problems are either simple or really complex.
I wonder if this would be a workable idea: Create a service for long-term storage with an easy integration API; the idea would be that if you integrate your data with our service, and you eventually (maybe you're going out of business, or something) make a call to delete data, that data is first transferred to our service before deleting it on your end. Integrating with us is basically like making a reservation in ad…
P2P software has solved this problem a while ago?
With modifications, maybe. Like, you don't have to store everything on the service's end until you're ready to delete it. Also we don't seem to have a P2P service with the kind of contract I mentioned.