we have sort of reverse engineered the de facto chat/web API to write chat bots for it, but we haven't transformed that into a gateway to other protocols
@flyingfisch we have non-standard features for chat rooms. Chat was built for our internal needs, and the needs of our sites. It integrates with Stack Exchange... not the outside world.
the reply feature is really nice, too -- one thing I truly like over&above XMPP/IRC -- click the little reply arrow on someone's message and it replies to a specific message
'course, stars, transcript search, oneboxing are pretty important too
SE chat has enough generally-useful features that one would almost wish they'd make some kind of de facto standard around it, open source a reference implementation, and release clients for desktop and mobile... could probably pick up a lot of traction and eventually replace IRC
@flyingfisch It's 2014. How can you use a computer without having a web browser open constantly? The last time I would regularly close my browser to interface with desktop applications primarily must have been... I don't know, 2003? earlier?
@voretaq7 I don't know, IRC was always used IRC and XMPP as my standard protocols with pidgin, and my web browser is my web browser. That is just how I roll. I can live with this though, I guess.
@allquixotic firefox is a fine browser if you exit it at the end of every shift. If I leave it open (and actually use it) there's a noticeable release of RAM when I quit
my work PC (which really, really sucks; i3-2100, 4 GB of RAM; no, our management does not understand or value developers) has an uptime of about 2 months, and my browser has an uptime of basically the same, and Firefox is using 388 MB of RAM with 12 tabs open and I've made and closed at least 150 tabs today googling a problem I had earlier
@allquixotic I agree it would probably be useful, but unlikely to happen. No one in the company really works on chat anymore except to add internal bots.
HEY! IT LOOKS LIKE YOU'RE HAVING AN OUTAGE! HEY! IT LOOKS LIKE YOU'RE HAVING AN OUTAGE! HEY! IT LOOKS LIKE YOU'RE HAVIN AN OUTAGE! <...and then the chat server went down and clippy shut up>
On the other hand, since we're going to be working on adding chat to the mobile apps, it's possible a real API might come out of that... [pure speculation on the latter part]
scraping the DOM frontend does have some advantages: if you guys did a major breaking backend change, we'd have to rewrite probably less code than if we did everything at the HTTP layer
at least that's my justification for the existence of so-chatbot-driver ;-)
If it'll make you all happy, I will have a conversation with our main API guy about whether there's any rationale for why we would or would not implement a chat API.
Actually, I have to go. There's Manuary judging right now (female coworkers judging the male coworkers who grew beards out for January). I did not participate, but I'll go watch the competition.
@Lnafziger PHP, python, SQL, django I'm the sysadmin for a tool and die company but I also wrote the website and the job management software nothing fancy just keeps track of stuff and creates pdfs to print or email and tracking how much time we are investing into jobs. It's a small company, 6 guys, I basically am the entire IT department