@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 I really like this direction! Offloading timeline to external apps is a great idea. I’m also happy that you’re open minded about Bluesky.

Do you think @takahe, when ready, would be an overkill as a single-user instance?

@andrew @takahe oh I'm excited for this! I've been waiting a while for someone to do home page functionality

@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

@andrew @takahe really interesting i will try asap and i will follow developments very closely! One question: is it possible, or it will be possible, to migrate an already running Little mastodon instance?

@andrew @takahe This makes me so excited! I'm willing to give up my single-user Mastodon instance in favor of this. I'm using Elk everywhere now, so on the surface, not much will change. But I really want to support this vision, and using Takahe for instances with friends.

Keep rocking!

@andrew @takahe @fediversereport FYI!

@andrew @takahe
A solid plan and good ideas. 👏

I'm currently hacking together something to achieve a single user version of this web presence idea by installing a modified version of gotosocial alongside my static website.

Plugin system sounds a real boon too. Exciting stuff.

@Sampei @takahe No - content and account migration from Mastodon is still something in future plans.

@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.)

@mull Got it! I do hope this is something we can overcome in the protocol eventually (I have some ideas!), but it totally makes sense.