This is something that could go in the FAQ. If the answer is to post to a community on another instance, I never figured out how to do that.
If the answer is to create a magazine, what is the process?
Thanks.
This is something that could go in the FAQ. If the answer is to post to a community on another instance, I never figured out how to do that.
If the answer is to create a magazine, what is the process?
Thanks.
To get to another instance there is the “Magazines” link at the top of the page, or just go directly to the one you want such as https://fedia.io/m/[email protected]
To create a new one is under that ‘+’ icon at the top of the page. Looks easy but I haven’t tried it yet.
You can also hit search and type it in in the format @[email protected]
Also, someone has to subscribe to the community, or else Fedia won’t load data from another instance.
Oh, so I can get an existing community on another server to show up here by subscribing? That sounds ideal as long as the other server has decent uptime.
Searching macos or @macos doesn’t find that community on any instance unless I use the magazine search, which is under the hamburger menu.
I think if you’re searching you need to put the domain in too.
Magazine search is a bit different but will only show the communities already known to the server, the global search will find remote ones too.
I get a 404 for https://fedia.io/m/[email protected]
That appears to be a bug. I’ve seen similar problems before but never on an active kbin community. Maybe @[email protected] has some idea?
Searching on the handler should indeed find & create the user if not present:, eg. https://fedia.io/search?q=%40Gaeilge%40kbin.social However, fedia.io still seems to return “Empty”. I tried to do the same on my instance and that worked.
I’m not sure what goes wrong, assuming kbin.social didn’t block fedia, then I suspect some kind of issue at fedia.io. I believe we need to debug this issue on the server-side. Hopefully @[email protected] can have a look at his logs when trying to execute the search query above and maybe find the root-cause that way.
it is working for me as well. I’ll check to see if there was anything in the error logs.
ok - just looked through logs and I am not seeing anything that looks related to this issue. There are a good number of error 500’s coming from kbin.social, but none appear to be around the time of these posts, nor associated with the referenced magazine.
He user only now seems to exists (created 1 day ago it says): https://fedia.io/m/[email protected]. So yes it seems to work fine!
@[email protected] @[email protected] be sure you are logged-in before doing this search.
I thought I was logged in but I can’t remember now. I don’t see a 404 now though, just “empty”. There are posts in that magazine though, on its instance.
The search worked for me just now.