All jokes aside continvouclious development is all the rage these days.
S
smallcircles@social.coop
@smallcircles@social.coop
Posts
-
When I was in my early twenties I read The Visual Display of Quantitative Information from Tufte and agonized over making charts great for users. -
After shutting down #HolosDiscover, we're rethinking the approach with #HolosIndex: users explicitly opt in by adding #HolosIndex to their bio with interest tags, then submit their profile.I also like the Follow approach best.
Follow the HolosIndex bot gives explicit consent "please index my public posts". HashPub by @evan follows a similar method, and also https://anagora.org by @flancian works on that basis. Give a nice acknowledgement after the follow request, and perhaps an unfollow removes you from the index again.
I find this a better mechanism than the magic hashtags in profile approach, where there's already tight charlimit in many apps for the intro. You also have (or had) this with https://fediverse.info when adding #fedi22 to ones profile.
-
I'm curious what other devs think about this.Btw @HolosSocial I really
love the clean documentation style of your "How it works" page, to outline various use cases. Great work! -
I'm curious what other devs think about this.Yes good to mention, I was out of chars. It becomes I guess like a local-first S2S on the client-side, tied to compliant Relay servers that facilitate the tunnel.
Perhaps @HolosSocial can enlighten us for their project, but such a set up should not necessarily bind to a single client.
-
I'm curious what other devs think about this.Yes, I would highly discourage the use of "app". It is why I scare quoted it, but "app" is common language when people talk about the fediverse. "App" is a neat container concept that fits the full scope of ones own FOSS project, but on the fediverse - a growing heterogeneous and interoperable social network - one becomes highly dependent on the foundational network communication layer based on #ActivityPub, and any fedi FOSS developer should be concerned beyond direct project scope, and pay attention that this foundation evolves healthily. This unfortunately happens unsufficiently, and only a very small number of people try to get the ecosystem as a whole to higher levels, volunteering time where it does not directly benefit their own projects. Think @silverpill for the #FEP and @evan for #SocialCG.
Cool find yesterday was that @HolosSocial rather than C2S has a "full AP server" client-side, that communicates with a Websockets tunnel to a dedicated relay server.
-
I'm curious what other devs think about this.Keeping msgs immutable is a general best-practice, I gather.
In the case you mention it becomes confusing to still use client/server terminology. You have a full actor on the client's side, and when it sends a msg it acts in server/S2S role.
Btw, in that scenario we do not have to make the distinction client + server anymore, as we have just actors communicating with each other. Then we can think in terms of the actor model, and honor its qualities.
A client sending to the server's outbox is then analogous to an actor sending to another actor's inbox. That is a one-way msg exchange usually, fire and forget (esp. in a pure event-driven architecture... which the current fediverse is not). The remote actor is not responsible for keeping the Activity (event) in its server-outbox / actor.inbox. That corresponds to the spec part "may disappear at any moment".