Stream-Framework VS wire-server

I have looked into a getstream.io integration, however it seems that the Ruby SDK is really treated as a second class citizen. There's bugs with the documented API (I'm having issues even creating users and querying users), the usage of the gem is low and there is an open issue since May that no one has even looked at, which doesn't give me hope for long term support.

An ultralight social media app with no dependencies that can run on shared web hosting. It's an API like Getstream, so F/E is up to you. I've had a fork of it in production for 2.5 years on a subscription site that generates a small income.

Now, I'm seeking your advice and opinions. If you have experience using Stream or MirrorFly for chat implementation, I'd greatly appreciate any insights you can provide. Here are some questions I have:

Think about the edge that you can have over thousands other people looking for a job like you. One of the ways to do it – tailor your (even small) experience to the company you are applying to. E.g. Let's take a company like Stream that have an open-source Swift SDK, try to contribute to their SDK, maybe close some `good-first-issue`s here and there, do some documentation improvements, enrich their example app. So that when you feel like you are ready to knock their door – you already have an edge over others – you don't need onboarding (because you already know most of their codebase, you even completed your first few tasks while yet not being employed!)

This is absolutely absurd. I mean I 100% believe it happens, it's just absurd that the Tier 1 admin bot is this bad.

I too firmly believe the tier 1 admins are just this program - https://getstream.io/ And reddit doesn't want to admit that humans are not actually reviewing things

Really depends on so many variables, and comes down to knowing the audience. I built a lightweight social network api platform to do a lot of what getstream.io and OSSN does, but the way users engaged with it was nothing like what I expected. One use case, for example, would have been mostly satisfied with WordPress and Mailchimp. Forums are very familiar to people and still used by a lot of "I don't do social media" types. At the risk of making a sweeping generalization, if you have an older target audience they will be happy with a forum. If you have a younger target audience they will prefer the sequential post / react style of interacting, like Discord or Instagram.

Use encrypted messaging apps. Several apps allow you to connect with others securely if you're using a smartphone. These include Signal and WhatsApp (both owned by Facebook), as well as Telegram and Wire (owned by Google). These services use end-to-end encryption, so they don't store any data on their servers or share it with anyone else.

For work each service it its own cabal project, and has src/ (the service) and test/ (in 3 styles)

Codes here: https://github.com/wireapp/wire-server

Haha. I stated using reddit after finding it when wire.com. Back in the day the top 10 reddit posts would show on Wire. This was around 2006/07. I specifically remember there being a science. You made me think, maybe I'm losing my mind so I checked into it. Sure enough there is a timeline available. Here is a 2007 accolade for r/ science, " For most of the year, "science" and "programming" are the most popular subreddits. I like the info for year 2008, "This year is dominated by the launch of numerous new subreddits." I do appreciate how confident you were in your incorrect answer though. You are probably a Digg.com refugee.

Is there any way if I self-host element, I can make it completely private? like somehow to remove the explore room option? like the users can't join any public room kind of what rocket chat does. or even wire.com. is it possible ? i want to make it completely private for the company

Also, I use it for my work @ https://wire.com

The backend of Wire messenger, with the server code publicly available in the company’s repository and detailed documentation, also written in Haskell.

The Client is GPL-3.0 Licensed. (WebApp,Desktop,iOS,Android) The Server is AGPL-3.0 Licensed. Both Client and Server are Open-Source.