OSSN VS Stream-Framework

GITHUB Page: https://github.com/opensource-socialnetwork/opensource-socialnetwork

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.

I liked Open Source Social Network (OSSN). https://www.opensource-socialnetwork.org/

open source social network might be something worth looking into.

Just throw up something like https://www.opensource-socialnetwork.org/. Why build it all from scratch?

I have heard of OSSN, which is basically the same thing? Except from what I understand instead of it being one big social network, its like a skeleton to build your own community, which runs into the same issue (no users). Also, it's written in PHP (ew). I could be wrong about the function, I haven't personally delved into it. I think if I had to give an answer on whether or not I would use it, it would entirely depend on how specific of a topic and how active the network is. I think personally, there's really not anything I couldnt do in a discord channel that I could on some social media site, especially after learning how to write a few bots for whatever channel or group I want/am a part of. I can join a discord group for practically anything, and just have more options to do stuff, compared to something like facebook or reddit,.

I really like the interface of OSSN, but I see that Hubzilla and Diaspora are both part of the Fediverse which seems to be widely liked and used, which makes me feel better about the longevity of such a product.

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.