Yahoo Groups archive

MOTM

Index last updated: 2026-04-05 20:20 UTC

Thread

FW: [motm] OT: Future of Yahoo Groups

FW: [motm] OT: Future of Yahoo Groups

2001-04-12 by Tkacs, Ken

Is there any way, I wonder, to get the database files for the past two years
so that someone else has half a chance of hosting the archives in case the
worst happens...?
Show quoted textHide quoted text
-----Original Message-----
From: 	Scott Evans, Gen Mgr [mailto:esresource@...] 
Sent:	Thursday, 12 April, 2001 2:56 PM
To:	EFM_Synth@yahoogroups.com; motm@yahoogroups.com;
oakley-synths@yahoogroups.com; SergeModular@yahoogroups.com
Subject:	[motm] OT: Future of Yahoo Groups

Hello to all,

This message is being cross-posted to the four Yahoo groups with which I
spend the most time.
I heard on the radio yesterday that Yahoo is in the beginning stages of
financial difficulty and that there are layoffs planned. My intention is to
begin discussion on the possible alternatives to Yahoo groups to avoid any
possible interruption to our interests and also to explore the possibilities
of archiving the valuable discussions that current rest on Yahoo servers. If
the company does have problems, it would be a shame for all of this
knowledge to suddenly become inaccessible.
I wish that I could lend some information to this discussion, but I am far
from an expert in these matters.
Scott

Re: FW: [motm] OT: Future of Yahoo Groups

2001-04-26 by Hugo Haesaert

Hi All !

I subscr*bed 26jan99 .  I have 11481 messages on file .  Occupies 
just under 44Mb on my hard disk .  I did delete quite a few posts 
with pictures attached tho .

If needed i can extract messages, kick them into a few email friendly 
zip's and send them to anyone starting up an archive .

When replying to the list using "all", one can easily "cut" the 
addresses not needed .  Easier than copy'n'paste ;^P

Bye for now .


Keep 'em oscillating :)


Hugo
=

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.