We're building something for the Fediverse. #Holos
ActivityPub running on your phone. Your own server, your data stored locally. A relay handles your stable identity when you're offline.
One account, all formats. Short text, long articles, photos, videos. The UI adapts to your mood. Switch between text mode, photo grid, video feed, article editor based on what you feel like sharing.
Same network, same followers.
Early stages, but the foundation is solid. We wanted to share the progress.
Franz Graf
in reply to Fedilab Apps • • •DNKrupinski 🧡🏴☠️
in reply to Fedilab Apps • • •Kāpitan
in reply to Fedilab Apps • •lime
in reply to Kāpitan • • •What if the feeds were also ActivityPub?
@apps
Kāpitan
in reply to lime • •@lime @Fedilab Apps How so? I'm thinking like Friendica handles feeds, I can follow them like I can follow anyone else on the Fediverse, so they just show up in my timeline, and I can quote it if'n I want to share it.
That and Diaspora compatibility are my two big must haves these days.
lime likes this.
lil5 🚲 🇳🇱
in reply to Fedilab Apps • • •@_aD
AGPL without CLA or it didn’t happen.
Fedilab Apps
in reply to lil5 🚲 🇳🇱 • • •GPL-3.0, no CLA. Working code, going public soon.
@_aD
Joe Vinegar
in reply to Fedilab Apps • • •@lil5 @_aD why not AGPL? whoever uses your code to offer an online service is not bound by GPL, while with AGPL would be obliged to provide the [modified] code to the user/customer.
By all means: your code, your time, your project: your rules. I'm just curious about the reasons behind the choice.
Felix 🐊
in reply to Fedilab Apps • • •Alex
in reply to Fedilab Apps • • •Soliman Hindy
in reply to Fedilab Apps • • •Andy Piper
in reply to Fedilab Apps • • •Furbland's Very Jolly Mastodon
in reply to Fedilab Apps • • •Fedilab Apps
in reply to Furbland's Very Jolly Mastodon • • •We'll work on PeerTube compatibility. Starting with standard Video ActivityPub objects, then adding PeerTube-specific features as we progress.
@peertube
Fedilab Apps
Unknown parent • • •No, the app and server run in the same process and communicate via bridge. C2S isn't needed here. The server uses S2S for federation with other instances.
🃏 su -
in reply to Fedilab Apps • • •jandi
in reply to Fedilab Apps • • •Arnel Šarić Sharan
in reply to Fedilab Apps • • •Ronan
in reply to Fedilab Apps • • •Ronan
in reply to Fedilab Apps • • •Epic Null
in reply to Fedilab Apps • • •Quokka
in reply to Fedilab Apps • • •Quokka
in reply to Fedilab Apps • • •beem
in reply to Fedilab Apps • • •Wachoperro
in reply to Fedilab Apps • • •🌬️
in reply to Fedilab Apps • • •Valdus
in reply to Fedilab Apps • • •saga
in reply to Fedilab Apps • • •🌱🏴🅰️🏳️⚧️🐧📎 Ambiyelp
in reply to Fedilab Apps • • •Oblomov
in reply to Fedilab Apps • • •Rokosun
in reply to Fedilab Apps • • •Can you expand more on the relay part? I'm curious how it deals with being offline.
Also wanted to say that I really appreciate you and the work you do, your projects are always pushing the boundaries of what's possible in the fediverse.
Mark Whybird
in reply to Fedilab Apps • • •Samuel
in reply to Fedilab Apps • • •Fils et Mailles
in reply to Fedilab Apps • • •Bonjour @marnic !
Je ne comprends pas. Ça signifie quoi au juste ?
C'est quelque chose qui signale si l'utilisateur est en ligne ou hors ligne ? C'est trop technique pour moi. 🥴
Que signifie Holos ?
Bonne journée 🙂
#Holos
To-ho-ho-bias Hellgren
in reply to Fedilab Apps • • •william.maggos
in reply to Fedilab Apps • • •the general user will only need a universal feed app for all formats, but I thought they'd be on servers based on locality. this might be better if we can prevent harassment.
we'll also need dedicated fedi servers for news outlets, governments, corporations, video production studios etc. and reader/player apps that fully embrace our social graph. and a decentralized fiat protocol to facilitate payments to creators based on the time spent with their work. #PublicPatron
JollyOrc
in reply to Fedilab Apps • • •got me curious - the company I worked at a few years ago had basically the same thing on the far-out roadmap (the main project was "let's have a private datastore on your device", social was more or less the add-on)
Will happily follow you!
Fedilab Apps
Unknown parent • • •@silverpill
Different architecture. Activity Connect bridges actors that can't communicate directly (blocked instances, different networks).
The Holos relay provides stable identity for mobile servers. Your phone runs the actual ActivityPub server, and the relay simply proxies requests to your current tunnel URL. It doesn't bridge or store content - just maintains a permanent address while your phone's IP and tunnel change.
Fedilab Apps
Unknown parent • • •@julian
User blocks always work, a standard ActivityPub.
The relay server handles infrastructure moderation (spam, abuse, illegal content). Your personal instance in the app is where you have freedom: choose who to follow, who to block, no admin deciding for you.
Moderation at the relay level, freedom at the personal level.
julian
in reply to Fedilab Apps • • •Re: We're building something for the Fediverse.
apps@toot.fedilab.app said in We're building something for the Fediverse.:
> Activity Connect bridges actors that can't communicate directly (blocked instances, different networks).
This... sounds potentially problematic at first pass.
We're building something for the Fediverse.
⁂ ActivityPub.Spaceygg
in reply to Fedilab Apps • • •I am very interested to see this project though.
Fedilab Apps
in reply to ygg • • •@emergencygg
Fair point! "Relay" in the Fediverse usually means redistributing public posts.
Ours is more like: identity provider, proxy and message queue. It relays traffic between the Fediverse and your phone, but you're right... might be confusing terminology.
Allan Haverholm
in reply to Fedilab Apps • • •Very exciting, will look forward to follow development updates at @HolosSocial.
This could dramatically lower the bar for owning your data, and for "self hosting" right in your pocket. It also raises the question of how end user friendly the relay server will be.
Are we talking a one-click install on commodity servers à la Wordpress, or something more involved like using Docker on a VPS? That will make a big difference in audience and adoption.