#Zegnatalright, so no way to distinguish web users. Might be for the best. Though a bit weird to have slack users stand-out
#[aaronpk]oh funny slack treats `backticks` as code markers
#aaronpkif you do a whois on the web users you'll see they are connected from the web gateway
#aaronpkbut I don't think there's any value to distinguishing web users here. all part of the plan to treat IRC as plumbing rather than as first-class infrastructure
#aaronpk_webhm can web users use the /nick command?
#ZegnatWill Slack ever drop the [ ] and just use “IRC as plumbing”?
#aaronpkI'm not sure I can, because the Slack API doesn't give me enough to distinguish where the messages came from otherwise
#ZegnatI guess you can’t be /whois'ing everyone to filter out the slack-use username?
#aaronpkalso there's a higher chance of nick conflicts between slack users and IRC users
#aaronpkfor example I've registered "aaronpk" with nickserv, and i'm also "aaronpk" on Slack. using [] is a convenient way to avoid nick conflicts
#aaronpkbut if someone is joining from the web interface, they are probably not a regular IRC user, and if they are, they probably know whether they are currently connected to IRC
Zegnat1 joined the channel
#Zegnat1Aah, it uses numbers to stop nick conflicts
#aaronpkyeah, and IMO "aaronpk1" is less ideal than "[aaronpk]"
#Zegnatextremely low priority though. Most people using the webchat will be more likely to close the tab than to figure out a command for disconnecting
#aaronpkwhat'dyou change? should I be using your fork?
#M-keganI can add a hook in my fork tomorrow if you want. I'm happy with the numbered suffix currently but I've been bitten by it just renaming it without any overrides before
#M-keganThere's also more sanity checks to avoid spontaneous uncaught exceptions
#aaronpkI'd gladly switch to your fork if yuo've been making more progress on it than they have
#M-keganmatrix.org are pretty serious about getting a reliable irc bridge up, given it helps bootstrapping, so I've been able to dedicate a lot more time than most on it
#aaronpki've gotta finish my new site before i can go anywhere near this tho :P
#M-keganWithout sounding self promotional, some of the issues you've described would be fixed using something like matrix. We have web clients, irc integration, basic rest apis for rolling your own clients, and we're completely open source / standard
#M-keganThings like storage matrix.org does very well
#M-keganHum, interesting. Things like push we have covered, and aggregating from silos is a thing we aim to do well. We don't have any specific twitter integration yet though afaik
#aaronpkthe main reason I keep coming back to IRC for everything is because with Loqi, I have a simple HTTP and UDP API to get messages into a specific IRC channel
#M-keganBut if you have bots which are spitting stuff into irc, it's trivial to get them to do an http post to send a message instead presumably.
#aaronpkthis lets me write external services that do things like twitter searches where the result is piped into an IRC channel
#aaronpkI use weechat which is normally connected 100% of the time, so scrollback happens in the terminal interface. (weechat is running on a server at home in a tmux session)
#aaronpkin the rare cases when my weechat isn't connected, like last week when my internet went down while i was out of town), I get scrollback when it reconnects to the IRC bouncer
#M-keganThe format of that link is unhelpful because it's too generic, the spec for sending text messages is contained in the spec http://matrix.org/docs/spec/#m-text
#aaronpkcan I hard-code an access token into a script? (i.e. do access tokens have unlimited lifetime?)
#M-keganno, there's no links to matrix.org itself unless you federate (by joining a room on matrix.org's server) with it
#M-keganthe thing which I like the most about it all is the decentralised nature and persistent history. It's really nice to be able to have everything running on my own server, and to have synced history on both web/mobile
#M-keganand the extensible API makes it nice to add cheeky hacks on top <_<
#aaronpklooks like all the message history is stored in the database? (sqlite by default with optional postgres support)?
#M-keganand since we bridge with moznet and freenode, it's completely replaced xchat for me
#aaronpkbasically one file per room per day, one line per message
uhhyeahbret joined the channel
#aaronpk(i'm not too concerned with the actual format per line)
#M-keganthat would be hard to do. We originally had just sqlite support but quickly realised we needed a more performant option, hence going down the road of postgres
#M-keganthough it depends what purpose you want it for
#aaronpkdoesn't necessarily need to be the canonical store, so like writing a connector would be fine
#M-kegansince you can sniff all the traffic on your local HS using an application service
#M-keganapplication services are basically separate components which "register" with a HS, the IRC bridge is an application service. The AS makes a webhook and the HS sends it events it is interested in
#M-keganyou specify your interest as a regex, so you can just do .* and get everything if you want it for logging purposes
#M-keganso it won't be the canonical store, and you don't need to faff with db connections
#M-keganjust like how IRC client bots can be powerful, so can matrix ones, like the one which splat github/jenkins/jira into Matrix -> https://github.com/Kegsay/Matrix-NEB
#M-keganapplication services are not client bots though. They are more like IRC services / extra logic on the actual server
#M-keganmy point is that there's many ways to skin the cat, either by adding a client bot, or by adding extra logic on the server via an application service
#M-keganand there are examples of both (NEB for client, as-micropub for server)
#aaronpkcool, I might try to install this to see what it takes