@baris In fact, all of the plugins that are shown have this warning:

This plugin has no compatibility data, make sure it works before installing on your production environment.

So especially for a beta, also (optionally) showing ones that have compatibility data but don't include the latest version could be useful and could be labelled in a similar way.

@baris Ohhh ok. Thanks for investigating! That makes sense, but also maybe it would be good to be able to disable that filter? After all plugins could be compatible but not have been updated to specify compatibility. It could show a warning that the plugin isn't known to be compatible.

And yes, it works!
It's certainly unintuitive but that's fair enough for a work in progress!

It doesn't appear in the recent posts for that category (it was an empty category and still says "no new posts"), but that's a minor detail.

Ahhh! So (ignoring the discovery aspect) if I were to paste a remote post URL into the search and open it like that, then "move" it into a local category, that would work as a boost? I'll have to try that!

Ok, found the problem. It only works with the privilege guests / View Users enabled. I had fediverse / View Users enabled anyway but that wasn't enough.
I'm not sure if that's intended? I guess it makes sense in principle…

Could it be a Cloudflare proxy issue?
I also just tried from the server:

curl 'http://127.0.0.1:4567/.well-known/webfinger?resource=acct%3Acaesar%40forum.rewild.pt'

And it still gives me Bad Request. But then, maybe that's because of what you said about the domain not matching…

My mistake, I was logged in as a test user in my private browsing session
It's working only when logged in, otherwise it's giving the 400 error. Any clue why that would be?

(No, nothing in /etc/hosts.)

@julian said in v4.0.0-beta.1 bugs & issues thread:

Actually, I cannot open that URL at the moment. I also get a 400 Bad Request

Hmm, that's odd. I've tried from a private window and it still works for me. It's conceivable I was restarting nginx after trying a different configuration when you tried it, could you try again?

Check that url in config.json is forum.rewild.pt. If it does not match, the webfinger controller will throw a 400.

It's https://forum.rewild.pt. Should that work?
I tried changing it to the bare domain without the https://, but I got an infinite redirect loop.

I suspect it's a misconfiguration on my part rather than a bug, but webfinger isn't working on my new install of v4.0.0-beta2.

I'm getting a 400 error – see https://browser.pub/@[email protected]. However I can open the webfinger document manually in the browser without issues, so I'm guessing it's a CORS issue – but I'm not sure what I should change in the NodeBB settings to make it work.

I don't see any mention in the docs of anything I need to do specifically to make webfinger work – any suggestions?

Question: what then is the "approved" way of installing common / official plugins like nodebb-plugin-sso-facebook, given that the docs explicitly recommend not using NPM?

Oh I see, I assumed there was some kind of plugin database that it was supposed to search, rather than just the few plugins that are already listed on the page. Ok, I'll open an issue on GitHub.

I'm running a new install of NodeBB v4.0.0-beta.2 (it's the first time I've used NodeBB).

The plugin search in the admin isn't working properly. It only searches the plugins that are already visible on the active tab – eg the Trending tab or the Find Plugins tab. There's no way to search for plugins that don't appear by default on one of those tabs (10 plugins on the former, 19 on the latter, with partial overlap).
When I wanted to install nodebb-plugin-sso-facebook, for instance, I had to use NPM because I couldn't access it from the admin UI.

The Trending tab also includes outdated plugins that haven't been updated in many years, but that's unrelated I guess.

It would be great to be able to "boost" posts/threads from across the Fediverse (and in particular, topics from other forums) into a local NodeBB category.

Is there a way to do that currently, or a likelihood of it being added it in the future?

I was wondering if NodeBB would run on Deno, especially with the new supposedly NodeJS-compatible Deno v2.0. Has anyone tried it?

@julian sorry to multi-post but I forgot to say: although I can find your post from my Mastodon account and reply to it, I still haven't worked out how I would do the reverse from here. In fact I'm not sure if I can follow a Mastodon account (or perhaps more usefully, a Discourse or Lemmy topic or even a topic or account on a different NodeBB instance) from a NodeBB account at all, is that possible yet?

@eeeee Absolutely, and @julian has my deepest respect for that. Like I mentioned, the UI for inter-platform interactions is definitely a really tricky problem to solve in an intuitive way, and I don't think any Fediverse platform has managed it yet. (I'm very interested in this because I'm starting to consider similar issues as they relate to the Fediverse implementation in Forgejo.)

@julian it was this one: https://socialhub.activitypub.rocks/t/explaining-the-fediverse-is-a-hard-problem/4462/7
It's a Discourse post (and thus problem) rather than a NodeBB one, but it illustrates the point of the general jankiness of inter-platform interaction on the fediverse: if I copy the permalink of your post above into my Mastodon instance, it finds it and I can reply, but if I copy the permalink of a Discourse post from the same thread, it doesn't work.

@julian Here's the one I saw today: https://indieweb.social/@[email protected]/113101718634936122

However, I now see that the broken HTML appears in the original post on this forum, so it's not a federation problem. Apologies for the 'false alarm' on that aspect. I've definitely seen broken formatting before, but haven't clicked through to check where the issue was. I'll keep an eye out for it again.

That said, my point was mainly about the difficulty of actually working out how to interact with posts from a different instance (especially one running different software), rather than about the actual content of the federated messages.

Honestly I think that if interoperability between different types of federated platforms Just Worked people would "understand" it more intuitively, because they'd see it in action instead of it having to be explained to them as an abstract concept.

I'm a fairly tech-savvy user, and I perfectly understand what federation is and how it works on a technical level, but even I find the UI aspects often confusing or downright impossible to figure out.
For example, I saw this thread from my Mastodon client because I followed the ActivityPub topic on this forum from my Mastodon account. In my Mastodon client the posts appear as boosts, but mostly with broken HTML formatting. I clicked through to this forum to read the thread properly. I then wanted to "like" / +1 a post, so I copied the permalink into my Mastodon client like I would for a post on a different Mastodon instance, but it couldn't find anything. In the end I had to log into my local account on this forum instead.

Don't get me wrong, the UI problems are very difficult to get right. But I think they're more important than documentation. When it Just Works, people will grok it and documentation/explanation won't be needed.