@[email protected] that's huge news! Congrats @[email protected] !
Ah... also hopefully there's a nice consultation fee involved.
Employees & Interns of NodeBB
@[email protected] that's huge news! Congrats @[email protected] !
Ah... also hopefully there's a nice consultation fee involved.
I've also added FEP 1b12 announces for additional activities:
Confirming that at least Discourse accepted the Announce(Like(Note))
and parsed it correctly.
As per the discussion generated by this topic, I have updated the NodeBB implementation so that its group actors (NodeBB categories) send out Announce(Create(Note))
in addition to Announce(Note)
, the latter being sent out for compatibility with services that do not handle activity announcement.
I tried with the below plugin.json and I can see my module getting loaded..
"modules": {
"searchv2.js": "public/searchv2.js"
},
The path is to the file in the plugin folder.
define('searchv2', ['search'], (search) => {
const Searchv2 = {};
Searchv2.init = function () {
console.log('v2 init');
if (!config.searchEnabled) {
return;
}
search.showAndFocusInput();
};
return Searchv2;
});
You don't need staticDirs for doing this, thats for serving files via express static middleware.
Let's see if replies work.
For simple stuff you can use the hooks in public/src/modules/search.js
, if you want to replace the whole thing I think you can do it by adding your own module in your plugin.json like below.
...
"modules": {
"../modules/search.js": "public/mySearchModule.js"
}
...
If you go that route you will have to copy the entire search.js file from core and then modify it to your needs. Basically the file in the plugin will overwrite the one in core during build.
@[email protected] well, if that was your concern then let me assuage your fear by telling you that you won't need to sell or give away the laptop because if you need an upgrade you can just upgrade the internals and keep the shell!
Those are only just for user SSO. Nothing related to post/article integration.
That might be better served with
It makes complete sense from a feasibility and scalability point of view. The downside is you might find it more difficult to achieve buy-in because you're introducing a hurdle, albeit one that is fully justified.
Could we meet half-way? Since NodeBB has its own RESTful JSON API, if one were to compile a list of endpoints that you could call to verify state, etc. would that be enough to address the roadblocks to supporting automated FediTest testing against NodeBB?
@Wilco there has been. You can use the WordPress SSO plugin now, or the sso-oauth2-multiple plugin.