Wrote up some thoughts about @takahe and a refactor/redesign I'm doing, with the aim of more customisable profiles and proper domain separation: aeracode.org/2023/04/29/refact
(also, maybe we can support BlueSky/AT as well? Who knows!)
Wrote up some thoughts about @takahe and a refactor/redesign I'm doing, with the aim of more customisable profiles and proper domain separation: aeracode.org/2023/04/29/refact
(also, maybe we can support BlueSky/AT as well? Who knows!)
@andrew @takahe All of that sounds great! Definitely will be following the progress.
> In addition, all of this will be built on a somewhat-extensible plugin system, so that if people have ideas they want to explore on the Fediverse, they can do so without having to author the majority of a server themselves.
Probably the most exciting part since it's a lot of work to re-invent the base activitypub for each new project (especially if existing implementations are not in your 'chosen' language.
@andrew @takahe Love this direction!
Sounds quite similar to what I've got in mind for my 'Weird web pages', except yours is more of an all-in-one (dynamic app) approach whereas we're starting with a lightweight (static, local-first) aggregator.
> from my reading of its design docs, I believe Takahē should be able to support both AT #bluesky and ActivityPub at the same time.
Very excited to see where this goes! I'm hopeful Elk will join the fun: writing.exchange/@erlend/11028
@mull It will be less heavyweight than Mastodon, that's for sure, but I don't know if it would be overkill or not.
Out of curiosity - what would drive you to set up a single user instance if you could still have your own domain and theming on a shared one - the ability to control your own moderation?
@andrew The main reason would be control. If the admin of a shared instance decides to “unplug” the server for any reason and suddenly, I'd lose my data, including my followers. I'd like to maintain that ownership and control.
@andrew @mull To me a big part of why I probably would like to run my own instance even in Bluesky is URLs. Every content would have an URL to my server.
If you want to host your content and control how its first-party presentation is done, that's a big deal.
Also, it would allow me to use Mastodon's long-form content and HTML formatting as a blogging platform. Send to Bluesky just a title and link. (Assuming it doesn't support long-form content.)