Is federation a topic that has been explored?
I'm interested from the perspective of loosely affiliated online communities.
Is federation a topic that has been explored?
I'm interested from the perspective of loosely affiliated online communities.
I'm new to javascript-- in fact to almost all programming. That said I've been doing some cool stuff with Hugo & JS. A client-side hook is something that happens in the client (web browser's javascript) -- correct?
How does one look at client-side code for nodebb?
Thanks a lot
-Jake
Please do put it on github. We are gearing up to make some extensions to nodebb in the direction of "real-time web interactivity" I'd love to see if we can support one another's codebases. BTW does your auction site support cryptocurrency?
Thanks!
-Jake
Has this been attempted? Basically, I'd like to enable multiple users to work on a single post at once.
Cool! I have a question about the chat, and I hope that you'll take/consider this seriously. I spend a lot of time on the web, and a lot of time looking at (specifically) Open Source web applications. When I was looking for fourm code it was quite the epic, trying damn near everything out there. I've chosen this forum code, and so I hope to support you with ideas as well as PRs. For a million and one reasons, I strongly prefer NodeBB to Discourse. It's a choice I'd gladly make over and over, and it largely has to do with the receptivity of the community that creates NodeBB to new ideas. Discourse is too busy trying to bury their Multi-Site functionality to be receptive to new ideas.
I think that the chat in NodeBB should integrate with either IRC or Matrix Chat. I know that Raocket.Chat, a meteor-based chat application has support for Matrix Chat (ether upcoming, or.... something. Here is a link to the relevant repo: https://github.com/RocketChat/Rocket.Chat.Federation
Standards are a very, very good thing. IRC is one, Matrix is another. Web app content-based walled gardens are just as annoying as any other walled garden, and we should strive to avoid them. Well, that's what I've got for now. Thanks for the awesome code, keep it up!
You could do that, it's true. That said I'd like to kinda shunt people away from NginX. To hell with it and its antiquated ways. (okay okay, that is harsh-- it's very good at what it does and most likely it will continue doing that even a decade from now.)
Anyway, try out Caddy. I use Caddy in front of my web applications, which I run in the wonderful isolation of Docker containers, and caddy slaps an automatically generated SSL/TLS cert on them, yay! If you're running without encryption, you no longer have any excuse. Both Caddy and Let's Encrypt have made trivial work out of the previously quite harsh process of getting your site secured.