Timeline for engineer list by rozzin, page 54
rozzin
engineer
Thursday, 29-Nov-0001 19:00:00 EST
-
#breakfast: coffee, oatmeal, butter, #marmalade.
-
Mmm.... I haven't had spaghetti in ages. I think I just decided on #dinner.
-
I'm using #spectrum2 to bridge #IRC / #XMPP now; it's better than the #ejabberd module, but still has some problems; I don't think it's expecting to actually be used for IRC....
-
This #IRC #XMPP transport in #Python looks nice, but needs some work to #port it forward to currently-available APIs: http://xmpppy.sourceforge.net/irc/
-
… and of course the #ejabberd #IRC transport doesn't stay connected to IRC when the XMPP clients go offline…
-
I'm trying to find a good #xmpp → #IRC gateway.... The one that comes w/ #ejabberd seems useless—it wants a separate back-end IRC login for every front-end XMPP session under the same account....
-
As an #IRC user, I'm always #frustrated by people using bridges that make it harder to talk with them by hiding them behind a single `bridge bot' handle with their actual name hidden _in the message content_ from the bot...
-
A principle of `depend strongly only on the most stable + least restrictive channel, attach everything else peripherally' would seem to apply even if you don't `own' that central `POSSE' hub https://indieweb.org/POSSE
-
… and doing "PESOS" like this seems a pretty awful choice when "POSSE" possible: https://indieweb.org/PESOS https://indieweb.org/POSSE @mmn
-
@mmn I'd guess #CreativeCommons think they're reaching out to some set of people they they think they can't connect with via IRC... Though as you noted there seem to be some big holes in the "can't" reasoning there.
-
@olobolgerbaggins@quitter.se, does #Mattermost actually fill a different need than, say #gnusocial + #email?
-
@strypey @rozzin @bes use MatterMost for all my team communication. it's great and light
-
@taknamay If you control the servers, you can create various methods of integrating the channel memberships/rosters.
-
@bob They say their IRC channel is linked in with a bot to Slack (I guess just relaying "<SlackUser1> blah blah", eliminating tab completion).
I'm curious however whether that's even allowed by Slack's EULA and - more importantly - what happens when Freenode notices an extremely spammy user (think ~20 Slack users communicating simultaneously, relaying everything to IRC).
-
Btw, this means that noone who is the member of a country which has a trade embargo with the USA can become part of the "chatty" community of Creative Commons, right?
Since everyone who uses Slack must become customers there.
-
...yeah, or just IRC. There are mobile friendly clients, clients integrated for web browser use, multiple desktop varieties. They could even pre-configure and brand a "Creative Commons chat client" since it's all !floss. IRC is excellent because it doesn't require a preregistered account, it is a common and well-spread means of communication, it can be integrated with …
-
#Slack is the opposite of a common and not even very creative!