Raw Text Club
rawtext.club
rawtext.club
"Our current relationship with the technologies of our hyper-connected world is unsustainable and is leading us closer to the quiet desperation that Thoreau observed so many years ago. But as Thoreau reminds us, “the sun rose clear” and we still have the ability to change this state of affairs.
To do so, however, we cannot passively allow the wild tangle of tools, entertainments, and distractions provided by the internet age to dictate how we spend our time or how we feel. We must instead take steps to extract the good from these technologies while sidestepping what’s bad. We require a philosophy that puts our aspirations and values once again in charge of our daily experience, all the while dethroning primal whims and the business models of Silicon Valley from their current dominance of this role; a philosophy that accepts new technologies, but not if the price is the dehumanization Andrew Sullivan warned us about; a philosophy that prioritizes long-term meaning over short-term satisfaction.
A philosophy, in other words, like digital minimalism."
The minimalist bit of the title does mislead some people into thinking it preaches "get rid of everything digital". But in practice, it is much more nuanced and helpful than that.
The quote you extracted sums it up perfectly, it's much more about not passively embracing everything about everything digital. But more about only taking what's worthwhile from those platforms.
Ezra Klein with Nick Carr:
https://podcasts.apple.com/us/podcast/nicholas-carr-on-deep-...
They even point you to actual text driven communities like SDF and tilde.club, which are both great. That's the best thing on their site.
I'm not sure it's really the reason. You could probably have performances in the same order of magnitude by sending JSON or simple HTML.
I don’t know if rawtext.club supports UTF-8, but if they only use ASCII, that would be a constraint I’m not sure can be matched in simplicity for both user and computer.
By old standards it's a huge server with a gigabyte of RAM memory and tens of GB of disk (maybe even SSD). Traditional text BBS's ran on 8 bit microcomputers with 64KB of memory and maybe some floppy disks, or perhaps a hard disk in the tens of megabytes, I thought.
I do like the idea of raw text. Leopold Kronecker famously said that God created ASCII, but Unicode is the work of man. Or something like that.
Is rawtextclub related to tildeverse? I feel like I'm missing some context here without which this part of your comment seems like a non-sequitur.
Heh?
Users log on infrequently, and you can catch up relatively quickly after not logging in for a couple of months. It's very asynchronous.
My primary use of RTC is hosting a gemini capsule and gopherhole generated from my Jekyll blogs markdown posts using a hacky shell script and pandoc.
Simple format, something like "RFC3339 <message>" and you can mention by doing @nick<their txt url> or something like that.
I forget the name and community though.
https://twtxt.readthedocs.io/en/latest/
There's also yarn[1] which builds on twtxt to give you APIs and mobile clients, etc.
The site is also available as a Gemini capsule: gemini://rawtext.club/ and gopher gopher://rawtext.club/
The idea sounds nice. It would be amazing if there was a cli friendly lightweight alternative to matrix.
I assume they use SSH for transport security. How do you discover content or message others though?
If it were up to me, I would enforce PGP signing for all content and PGP encryption for private messages. The network's key will be ultimately trusted by all clients. When accounts are registered, their key is cross-signed. Standardize it a bit and keep it very simple so that others can spin up their own "network". Network capacity scaled by means of mirrors, typical OSS style. Ban==signature revocation. Come to think of it, why is this not a thing already?
At the very least use these 100 bytes of CSS so it’s readable.
There is absolutely nothing wrong with allowing a sane default that works for the 99.9% of people.
The page already uses some crappy CSS that forces dark mode. Surely that isn’t OK if the user should be the one to need to supply their own CSS to use a site.
I really like the "call" model and "hold and forwarding" features of UUCP:
- All that's needed for two systems to exchange data is for one to call the other and it doesn't matter which side does or it how.
- A UUCP node will hold messages received by one node, but intended for another, until it makes/receives a call from the destination system or intermediate.
You can have a "leaf" system that calls into a hub system regularly but never receives calls, and it can still bidirectionally communicate due to the above. It'll be slow depending on the call schedule but it worked in the 70's. :)
It's a lot of work though because you have to specify all your nodes, links, and forwarding manually. You also have to integrate it with your UNIX mailer to get standard mail tools working with it, but it wasn't too hard with postfix.
uw-beaver!tikal!jes :-)
[1a]: https://www.complete.org/nncp/ a site with info about NNCP
[1b]: http://www.nncpgo.org/ the official site.
There's also a Matrix room and an IRC channel for questions and general community if you're interested.
[1a]: https://www.complete.org/nncp/ a site with info about NNCP
[1b]: http://www.nncpgo.org/ the official site.
There's also a Matrix room and an IRC channel for questions and general community if you're interested.
Hey, it's cool!
Eggdrop is configurable with scripts and for what that allows I want to simply quote https://en.wikipedia.org/wiki/Eggdrop: Scripts are available to add and extend support for: online games, stats, user and channel management, information storage and lookup, greeting channel members, tracking last seen times, botnet management, anti-spam, file serving and distribution (usually via the DCC protocol), IRC services (similar to ChanServ and NickServ), and much more.
- keeps a list of nicknames<->IP sockets,
- keeps a list of channels, which nicknames is in what channel, and the mode of each nickname in the channel (operator, etc.). First join command to a channel creates the channel and sets the creator with operator privileges.
- when a command to send a message is received (which must specify a channel), it forwards the chat text to the appropriate sockets based who is in the channel.
That's it. Honestly it's about the least you can do to turn TCP into a multiuser chat protocol. Because of this minimality, IRC was able to handle hundreds or thousands of simultaneous users on 1990 hardware.
Channel operators can kick malicious users, set topics, etc. Again, when you create a channel, you're op. An operator can give operator privileges to other users, so it's possible for a channel to have multiple ops and they can look out for each other - if connected.
When your TCP connection to IRC ends, classic IRC forgets all about you. If all channel operators lose their connection, then your channel may be opless and you might lose control of it. A classic IRC server is not like a modern chat server, it keeps no database or persistent record of chat text, nicknames, or channels. So you can't log off and back on and get your chat history, look at messages in the channel while you were gone, or get automatically joined back to the channels you were part of, or "own" channels. That was all offloaded to the client.
Eggdrop was a program that would let you create an IRC bot - you would run this on your early 90's UNIX shell account you got from your university and it would stay connected when you weren't dialed in. Eggdrop will connect to the IRC server you tell it under the nickname you provide, join the channels you tell it, and then sits in the channel.
You can give it op privileges, and would basically occupy the channel so it would not get taken over. It could also be set to auto-op people who joined (you could talk to the bot via IRC and authenticate). It was also possible to create multiple eggdrops that worked together and would look out for each others channels (a botnet) - ideally you would have multiple running from different IPs such as your friends from different universities.
Eggdrop could also talk in the channel, respond to chat text in the channels, and provide access to files or memos.
You could also telnet into the eggdrop directly and manage it, and talk with others on any botnet you setup. So if a channel or IRC server was being attacked or down, you had an out of band way to talk.
Most modern IRC servers have "NickServ", "ChanServ" services that provide things like persistent users, channel ownership, and such, but that didn't come around until the 2000's I believe. You might still use an Eggdrop to do IRC games or file distribution.
Fond memories of staying up late into the night.
To those that are complaining about discoverability: go to the gemini and gopher versions of the home page, and you will find a list of content made available by the users in those respective formats, I'm guessing no users are publishing html content hence the list of user generated content (which is supposed to be at the bottom) is empty in the http version of the home page.
For anyone interested in spinning up their own plain text blog/site, feel free to check out Shinobi (shameless plug)
Cool tool!
—-
Here I fixed it for you ;)
https://earthly-tools.com/text-mode?url=https://rawtext.club...
(Although for some reason a few of the paragraphs in the original were too wide for my screen)
I guess html has benefits :) Does Gemini handle wrapping?
_ _
__ ____ _| |_ _ ___ __(_)
\ V / _` | | || / -_|_-/_
\_/\__,_|_|\_,_\___/__(_)
I… think that says “values:”, but it took me a while to decide, aided by what I might call the known-plaintext heading “rawtext.club” written in the same style. figlet -f small Values vs. Valves
__ __ _ __ __ _
\ \ / /_ _| |_ _ ___ ___ __ _____ \ \ / /_ _| |_ _____ ___
\ V / _` | | || / -_|_-< \ V (_-<_ \ V / _` | \ V / -_|_-<
\_/\__,_|_|\_,_\___/__/ \_//__(_) \_/\__,_|_|\_/\___/__/ % figlet -f small values:
I think the default font (standard) is more readable. But they state, taking part is not easy:) % figlet values:
_
__ ____ _| |_ _ ___ ___ _
\ \ / / _` | | | | |/ _ \/ __(_)
\ V / (_| | | |_| | __/\__ \_
\_/ \__,_|_|\__,_|\___||___(_)Run it from your basement on a pentium and I'll be impressed ;)
Sorry I'm too old for this.
You could also run raspberry pi, or other small SBC form your home.
https://gemini.circumlunar.space/
Interesting, I did not know about it.
Not related to the original link, right?
1. https://phroxy.net/gopher://zaibatsu.circumlunar.space:70/1/...
I've no doubt that one could serve gopher pages using a microcontroller like the ESP-32. Gemini would be more difficult, due to encryption requirements.
Readers may also be interested to learn of the Spartan protocol, which is basically Gemini without the encryption and a more flexibly upload option. Spartan hasn't really caught on yet, though.
I've also heard of a protocol called Mercury, which I assume is similar to Gemini, but even simpler. I've not read up about it, though.
> RESOURCE MINIMALISM. rawtext.club runs on a tiny cloud-based VPS with 1 GB of memory and a 25 GB disk.
Nothing "tiny" about this!
Yeah. Of course, Who would not want to go back to the dark ages and strip everything down and go underground with the rest of the fringe projects that failed before it? Not to get too excited about creating a hidden sea chamber in the internet but I guess to each to their own?
I don't think the typical regular blogger off the street would want to revert back to writing manuscripts to their readers for the sake of privacy or setting up their own instance themselves just to join an exclusive party of 5.
If they won't do it with Mastodon why would they do it with this?
It's ok to build small, simple things. Not everything has to scale or be suitable for all users.
RTC’s pitch doesn’t make me want to learn more but there are probably people here who are totally into what it’s offering.