Here's another question about everyones tilde usage, and maybe
some food for thought:
I can see how a shared unix/linux system is a social construct.
People are sharing resources like saving their stuff in a common
file tree. Also, right from the beginning UNIX has supported
direct communication like motd, write and the very basic news
system described in *The UNIX Programming Environment* by
Kernighan and Pike. Using these systems users are literally
meeting and communicating on their one system.
However, while most of these basic services are still there,
they've been superseeded decades ago; by Email, Netnews and IRC.
Even talk and finger transcend the one system, making the net the
place people are actally meeting.
And so the question here is: in the tildeverse it seems to be
common lingo to meet on this or that tilde. Which seems to make
sense especially for the special interest tildes like breadpunk
or cosmic. But don't those users actually rather meet in the
#cosmic or #breadpunk irc channels? or the respective newsgroups?
That would be quite different from meeting on a particular single
system, wouln't it?
To ask the other way around, how much do folks actually use the
traditional communications systems like write, when interacting
on a single system?
Cheers,
lkh
However, while most of these basic services are still there,
they've been superseeded decades ago; by Email
finger transcend the one system
To ask the other way around, how much do folks actually use the
traditional communications systems like write, when interacting
on a single system?
But don't those users actually rather meet in the
[...]
respective newsgroups?
On Sat, 6 Aug 2022, lkh wrote:
However, while most of these basic services are still there,
they've been superseeded decades ago; by Email
Actually, Unix-local email (i.e. `mail` command) originated within
Unix itself, has been available from the *first* edition of AT&T UNIX
circa 1971; thus qualifies as one of the Unix social interaction facilities.
What this program originally did was simply appending the message to the recepient user's inbox (MBOX) file; and recepient would run `mail` command without parameter to page through (and manipulate) this file.
Nice side effect of this is you can use this old-school `mail` program
to send an Internet email on such system; but a less-nice side effect
is you probably cannot use this old-school `mail` program to read email
sent to you unless your system's MDA is configured to deliver emails
to you in traditional MBOX-in-homedir (or MBOX in spooldir) fashion;
and you would have to use whatever Internet email program you're
already using instead.
finger transcend the one system
Fingering user without `@` is a strictly local operation.
You'll notice the difference immediately on systems with EfingerD daemon (like Tilde.club, Tilde.team, and Tilde.instute)
that allows user to provide custom Internet Finger status text.
For example, if someone run `finger xwindows` on Tilde.club,
the information would be gathered via system calls and files;
and that person would see my (actual) login stats
as well as my ~/.project and ~/.plan content. No daemon is involved.
However, if someone rather run `finger xwindows@tilde.club` there
or from somewhere out there on the Internet, the Internet Finger daemon (EfingerD in this case) would handle the request,
my Internet Finger banner would be printed instead
(which in my case, contain ASCII art and ~/.plan content,
but devoid of actual login stats).
To ask the other way around, how much do folks actually use the
traditional communications systems like write, when interacting
on a single system?
I'm reluctant to use `write` (or `wall`); mainly because people today spend large chunk of terminal time in full screen TUI applications
rather than traditional line-oriented programs operating directly
on top of TTY. [1] This means apart from the message polluting the receipient's workspace, the message text tend to get mangled
(or disappeared) as soon as the foreground program redraw the screen;
which means the message (apart from being annoying) is also hard to read.
(Currently, it got a YTalk without the actual daemon runing, which would just hang when one run the client) Personally, I would prefer a `talk` implementation that works in peer-to-peer fashion over Unix stream socket residing in recepient's home directory without any central daemon;
but I hadn't tried to seek out and see if there is any actual `talk` implementation that works this way.
But don't those users actually rather meet in the
[...]
respective newsgroups?
I actually treat Newsgroups very much as a local facility,
just with wormholes that make things from "the other side(s)"
magically appear. (Considering that I actually read your post
in-spool on-Tilde with `less` and posted this reply via `inews`)
Regards,
~xwindows
Sysop: | deepend |
---|---|
Location: | Calgary, Alberta |
Users: | 255 |
Nodes: | 10 (0 / 10) |
Uptime: | 159:46:04 |
Calls: | 1,725 |
Calls today: | 5 |
Files: | 4,107 |
D/L today: |
12 files (9,998K bytes) |
Messages: | 393,013 |