Couple of questions regarding the project

[alexpdp7]

Hi!

I started using Takahe a while ago, because I was really attracted to its unique ideas. But now I'm considering a move to Incarnator. I have multiple questions- in general I would think it's bad etiquette to cram them in a single post (and outside the Q&A section!), but I think it might make sense.

These might look like I'm "demanding" a "massive investment" in Incarnator- I am not; I realize during the last year, there have been 26 commits by two Git users... I just think the multidomain idea in Takahe/Incarnator is awesome, I like Python/Django and more diversity in the ActivityPub ecosystem would be great. (Unfortunately, I have to sing the classic tune of not having enough time to commit to walking the walk :(

• What is the policy wrt. to updates from Takahe to Incarnator? Is it a "bug" if I just switch my deployment from the latest available Takahe container image to the latest Incarnator image and it doesn't work? If it is expected to work, perhaps the README could note this?

• I see that every push to the main branch results in a new image published to Docker Hub with the edge tag. Is there any public instance tracking this tag closely, such as https://alpha.incarnator.org/? Maybe the README could have a small text about that? For me if Alpha (or any other instance) tracks edge, and someone checks it after a commit is pushed, that is more than enough for me to adopt Incarnator. (I can also check Alpha before updating my instance, etc.)

• Would it be OK to promote Incarnator? I'm thinking just mentioning I use it, perhaps adding it to some "awesome ActivityPub" lists, etc.

Cheers,

Álex

[alphatownsman]

I upgrade a while ago. relatively painless imo.

[dcwatson]

Yes, I expect that updating from takahe/main to incarnator/main would work - this project was a fork that kept the existing migrations.

It sounds like a lot of this feedback is really just asking for a much better README, which I both wholeheartedly support, and also have not had the time or motivation to do 😁 My original plan for this project was to bring it back into Takahe mainline, but Takahe has since become unmaintained. I think before I fully break from Takahe and do my own README, docs, process, etc. I'd like to touch base with Andrew to ask about perhaps just merging this back and taking over the project. I honestly don't know if his preference would be for it to live on with different stewards, or just let new projects bloom from it.

You are certainly welcome to promote incarnator if you'd like. My own goals for it are selfish - just to have something I can host myself - but I certainly welcome feedback and contributions. Making it better for others will make it better for me too 😁

[alexpdp7]

Yes, this README would be enough for me:

Incarnator is a fork of Takahe. Switching from Takahe to Incarnator should just work.

https://alpha.incarnator.org/ is updated to the latest edge container image after the image is created.

You can open issues if https://alpha.incarnator.org/ is broken or if updates from Takahe fail.

Concerning the publicity, I don't think there are so many Takahe instances out there- and no matter what, it is unlikely that there will be a huge influx of users... but you know, it's plenty reasonable to want a hobby project to remain a hobby project :)

I'd be all in favor of assimilating Incarnator into Takahe and updating ownership. But really I should not have a say on the matter :)

I guess I'll wait a bit and when I have some spare time I'll update my deployments and see what happens!

[alexpdp7]

alexpdp7/alexpdp7@014d31d

My way to run the migrations is not working correctly and I had to fix things manually- but other than self-induced problems, the switch was seamless as expected.