In article <
91cb6epccdjihdpqu...@4ax.com>,
>>Convert them to Mastodon? - - - - Well, you could try. ;-)
>
> Which merely adds one more layer of complexity. I got drafted to
>be the Canton's Seneschal. To change the business meeting(due to an
>anticipated attack of the Frost Giant) I log into the Nikolai Account,
>and check Canton email, the canton facebook page, and the SCA.org
>site. Log out of that and into this to post to the Interwebs. Then
>call a couple people to handle the phone tree.
>
> Adding Mastodon to this merely means, Yet Another Bunch who
>believe that social media is the Internet. Should I include Twitter,
>Pinterst, Punch, and some cool site you've never heard of?
It feels like we're vaguelyt off-topic ... but still:
It's reasonable for different people to have different preferences.
It's not reasonable fr people to think their favourite site/medium
is What The Internet Is. But folks do that. *sigh*
I think it's well into the time for there to be a coordinator/aggregator
layer that sits atop of email / usenet / social media / chat / dm / etc.
and presents these in a user's preferred abstraction (to the extent that
each can be bent or folde to fit said preference), with an addressbook
that tracks each correspondent's preferred medium. So if I want to send
a message to Miles Singer, my addressbook would contain the information
that Miles prefers Twitter DMs, and convey my message to him that way
without my having to remember that or go to Twitter directly. And when
I wanted to send a message to Tristan Hunter, it would get delivered via
Facebook, per his entry in my addressbook. But since I personally
prefer email, from my end it woul look very much like sending email.
(Okay, neither Twitter nor Facebook exist in Dr. Singer's & Tristan
Hunter's world. Conceivably pneumatic tubes might, but they weren't
mentioned in the story. Bear with me; I needed a couple of names.)
Discussion-type mailing lists would probably not map very well onto
this, but something very similar (or perhaps a module of this) could
work for announcements: after some care with initial setup, someone
responsible for newsletters and announcing reschedulings and such would
enter their missive once, and it would be fed to the organization's
various social media accounts, its mailing list, the appropriate spot on
its web site, etc.
Two _relatively_ minor hurdles and one larger one: (a) coming up with a
robust design adaptable to many users' preferences (not just folks like
me who'd be happy with feels-lik-email) without requiring a dauntingly
high learning curve to set up in the first place, (b) creating a smooth
implementation skating past all the pitfalls in the various APIs, and
(c) -- the one that makes the first two, which would normally count as
pretty big deals, look like the smalls ones -- Facebook would hate this
and keep tweaking its API to break it, so _maintenance_ would basically
be an _arms_race_. :-(
It would make the world better, but Facebook wouldn't want it to.
(Because Facebook serves not its users, but its advertisers, of course,
and this would not reliably show Facebook's ads.)
--
Daphne Eftychia Arthur
dap...@panix.com
Grandis vetus factio delenda est.
Everything is better with live music.