Finding people, companies and references is most crucial for a professional social network.

Here is how we plan to tackle this for Flockingbird: Decentralised and Privacy-friendly:

@flockingbird Doubt this would support the way I used LinkedIn: make connections and look them up when following up. Very common.m

I often land in new groups/contexts with no connections yet and this approach would make finding the first connection very very hard.

Connecting should be super lightweight, discovery easy. A public (slow?) search spanning many many instances might help? Perhaps allow many 'local' contexts (eg: a conference, organisation or topic) rather than one?

@madnificent As for connecting, that is a good subject for another post. I'm sorry if the blogpost implies that searching is the only way to connect.

I'm not sure if I understand your comment about it "making finding thefirst connection [..] hard". Do you mean that without groups, discovery is hard?

Geographic, or local discovery is a neat idea, It's on the list now. We need to think this through very well, though, because it also is a potential privacy nightmare.

@flockingbird It's easy talking from my lazy chair, but the search problem is hard.

The first connection in a new group would be very hard to find. You most often find people by name, not because they shared their URL (especially so when the network is still smaller).

Regarding privacy: it could make sense to *choose* to make some info publicly available perhaps?

Regarding "local": I'd want to be on multiple federated instances in an integrated way. I cater to multiple groups. 🤔

@flockingbird Makes sense. Especially because it's something we'll have to experience and try.

Really appreciate the work you're putting in this and can hardly wait to try it.


@flockingbird PS. your git is currently unavailable:

"The site at has experienced a network protocol violation that cannot be repaired."

(trying with FF/ubuntu from NL)


· · Web · 1 · 0 · 0

@humanetech Thanks for the headsup. We really need to migrate this server to caddy. Let'sencrypt and Nginx are an unfortunate combination.

@flockingbird have heard good things about Caddy.

Nginx + LE may work fine, but are a bit of a hassle to maintain and such, especially when having multiple services behind the proxy.

@humanetech in our case it's cause by our Ansible which needs to be generic and support provisioning of new services on -indeed- a shared nginx as well as updates an also -in the case of gitea- somewhat customised nginx configs.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!