-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support any website...? #98
Comments
Yeah! Haha. It was something I realized half way through the build (some
client wanted WP). Yes it could be done that way. Interested in taking on
this build? What’s your app, maybe I might jump in.
Happy holidays, merry Christmas
…On Sun, Dec 24, 2023 at 23:10 braco ***@***.***> wrote:
Wouldn't it be possible to support any website?
The comments would be lazy initialized in the sense that nodebb would only
create the post on its back end when a user was entering a first comment on
that page.
There is a simple configuration to check if the current page the comment
box lives on is valid. Maybe a wildcard for the URL.
"https://mydomain.com/blog/*"
the nodebb plugin would check to see that the URL returns a 200 (not 404)
before allowing the first comment.
The use case is that I would like to drop nodebb comments onto a static
blog, but don't see why this wouldn't work for everything.
—
Reply to this email directly, view it on GitHub
<#98>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE72TU7BXASSXSHUDM2SFTYLD4DDAVCNFSM6AAAAABBCABYW2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TKMZVGQZDMNY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Happy holidays!! I only have a couple of weeks worth of experience in nodebb (as a user), so I'm pretty useless for PRs. I have a somewhat large nonprofit community that I just launched a website for, and part of that is a ton of scientific content. Each one of the papers has its own page now, so it would be really nice if people could comment under that particular study and have that tracked in nodebb. The lazy load / lazy topic aspect is important because there are thousands of papers and a lot of them are not important. Also seems like you could deeply simplify this plugin, doesn't it? This would let it work on any website, WP etc included, no integrations needed. You could do something as simple as
and have the server check for that tag and then maybe even tags/categorization in the meta as well?
|
You’re not wrong. This plugin was mostly paid for and designed by those who
wanted xyz use cases, so obviously as I alluded earlier, half way through I
realized that this basically can be refactored properly to essentially
support most platforms.
Now, very interestingly! I may be aligned with your use case. Let’s talk in
the new year? Almost sounds like there’s a particular project I have in
mind that almost sounds like I stole it from you, re: comments on
scientific papers
I’m also from that industry so colour me intrigued. :)
…On Wed, Dec 27, 2023 at 11:02 braco ***@***.***> wrote:
Happy holidays!!
I only have a couple of weeks worth of experience in nodebb (as a user),
so I'm pretty useless for PRs.
I have a somewhat large nonprofit community that I just launched a website
for, and part of that is a ton of scientific content. Each one of the
papers has its own page now, so it would be really nice if people could
comment under that particular study and have that tracked in nodebb.
Also seems like you could deeply simplify this plugin, doesn't it? This
would let it work on any website, WP etc included, no integrations needed.
You could do something as simple as
<meta name="comments" content="enabled">
and have the server check for that tag
and then maybe even tags/categorization in the meta as well?
<meta name="nodebb-category" content="xyz">
—
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE72TRD73T2WPNLE6XPR6TYLRBBPAVCNFSM6AAAAABBCABYW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGQZTINBVGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
post holiday bump! 😬 |
Happy new years! Shoot me your personal and let’s see what I can do. No
promises but I’d be happy to help and work on this if our interests are
aligned!
…On Mon, Jan 8, 2024 at 23:20 braco ***@***.***> wrote:
post holiday bump! 😬
—
Reply to this email directly, view it on GitHub
<#98 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE72TQLC7JSGUTVX2OFB2LYNTARZAVCNFSM6AAAAABBCABYW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBSGM4DSOJWGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Wouldn't it be possible to support any website?
The comments would be lazy initialized in the sense that nodebb would only create the post on its back end when a user was entering a first comment on that page.
There is a simple configuration to check if the current page the comment box lives on is valid. Maybe a wildcard for the URL.
"https://mydomain.com/blog/*"
the nodebb plugin would check to see that the URL returns a 200 (not 404) before allowing the first comment.
Or it could check for a meta tag with something allowing comments there.
The use case is that I would like to drop nodebb comments onto a static blog, but don't see why this wouldn't work for everything.
The text was updated successfully, but these errors were encountered: