Discussion
Hi @misterdubs, I found your fediverse service on the list here;
https://forte.eenoog.org/instances?project=coresignal
Coresignal.podmoodle.nohost.me looks like a Bonfire instance, but it's not on the Bonfire list here;
https://forte.eenoog.org/instances?project=bonfire
Is CoreSignal a fork of some kind? Or has @Bonfire maybe got some issues with its NodeInfo implementation?
@misterdubs
> It is definitely a Bonfire instance and not a fork
Thanks for clarifying. Would be good to know why it doesn't seem to be identifying itself. Have you/ your admins ...
@Bonfire
> customised the APP_NAME environment variable
... as the Bonfire devs guessed?
@strypey@mastodon.nzoss.nz @Bonfire@bonfire.cafe
I have not modified the APP_NAME environment variable.
This is a vanilla install of a Bonfire instance. However, it is hosted on Yunohost.
@misterdubs
> This is a vanilla install of a Bonfire instance. However, it is hosted on Yunohost
Hey @yunohost, can you think any reason this instance is identifying itself (presumably over the NodeInfo endpoint) by its domain name, rather than the name of the actual software it's an instance of?
@strypey@mastodon.nzoss.nz they've probably simply customised the APP_NAME environment variable.
Install bonfire.cafe
Get the full app experience
@strypey@mastodon.nzoss.nz @Bonfire@bonfire.cafe It is definitely a Bonfire instance and not a fork. I can't comment on the NodeInfo implementation. Sorry!