Opkode - Blog


33 bookmarks. First posted by janezstupar march 2018.


Slack's bait and switch
march 2018 by f440
Slack, like so many others before them, pretend to care about interoperability, opening up just so slightly, so that they can lure in people with the promise of "openness", before eventually closing the gate once they've achieved sufficient size and lock-in.
chat  slack  business 
march 2018 by Gwendoux
Note: server doesn’t monetize your conversations ..
mattermost  openetc  from twitter
march 2018 by grantpotter
RT : Slack's bait and switch
from twitter_favs
march 2018 by eljojo
RT : Slack is lying when they say XMPP can't support the features they're adding. I've written a blog post about this:
from twitter
march 2018 by rjw1
Opkode – Blog
from twitter
march 2018 by jackysee
RT : Slack's bait and switch
from twitter_favs
march 2018 by sickill
Slack has finally decided to close down their IRC and XMPP gateways. True to form, you can only read their announcement if you already have a Slackaccount and…
from instapaper
march 2018 by dylan
True to form, you can only read their announcement if you already have a Slack account and are logged in to a workspace.
chat  cloud  hipster  irc 
march 2018 by pankkake
For the last few years I've been working in my spare time on making a JavaScript XMPP chat client, called converse.js. Originally the idea was to make a Gtalk like chat client that you integrate in your website
kb_cpu  web  library 
march 2018 by rootis0
Slack's bait and switch
chat  javascript 
march 2018 by lesbaker
Converse.js

For the last few years I've been working in my spare time on making a JavaScript XMPP chat client, called converse.js.

Originally the idea was to make a Gtalk like chat client that you integrate in your website, and it can still be used like that.
chat  slack  opensource  federation  XMPP  Javascript 
march 2018 by euler
'...We all know the real reason Slack has closed off their gateways. Their business model dictates that they should. -- Slack's business model is to record everything said in a workspace and then to sell you access to their record of your conversations. -- They're a typical walled garden, information silo or Siren Server -- So they have to close everything off, to make sure that people can't extract their conversations out of the silo. -- We saw it with Google, who built Gtalk on XMPP and even federated with other XMPP servers, only to later stop federation and XMPP support in favour of trying to herd the digital cattle into the Google+ enclosure. -- Facebook, who also built their chat app on XMPP at first allowed 3rd party XMPP clients to connect and then later dropped interoperability. -- Twitter, although not using or supporting XMPP, had a vibrant 3rd party client ecosystem which they killed off once they felt big enough. -- Slack, like so many others before them, pretend to care about interoperability, opening up just so slightly, so that they can lure in people with the promise of "openness", before eventually closing the gate once they've achieved sufficient size and lock-in.' -- New open same as the old open
internet  businessmodels  chokepoints  hackersvsvectoralists 
march 2018 by adamcrowe
Great article at about the sad state of messaging apps with a focus on the bad practices by…
from twitter_favs
march 2018 by dietrich
We all know the real reason Slack has closed off their gateways. Their business model dictates that they should. Slack's business model is to record everything said in a workspace and then to sell you access to their record of your conversations.
feedly  ifttt 
march 2018 by AnthonyBaker
Slack has finally decided to close down their IRC and XMPP gateways. True to form, you can only read their announcement if you already have a Slackaccount and…
from instapaper
march 2018 by joeybaker
All the more reasons for open, permissionless systems:
from twitter_favs
march 2018 by rukku
federated chat
arc 
march 2018 by mrbt
We all know the real reason Slack has closed off their gateways. Their business model dictates that they should. Slack's business model is to record everything said in a workspace and then to sell you access to their record of your conversations. They're a typical walled garden, information silo or Siren Server. So they have to close everything off, to make sure that people can't extract their conversations out of the silo. We saw it with Google, who built Gtalk on XMPP and even federated with other XMPP servers, only to later stop federation and XMPP support in favour of trying to herd the digital cattle into the Google+ enclosure. Facebook, who also built their chat app on XMPP at first allowed 3rd party XMPP clients to connect and then later dropped interoperability.

Twitter, although not using or supporting XMPP, had a vibrant 3rd party client ecosystem which they killed off once they felt big enough. Slack, like so many others before them, pretend to care about interoperability, opening up just so slightly, so that they can lure in people with the promise of "openness", before eventually closing the gate once they've achieved sufficient size and lock-in.
chat  irc  xmpp  standards  instant-messaging  blog-posts  business 
march 2018 by mikael