@kyzh with some good Docker templates being shared it shouldn't be much harder than eg. running Mastodon which by itself already runs several containers
It does have a repercussion on the sys admin level required to operate . As in, microservice interdendency is harder to manage than say a monolith application or a packaged stack. Historically that raises the bar of entry of self hosting.
For those capable it makes the going from 2-3 use ap serice to 10 an more easier tho.
@mayel My ideal is an open-ended, highly configurable design with an interesting set of defaults and a robust user community contributing templates or otherwise documenting configuration recipes. This comes from a game design space informed by *nix design principles, which is to provide simple primitives from which people can composite emergent behaviors
I think most fediverse apps would be better suited as frontend clients (or mobile apps) which can all connect to the same backend server (probably with some backend plugins or microservices to handle things like video compression).
One advantage would be having one federated identity where I can post toots, articles, photos, videos, events, educational resources, git merge requests, etc, etc, rather than having dozens of disparate identities and contact lists.
Clear value proposition, or infinitely customisable?
Slick or austere?
Strictly implementing one vision and set of goals, or adding all kinds of features that different people request or contribute?
Extensive user documented, or code and settings panels (or config files) as documentation?
Historically, the former tends to be proprietary apps, while the latter then to be free software projects that clone the intitial vison/functionality, and then evolve mostly by adding features. The complexity goes up and the UX goes down.
These days we have free software products (eg. Mastodon and Pixelfed) and free software tools (eg. Pleroma).
The question is how do you preserve the user-freedom advantages of tools while gaining the user traction and usability of products?
I suggest one approach could be having a generic backend tool, with standard protocol-based federation and an open API that enables frontend app designers/developers to create slick products that implement all kind of different visions and use cases.
Ğ1 est une monnaie libre, démarrée il y a 3 ans. Elle compte actuellement 2219 membres, qui produisent et perçoivent un Dividende Universel (DU), chaque jour.
I wish fediverse clients had a working petname based contact list type system so I could write down notes about people and give them my own names so I can actually contextually remember who they are
Especially a big problem after APConf, where now I just followed a bunch of people I really cared about the conversations of, and will have a hard time mentally mapping them to their online identities :(
1. SharedInbox is dead (look out for MultiBox and OcapsPub)
2. Strong interest to explore Object Capabilities as a way to secure social introductions, power delegation and transitivity, and to develop effective cooperation tools that prevent abuse in the #Fediverse
Some Chromebooks mistakenly declared themselves end-of-life last week
When your Chromebook or Chromebox approaches its built-in expiration date, it will warn you that it's time to go buy a new device entirely. Not long after that, it will refuse to apply any further security or feature updates. In addition to leaving users vulnerable to unpatched security exploits, this means that constantly evolving services such as Gmail will eventually stop working entirely.
Despite a persistent legend, the Chromium web browser is strongly tight with many Google services, and thus is *NOT* ungoogled. In /e/OS we are using a fully ungoogled Chromium web browser. On Linux, Mac and Windows, you can use "ungoogled- chromium": https://github.com/Eloston/ungoogled-chromium#downloads