Human-Assisted Archival of Yahoo Groups
github.com
github.com
If they will use their cache of yahoo addys to exfiltrate Yahoo Group content, we'll give them a free month of gitlab user spam usage no questions asked.
Unfortunately doesn't seem to be updated very frequently.
> Your email address is not linked to a Yahoo ID. To join this group, you need to link your email address to a Yahoo account.
Then you need to go into "Account security" and link an email address with the account. I don't know why the instructions don't tell you this.
Thanks for the suggestion though, I saw that thread about linking a fallback email address as well but that seems to be a different thing.
Thanks for helping us test our next CAPTCHA on HN, you’re getting closer. https://xkcd.com/810/
https://github.com/davidferguson/yahoogroups-joiner/issues/1...
Let Google and Verizon Media know with a tweet:
https://twitter.com/intent/tweet?url=https%3A%2F%2Fgithub.com%2Fdavidferguson%2Fyahoogroups-joiner%2Fissues%2F14&text=@Google%20and%20@verizonmedia%2C%20increase%20the%20reCAPTCHA%20quota%20of%20Yahoo%20Groups%2C%20archivists%20are%20blocked%20from%20preserving%20history.&hashtags=letusarchive%2CrecaptchaGiven that my account got a connection attempt from Sweden, I guess that's where the archivist live. Hopefully he will have a nice morning tomorrow thanks to the community.
I'd rather we archive large or relevant groups first instead of going alphabetically and having to join groups with just 1 post.
Crowdsourced labeling doesn't make sense if you already have something that can tell you what the label should be.
https://bbs.boingboing.net/t/as-the-end-nears-for-yahoo-grou...
https://www.zdnet.com/article/verizon-kills-email-accounts-o...
https://www.theinquirer.net/inquirer/news/3084557/verizon-bl...
But yes, you are right. We need to keep pushing it into the public sphere. Twitter, Reddit, I hate to mention FB here, but ...
I primarily mean newspapers. The Times (of London & New York), The Guardian, but Bloomberg too.
The story is probably a wider point about the fragility of online information, for which this is a mere significant event, but without that happening I just don't see the give-a-shit count increasing.
For organisations, the best you might be able to do is some kind of co-operative: it's much less likely to sell out (although not impossible), you generally get a vote in how it's run, and since they're forced to be self-funding you're not dependent on VC funding whims. With sufficient runway transparency you can always know how far they are away from shutdown and how much funding they need.
Twenty years ago (!) I helped set up a hosting co-op for university societies: https://www.srcf.net/
One of our specific aims was preserving continuity. Most societies are run by undergraduates who do it for a year or two and leave after 3 years, so making it as easy as possible to handle handover was a key feature. It's done pretty well for something that pre-dates Facebook, Github, Myspace, and even Yahoo Groups itself.
The "backend" will be Apache. On day 1 we used SSI (server-side includes) for "theming" pages, which were all in handwritten HTML. I suspect it's still like that given the five blank lines before DOCTYPE. It looks like some bootstrap CSS has been sprinkled on it since then. There's no front-end Javascript because there doesn't need to be.
> Until 2006 we had just one server in use, kern (a dual Athlon 1.6GHz PC with 2GB of RAM and 400GB of disk). Before that we used to run on an ancient Intel Pentium running at 166MHz with 128MB of RAM. How times have changed :)
Indeed. That ancient system was perfectly adequate for serving web pages to a few thousand people for light use. At the time I was carrying around the amazing new thing that was a computer you could fit in your pocket and play music illegally downloaded from the internet on. It was a Toshiba Libretto 30 with 8MB (eight megabytes) of RAM and a PCMCIA sound card.
Our systems approach to the SRCF was very much "what is the simplest thing that could possibly work". Apache+CGI+PHP with UNIX user accounts will get you a long way if you let it.
The real achievement is political and personal. I'm amazed that they've always managed to find good enough volunteer staff for the whole thing for twenty years.
Help by Joining Yahoo Groups so the Archive Team can Download them (easy! - this is the link in the OP here): https://github.com/davidferguson/yahoogroups-joiner
(That's the most needed right now so the scripts can get access to the groups.)
Help by Downloading yahoo Groups with the Archive Team's Script (not hard!): https://www.archiveteam.org/index.php?title=ArchiveTeam_Warr...
Get the word out/Call for Action (put pressure on Verizon!): https://modsandmembersblog.wordpress.com/taking-action/
Don't miss the sidebar with these links:
https://modsandmembersblog.wordpress.com/media-contacts/
https://modsandmembersblog.wordpress.com/contacting-verizon-directly/
https://modsandmembersblog.wordpress.com/contacting-verizon-yahoo-stockholders/
Also, you can add these emails to the media contacts: "Reporter Katyanna Quach" <kquach@theregister.co.uk>,
"Managing editor Gavin Clarke" <gavin.clarke@theregister.co.uk>,
"Corey Wilson & Rachel Janc; Senior Director, Communications" <press@Wired.Com>,
"Pitches" <submit@wired.com>,
"Rich Woods" <rich.woods@neowin.net>,
"Paul Thurrott" <paul@thurrott.com>,
"Brad Sams" <brad@petri.com>,
"Kate Rayford, Media Inquiries" <katie.rayford@slate.com>,
"Bryan Lowder (LGBTQ issues/culture)" < bryan.lowder@slate.com>,
"Torie Bosch (emerging technology effects on public policy and society)" <torie.bosch@slate.com>,
"Jonathan Fischer (big tech, cities, media/internet culture)" <jonathan.fischer@slate.com>,
"Susan Matthews, Health & Science" <susan.matthews@slate.com>,
"Erika Allen, Executive Managing Editor" <erika.allen@vice.com>,
"Katie Drummond, SVP, Global Content" <katie.drummond@vice.com>,
"Press, US" <press@vice.com>,
"Press, Canada" <presscanada@vice.com>,
"Press, UK" <ukpressoffice@vice.com>,
"Pitches, Culture" <culture.pitches@vice.com>,
"Pitches, Tech" <tech.pitches@vice.com>,
"Issues" <issues.pitches@vice.com>