[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: To evolve or not to evolve

That we have an ever expanding ... installed machine base when the ever forward march of the latest and greatest browser technology leaves machines behind.
 Not just 8/16 bit machines under 100mhz or 80s/90's 32 bit bachines, but 1-2ghz intel stuff with 512mb of system ram that cannot keep up, 'newer' machines that are aging and entering the twilight years because they are suddenly unsupported by browsers where gopher can serve them really well!
 I think, like the tenfourfox movement, those machines could be served well by simply providing a gopher client with some active uptodate links(continueally updated as a project) to all the gopher services out there eg v2, gopherpedia etc etc etc (twitter gateway, tho I think this is now defunct?)
and a vlogger type showing people on a dedicated youtube channel exactly how gopher can serve the these newly legacy machines... users needs..
 Adressing the not so warm and fuzzy coder types presenting and the not as established viewerbase, detailed point scripts or outlines can be given to established retro community vloggers so that gopher can be explained episode by episode, and how it suits the needs of legacy / IOT..rpi and arduino...
 One could even setup a channel, having a series of scripts/guidelines as a 'gopherproject' episodes 1-10 and each episode being .... presented by a different presenter, going into greater depth or varied platform needs that gopher fills eg episode 1, gopher presented by 'the 8bit guy' e02 by an old pc vlogger e03 an arduino maker e04 by a hardcore maker into 3dprinting/cad/cnc ep05 rpi guy e06 tandy trs80 vlogger channel  e07 by a console guy getting online with his sony ps1 e08 a retro phone handset guy using new services with pocketgopher and so on and so forth..
 retaining the cohesion and progressive learning agenda, but spreaading it out over the community broad and far covering niche capabilities and new tech for legacy platforms,
 Even showcasing, once audience is up to speed some of the non gopher destinctive types of tech, eg gopher protocol additions to video players, and other technologies.
 eg gopher enabled mplayer for 68k amiga...
my 2 dung pellets....

From: Mateusz Viste <mateusz@viste.fr>
Sent: Wednesday, 26 October 2022 3:31 AM
To: gopher-project@other.debian.org <gopher-project@other.debian.org>
Subject: Re: To evolve or not to evolve
On 25/10/2022 19:07, Hiltjo Posthuma wrote:
> On bitreich.org the community started documenting some common
> addiions/extensions in use today.  (...)
> gopher://bitreich.org/1/scm/gopher-protocol/file/gopher-extension.md.gph

That's nice. Not that I agree with all that is written there, but I like
very much the approach of trying to formally document the status quo.
Too bad it is limited to a gopher sub-community, but that's the price of
a fragmented user base I guess, and I don't see any solution to that anyway.

I'd be curious to know: are there any other such initiatives out there?


Reply to: