Ooh, that's nice. I could see that effectively replacing disqus comments below articles. Cool beans!
this post was submitted on 21 Oct 2024
346 points (97.5% liked)
Fediverse
28465 readers
799 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
Wait, so theoretically, you could create a blog, and create a Lemmy instance/community, post a blog entry, have it auto post the blog entry to your instance, and now the Lemmy comments for the Lemmy post are the comments on the blog post? Do I have that right?
And in theory THIS comment should show up on your blog, yes?
Edit: Hey, I see it!
Oh much simpler, I just make a post with my blog as a link, and supply that link to my site and it shows the comments from that link. As I said, not actually federated. It's basically a sort of frontend.
Could you make a community, and a bot? The bot would look for any post on your blog, then the bot creates a post in that community that uses the blog post title as the lemmy title, and uses the blog body as the post body.
Then the bot tells your blog the url of the lemmy post to use the lemmy comments.
Then, I see the button that says "load lemmy comments". Maybe your bot also creates a mastodon using the title of the blog post as a link to the blog post. Then any mastodon replies to that mastodon post could be under a different button that just says "Load Mastodon replies".
So at the end of your blog you have "Load Lemmy comments" (just as we see here) but next to it is "Load Mastodon replies".
And all of this, is done by you just posting once to the blog, while the bots do everything else in an instant.
You just post once on the blog, and automatically a Lemmy post is created which is a duplicate of the blog post, the lemmy comments are loaded via a button on the blog automatically, a Mastodon post is created which is just a link to the blog using that posts title as the clickable link, AND a button on the blog is created to see Mastodon replies to the mastodon post.
Everything besides the innitial blog post is automatic.
Is that possible?
Possible sure, but aside from the effort to make such a bot, posting to my own community would mean that very few people would see it, aside from those who already follow the blog. I have to pick a lemmy community, at which point I may as well do the rest of the work too. Now maybe I could have an llm analyze my post, fetch a list of communities, and then pick a likely one, but honestly this is getting too complicated
load more comments
(2 replies)
Kinda cool. To be honest I’m mostly posting this to test it.
Edit: It works!
How about image support?
Not at the moment, since that would require parsing the markdown
Neat. It took me a while to realise what was going on: the post on Lemmy and the blogpost are two separate entities. The Lemmy post is a link to the blogpost, and the blogpost uses the post_id to fetch the comments (so I guess this means you have to make the blogpost, make the Lemmy post, and then go back and edit the blogpost with the correct id?)
The script is inspectable on the blog - I can see it does:
const url = 'https://lemmy.ml/api/v3/comment/listpost_id=21617067&limit=100&max_depth=8&sort=Top&type_=All';
So I suppose there's an inbuilt limit for comment depth and number of replies, but if you start down the road of working on that, you'll eventually find that you've re-invented a front-end, and there's no end to it.
What the duckquill guys are doing is a bit fudgy, in that they're getting another website to do the federation legwork for them, but the results are pleasing enough.
Lol, don't blame the duckquill dev, he only wrote the mastodon one, which I don't use. This is all me.
So I suppose there’s an inbuilt limit for comment depth and number of replies, but if you start down the road of working on that, you’ll eventually find that you’ve re-invented a front-end, and there’s no end to it.
Yeah, I kinda chose the limits arbitrarily, but I don't expect them to be an issue anytime soon.
This setup is also more flexible. I can in the future add comments from multiple lemmy posts, as well as other completely different sites.
It seems like a tedious workflow, but the end result is quite good.
I wonder what happens if a comment is deleted
Neat! Do you pick one instance to load comments from? I notice that this comment isn't showing up immediately, so wondering if there's federation delay or the like.
Currently uses my home instance, lemmy.ml. I'd expect there to be some delay
I’m a little bit biased here but it might be a good idea to use an instance like lemmy.zip instead, to minimize the amount of defederation going on.
Would be cool if something like this existed for WordPress
It would be nice if you could sign-in/comment directly from the blog. But I'm guessing the Lemmy api doesn't provide that without making the blog it's own instance
load more comments
(2 replies)
Nice, I did the same for my blog. Didn't want to build a whole comment system when Lemmy fits the bill quite nicely :)
I did the same using Mastodon for my blog, ended up switching to Disqus (shudders) just because it supports more SSO options for accounts that my limited readership is likely to have
Great!
peachy keen, friend. peachy keen.
Alright, let's see if this shows
it be there! ;-)
awesome job!
Lets gooo ╰(*°▽°*)╯╰(*°▽°*)╯
History in the making. This is what open source is all about.
This is a test comment to check the functionality.
This is a test reply to test the functionality of the test comment.
This reply is for informing you that both your and my comments are visible on the blog. Also, i'm posting from lemm.ee and the user is from .ml. So cross-instance comments are also working.
Good job @[email protected]
load more comments
(1 replies)
Super neat concept. I really enjoy the melding of (micro)blogs and threads, which is what I like about Kbin/Mbin; I can follow interesting people from Mastodon without needing to visit a separate app or site. In a way, this scratches that same itch for Lemmy.
Immediately scrolls down to the comment section. I've been spoiled by content just automatically loading, but I saw the "Load Lemmy" button. Tres chic.
It would be cool if there was a raised question mark button to the right for the load button, that on mouse over or click shows a tooltip explaining shortly what Lemmy is, as well as directly telling the user what community and instance the comments hail from - even before loading the content.
A standard tooltip for that purpose would be kind of nice.
load more comments
(2 replies)
Awsum!
Hey aren't you the duckquill dev?
Mhm :)
Nice work!
naawww this is tuff
This is really cool. Can you add more detail on how to set this up to the blogpost?
I was, but honestly there's not much to write without getting into the specifics of parsing the lemmy api, because it's literally just a fetchcall and then turning the response into nice html
Interesting. What is tge reasoning behind only fetching the comments vs. a full fediverse integration?
Fediverse integration would require me to run, pay for and maintain a federated server. This takes me 50 lines of Javascript on a completely static site that cloudflare runs for free. It's just so much easier
this is actually really cool! I also wanna suggest using any instance besides .ml or .world, just for the sake of why Lemmy exists in the first place
load more comments
(4 replies)
Duckquill sounds like cold medicine specifically formulated for ducks.
I just wanted to say 2 things, 1) Very cool! 2)Nice username.
Does it also work with Mastodon? Because it is possible to reply to Lemmy posts from Mastodon, right?
load more comments
(3 replies)
What an awesome implementation for Lemmy!
view more: next ›