Time to set up an IRC server again then. Sigh.
Slack Is Buying HipChat from Atlassian
591–600 of 730 posts
Re: Slack Is Buying HipChat from Atlassian
#592Slack is best of the breed - all history search, easy code blocks that i cannot yet figure out how to in Hipchat, pictures, files.
Electron is big and bad, is it phoning back to Google? but I can understand the savings.
Hipchat have an UI, that looks like a joke, after using Slack, but on-premises, offline installs are very important for company security.
I guess Slack bought it just to kill it. No offline stuff in 2018, folks.
Re: Slack Is Buying HipChat from Atlassian
#593Earlier quoted context omitted.
Those aren't slack problems, those are people problems. I can just as easily point to email threads that are incoherent and hard to follow. I can also point to meetings with no agenda that waste everyones time but give the appearance of 'managing' or team building. When used properly (not lazily), Slack is a great place to organize communication between teams. At worst its Skype with a way better UI...what's wrong wi…
Better than "Skype with a way better UI". * it has a history I can actually search. Skype used to have this, but removed it when they rewrote it in Electron. !@#$ you to whoever at Microsoft decided to get rid of that; I used chat history search every day as part of my workflow. * it has an API/plugin ecosystem. Admittedly, that's a walled garden so it's a double-edged sword. But for businesses that's awesome . Skype…
Oh, it has history... in Outlook, that's like Edge saving your bookmarks in Excel kind of absurd.
But I agree it works like shit, half the conversations aren't there and I can't figure out a pattern or why.
Re: Slack Is Buying HipChat from Atlassian
#594Earlier quoted context omitted.
> Confluence which lead to out dated, subpar and incomplete documentation. How exactly is it Confluence's fault if your team does not update the docs?
Confluence's editor is truly awful. I've spent 15 minutes just trying to remove superfluous newlines -- it's maddening. If you do something like {{fsck}} to create a bit of monospace text, it's totally unclear if there is a space after the text, or there isn't, due to the way the reverse video section is larger than the actual text. God help you if you accidentally backspace into the monospace section, everything you…
> I've spent 15 minutes just trying to remove superfluous newlines
I find that hard to believe but have reported it to Atlassian?
If all the problems which have mentioned are true why not move to something else?
Re: Slack Is Buying HipChat from Atlassian
#595Slack is still to expensive :/ this merge will not help.
What we need is self hosted app like Rocket Chat, which is not the best software on the market but it's the best solution for new companies to start with something inexpensive.
Re: Slack Is Buying HipChat from Atlassian
#596Earlier quoted context omitted.
We use Slack now, and are looking to migrate to Mattermost (since we run GitLab already). We don't want to pay the price we'd need to pay to keep Slack, and plus we want to host our own.
We moved from Slack to Mattermost, and Mattermost is garbage. Messages are delivered late (by hours), if ever. You don't get notifications correctly. It takes seconds (more than 10 sometimes) to load a page. Sometimes the page goes blank. Much of our office has reverted to email and phone calls for many things that would have worked fine with Slack.
We had a similar experience (moved from IRC to Mattermost). We're on Matrix now, running with no problems.
Re: Slack Is Buying HipChat from Atlassian
#597Hey all here, So I observe that lots of team chat users seem lost and don't what to do anymore. The problem with alternative Open Source team chats attempts is that they are just another silo, or walled garden. Instances do not talk to each other. A private island cannot join continent. Even within the same organisations plenty of incompatible team chats are used competitively, fragmenting the workforces. We propose…
Echoing Promarged, the world class UX claim had me searching for screenshots, not having any was a major turn-off.
I understand.
A complete and comprehensive UX is not seen in a few screenshots...
Re: Slack Is Buying HipChat from Atlassian
#598Hey all here, So I observe that lots of team chat users seem lost and don't what to do anymore. The problem with alternative Open Source team chats attempts is that they are just another silo, or walled garden. Instances do not talk to each other. A private island cannot join continent. Even within the same organisations plenty of incompatible team chats are used competitively, fragmenting the workforces. We propose…
Sounds nice, too bad there are no screenshots so I can't see what does it look like without giving my e-mail. Does it run on an open protocol? (Maybe HTTP or XMPP based?)
That is right, I "exchange" screenshots against feedback, on a live interaction...
Yes, it runs on XMPP and SIP and WebRTC, and obviously HTTPS (because what does not?).
Re: Slack Is Buying HipChat from Atlassian
#599Huge problem for on-prem Hipchat customers. Plenty of customers out there not willing to put all their internal communications on the other side of their firewall, and now have to migrate. Slack doesn't have an on-prem option. Microsoft Teams doesn't have an on-prem option. What are enterprises supposed to use, RocketChat? Matrix? With no clear migration path? Really poor move on Atlassian's part. It would be one thi…
The customers of these on-prem options are themselves developers, what's stopping them from forming a consortium and building a free software alternative themselves?
It should be simple enough, since you're operating on a negligible scale when it's on premise.
Re: Slack Is Buying HipChat from Atlassian
#600Earlier quoted context omitted.
Why is you current solution so ressource hungry? I mean, my 10-active-users off-the-shelf XMPP server (ejabberd) uses about 100MB RAM currently.
a 10 active user Synapse should use about 1GB max, so unsure what’s up with the earlier post. The reason it’s currently so much heavier than XMPP is that resource usage scales with the size of rooms being participated in, not the number of connected users - and we aggressively cache those rooms in RAM. However, 100MB is a much more sensible target and we’re busy optimising to try to shrink things down.
Maybe you want to see the preview of our work in progress? https://nayego.net/ Open Source, real Open Standards, mature technology, decentralised/federated/distributed, and a great UX.
Fit for orgs with external partners, providers, customers, freelances, remote and home office workers...