Fork me on GitHub
#off-topic
<
2020-06-15
>
emccue02:06:27

I really don't understand how to use zulip

6
plexus09:06:40

same here. tried a couple times, just can't get used to the UI

sova-soars-the-sora12:06:23

everything requires a Topic before you can post anything -- although there are apparently rooms called "Streams" that resemble a chat room.

sova-soars-the-sora12:06:44

replying to a topic just nests it there, like the subthreads on slck

seancorfield15:06:34

Streams = Channels, Topics = Threads, every new discussion is a thread (topic) which keeps streams nice and organized (rambling discussions in channels is a problem here, that is alleviated by people using threads more).

emccue02:06:34

i get straight confused constantly

p-himik07:06:01

Just to expand a bit on the reasons why people don't want to use Zulip - a few people (a different community though) told me that they tried it and made a decision to go with Slack simply because they use Slack for other communities, and they don't want to keep two apps/tabs open when they can have only one. I myself have tried a few apps that aggregate different IM apps. None worked great, and all just wrapped the web versions which sometimes can differ, sometimes significantly.

mpenet07:06:06

riot/matrix has a quite impressive bridge for IRC, I suspect for slack it's quite decent too. I guess that could make a soft transition possible or just let people use whatever ui/backend they like (slack/riot/<whatever>) in the long run. One of the channel I am on on riot uses the irc bridge, the discussion between people on both platform is transparent you basically do not notice who's on freenode and who's using a matrix server.

sova-soars-the-sora12:06:23

everything requires a Topic before you can post anything -- although there are apparently rooms called "Streams" that resemble a chat room.

sova-soars-the-sora12:06:44

replying to a topic just nests it there, like the subthreads on slck

naomarik12:06:48

So will the new Mac ARM CPUs affect all the development tools we're all using?

sova-soars-the-sora12:06:57

maybe, does the kitchen change what silverware the restaurant uses? sometimes even though they need not

Mno13:06:12

All of this talk makes me dream of a world where chat apps are just the UI and you can subscribe to message groups. Kinda like the whole LSP and IDEs situation.

❤️ 3
Mno13:06:08

So you could use the client you like the most as long as it had a Messaging Server Protocol implementation.

mario-star 3
dominicm14:06:29

The problem is that zulip & slack are at odds with each other. You can't translate slack messages into zulip reliably, because they're not organized in the same

dominicm14:06:37

discussions aren't threaded how zulip likes them.

ec19:06:25

What kind of DB makes the most sense for storing kafka messages to play later? Timestamp, Topic Name, Msg serialized as binary blob will be the only things that stored. Only query will be, fetch these topics in this time interval. InfluxDB (suited for timeseries metrics but could work here too), Mongo, Postgres? Something that highly available, fast writes, and good compression is seems to be what Im looking for

Daniils Petrovs20:06:57

We use Cassandra in our company and it has been working pretty nicely for us.

Daniils Petrovs20:06:35

Postgres is also a solid choice for something a bit simpler.

emccue00:06:49

I also used dynamodb

emccue00:06:29

but truth be told, kafka does that already to an extent just not in a persistent way

drewverlee01:06:38

If you know ahead of time what the interval will be, then a streaming solution like spark, onyx, kafa streams would be good. Otherwise a time series database like influxdb. Not mongo.

ec16:06:23

thx for the answers