rekoros

17 ms·

1. 151.▲
   by rekoros 10y ago

   It's a channel for every "conversation", not tweet. The benefit here is that you can keep talking to someone without asking them to email support@company.com. There is usually a window of open channels -- 15 or 40, say, that
2. 152.▲
   by rekoros 10y ago

   Twitter-wise, even better is to respond from Slack to tweets in real time with this integration — https://sameroom.io/integrations/respond-to-twitter-from-sla... [0] [0] shameless
3. 153.▲
   by rekoros 11y ago

   Updated to point to https://en.wikipedia.org/wiki/Multi-core_processor#Technical...
4. 154.▲
   by rekoros 11y ago

   We decided to only include cloud services, so we weren't sure what to do with something you have to run yourself. That said, the line is blurry, we will fix.
5. 155.▲
   Type-Safe Flux Architecture Using TypeScript(sameroom.io)

   4 points by rekoros 11y ago|0 comments
6. 156.▲
   by rekoros 11y ago

   That would be great - I can put you in touch if you're not already (andrei@sameroom.io).
7. 157.▲
   by rekoros 11y ago

   I think because it's a "nice-to-have", not a "must-have". (We have SMTP, a must-have.) There is no such thing as a "nice-to-have" universal protocol.
8. 158.▲
   by rekoros 11y ago

   There's a huge compliance problem with working in someone else's Slack team -- you own none of the resulting data and you don't control access on your end. Email is much better in this way, since everyone gets a copy. With Sa
9. 159.▲
   by rekoros 11y ago

   Thanks - will fix.
10. 160.▲
    by rekoros 11y ago

    We focus on connecting teams vs individual productivity. Check out http://meetfranz.com/ for a single app option. About getting fired - not if we sell our solution to your IT :) They might like it, actually, since they can
11. 161.▲
    by rekoros 11y ago

    Hi Andrey - we're not using spectrum.im or libpurple (but are aware of both). We saw that libpurple now supports Telegram, so we may borrow some ideas from them :) Thank you!
12. 162.▲
    by rekoros 11y ago

    Actually I don't think so. The main thing the owners of big networks are afraid of is spam. We provide a ridiculously expensive way to connect, say, Slack to Skype, which is ==great for Skype==, from almost every possible angle. It mea
13. 163.▲
    by rekoros 11y ago

    We implemented them ourselves, and it took quite a bit of work. Our magic weapon is Erlang, which is a wonderful language for working with protocols, and a wonderful runtime for working with many things happening at the same time. The other
14. 164.▲
    by rekoros 11y ago

    You can see what happens to OS projects that work with WhatsApp, Skype, and some of the other heavily guarded walled gardens -- cease & desist orders, carried out by GitHub. We have absolutely no interest in joining that list, which unf
15. 165.▲
    by rekoros 11y ago

    Thank you! We're so paranoid about getting shut down by Google (Hangouts, no API), Microsoft (Skype, no API), and Facebook (Messenger, no API) that we're not only not open sourcing any of our implementations, we're not even p
16. 166.▲
    by rekoros 11y ago

    Here's a timeline we put together of about 60 incompatible chat services: https://cdn.sameroom.io/chat-timeline.pdf Our service Sameroom ( https://sameroom.io ) is a commercial solution to the chat incompatib
17. 167.▲
    Help Me Understand the Value of Slack Instead of an Email List(feld.com)

    2 points by rekoros 11y ago|0 comments
18. 168.▲
    What We Learned from Sponsoring an Open-Source Developer for a Year(medium.com)

    3 points by rekoros 11y ago|0 comments
19. 169.▲
    Salesforce--Team Chat(s) integration(sameroom.io)

    1 points by rekoros 11y ago|0 comments
20. 170.▲
    by rekoros 11y ago

    Just a note that you can use any other client supported by http://sameroom.io to connect to Skype. https://sameroom.io/attend lets you auto-create Slack channels for each incoming Skype conversation. We have som
21. 171.▲
    by rekoros 11y ago

    For syncing between [some] real-time systems, check out https://sameroom.io
22. 172.▲
    by rekoros 11y ago

    In a busy market, distribution is king. It's hard to get your name out there. Speaking of unknown players in this space, check out the wonderfully minimalistic updown.io. It's much cheaper than SP and really is quite good. Here&#x
23. 173.▲
    by rekoros 11y ago

    Will it work with https://sameroom.io ?
24. 174.▲
    by rekoros 11y ago

    Sameroom - REMOTE - full time Sameroom ( https://sameroom.io ) is chat interoperability-as-a-service. We need help with all the goddamn emoji. https://sameroom.io/blog/wanted-sr-emoji-engineer/
25. 175.▲
    by rekoros 11y ago

    But how would you deal with losing history? 10K messages is not very many. I've been using gmail/gtalk for ~12 years -- I can quickly dig up (and regularly do) pretty much anything my parents and I ever talked about. I consider t
26. 176.▲
    by rekoros 11y ago

    Bad word choice on my part. Didn't mean "proper" as in "correct", but as in all-in, no-looking-back.
27. 177.▲
    by rekoros 11y ago

    Before Sameroom [1], we spent two years building Kato ( https://kato.im ), which became a Slack competitor once Slack launched. We did enjoy a brief pre-Slack honeymoon (at Techstars, no less). For a few reasons, we chose Xamarin
28. 178.▲
    by rekoros 11y ago

    Hey - thanks! Proper TypeScript usage is still pretty rare, so this felt OK. As a startup founder, if you have a choice between telling people about your startup and not telling: tell. This is incredibly hard for engineers, but you just hav
29. 179.▲
    by rekoros 11y ago

    TypeScript is amazing. We decided on TS to build https://sameroom.io and never looked back!
30. 180.▲
    by rekoros 11y ago

    What will happen to the archive? Also, do you mean team (vs. channel)?