alovoa
alovoa copied to clipboard
Alovoa
ActivityPub support
Decentralization is a nice to have feature, and ActivityPub should be used for that.
Definitely need help for this one, I don't know anything about decentralized systems.
You might get some help on this on socialhub (there is a forum about how to implement it).
the lemmy community also has some resources on the sidebar.
General question about connecting to other federated servers: Wouldn't that imply that I (or they) have to send all user data to other servers? If not, how would a user search work?
I would like to point you in the direction of the SocialHub community for technologist that drive the fediverse standards and evolve the ecosystem. Would be great if you interact here, and you can also get a dedicated section for your project if you implement activitypub. I am moderator on the forum.
For general brainstorming about what's possible with Federated Dating you can use the Fediverse Futures category, and to go wild and non-technical there's the companion Fediverse Futures on Lemmy.
Since Dating is a new application domain, it is of particular interest to the community. Another new domain is Hospitality Exchange. What all these domains have in common is that AP extensions may be needed, and there's a common design process that we'd like to explore to tap deeper in the potential of the AS/AP specs (we only touched the surface with current, mostly Microblogging apps).
On the forum you'll also find the Guide for new ActivityPub implementers with many references to more info.
Besides that I also co-maintain 2 watchlists that are useful to you as input:
(PS. I will copy this comment to the Lemmy post where I heard about your project, and will also add you to the AP apps watchlist)
Update: You were added to the Other category on the application watchlist.
What are the features, that should be supported by activityPub? @aschrijver do you have an idea? What activities and what objects should be federated? Is it just about posting things to the federsive or should the app be an activityPub App and two or more instances should interact with each other?
I have no idea @naturzukunft just came upon this issue. But there are interesting opportunities.
One would be where anyone could spin up their own Instance and become part of the larger federated Dating network. They might give their own instance an unique twist making it interesting for specific groups to join a particular instance. Dating Profiles might federate across whitelisted instances and only be visible to its member. Privacy should be quite important and personal exchanges should be private, maybe even to admins (though that may facilitate abuse, it's a tricky thing, but interesting to consider).
There's a lot of commonality to some of the issues that the Federated Hospitality Exchange movement has to solve, i.e. Guest + Host exchanges are private, PII (addresses) are too, and Guests and Hosts need to find each other based on certain criteria (Metadata search?).
The TrustRoots platform has the concept of 'Circles' and their theme (e.g. 'cooking') might span multiple instances, which is interesting, as an actor (e.g. as:Group) is tied to a domain name via its ID. Alovoa may have a similar concept, where e.g. LGBTQ+ are separate groups. Maybe "Community has no Boundary" offers solution here. There may be nested groups, e.g. people flocking together within the larger umbrella 'Queer' or XYZ-topic groups.
What may be cool, besides 'mindlessly swiping profiles' is to offer safe social spaces where groups of people discuss together and get to know each other in other than 1-on-1 context. Might be done with local-only posting, such as implemented in Hometown.
In FediHospEx we create these simple models of how current platforms work to find likely candidate concepts for federation. See the summary wiki post for that and this website page.
Update: I cross-posted this comment to Fediverse Futures on Lemmy (the federated Reddit alternative).
;-) ok, so the first task will be "find requirements" and the next step "break the requirements down in implementation tasks and milestones". a lot of work. I'm working on an activityPub Implementation, that is some kind of generic. It very in the beginning, but maybe other projects can use it. For now it is still closed source, but i hope it will be open source in the next months. Currently we talk about the seperation of the main activityPub Modules out of a bigger maven multi module project. that will be an advantage. It's based on rdf4j. The main focus at the moment is C2S but i plan to do some S2S stuff as sone i has free time. (maybe this will be autumn)
I would be very much in support of a connection to ActivityPub. What would be necessary in terms of professional, organisational competences and human resources to push this connection?
TL;DR: How can I help?
And Matrix support, both could be made possible thanks to https://gitlab.com/kazarma/kazarma
