Closed aarongustafson closed 1 year ago
I kept having Ruby/Jekyll issues when upgrading my Mac, so I have moved off of Jekyll and will not be working on this project anymore, going forward. I am going to flag this as wonβt fix, but leave it open in case someone else wants to pick up the project from here.
ππΌ Brett,
Is this "feature complete"?
I can install from your branch, but Brid.gy does not appear to be sending webmentions through the plugin.
Is this just missing documentation on how to configure or did I miss a step?
The relevant commit is at this URL.
ππΌ Brett,
Is this "feature complete"?
I can install from your branch, but Brid.gy does not appear to be sending webmentions through the plugin.
Is this just missing documentation on how to configure or did I miss a step?
The relevant commit is at this URL.
Wow, apologies for the very late reply!
Yup, this feature is complete! I use it for syndicating my posts to Twitter via Brid.gy on my own blog.
I don't see anything immediately wrong with your configuration. After calling jekyll build
, if you look in your cache directory, are there any entries in webmention_io_outgoing.yml
indicating a queued outgoing webmention?
Re-upping this now that I'm giving it another look. I'm running the dev branch version of JW if that helps...
Setup is as follows:
Jekyll 3.9.2 Ruby 2.7.0
_config.yml
feed:
path: notes-rss.xml
webmentions:
collections:
- notes
syndication:
mastodon:
endpoint: https://brid.gy/publish/mastodon
_layouts/note.html
<article class="h-entry">
<h1 class="p-name"><a class="u-url" href="{{ page.url }}">{{ page.title }}</a></h1>
<div class="meta"><time datetime="{{ page.date | date: "%Y-%m-%d" }}" class="dt-published">{{ page.date | date: '%B %-d, %Y' }}</time></div>
<div class="e-content">
{{ content }}
</div>
<a href="https://brid.gy/publish/mastodon?bridgy_omit_link=true"></a>
</article>
Creating a file in _notes
with the following content will generate a curl command to send the webmention (lookups and queueing are done in my build task):
---
layout: note
title: Another Test
syndicate_to: [ mastodon ]
---
With any luck, this note will find its way to [Mastodon][].
[Mastodon]: https://joinmastodon.org
One thing that comes to mind is that my deploys are not automatically published when Netlify builds and runs the webmention plugin. Could this be tripping up Brid.gy's post discovery? (π @snarfed)
@chrisfinazzo sorry, I don't quite follow the problem here, other than your posts aren't triggering Bridgy Publish? You can see attempts on your Bridgy user page, and I'm happy to check logs too if you want.
@chrisfinazzo sorry, I don't quite follow the problem here, other than your posts aren't triggering Bridgy Publish? You can see attempts on your Bridgy user page, and I'm happy to check logs too if you want.
That's what I'm seeing. Although it was slightly delayed, I did get a 200
response to this request. Is it necessary to include u-syndication
with a hyperlink in order for this to work automatically?
I'm not doing this bit currently, but it brings up a question of how to add these links if the post being syndicated doesn't actually exist on the service. IOW, I'm guessing until the post hits Mastodon, that URL isn't known yet to Brid.gy yet? The other thing I can think of is that my requests omit the URL, but this was done more in the spirit of things that don't have a title so as to keep things as clean as possible.
Happy to be proven wrong...
Edit I'm just slow. Missing some metadata (like u-url
) which caused this not to be picked up.
Reading the spec...helps? Who knew π€¦
Hi @chrisfinazzo! Looks like that was just a preview; the line for it in the "Published" section on https://brid.gy/mastodon/@chrisfinazzo@mastodon.social says preview. If you preview it again and click Send, it should go through.
FYI, I've been doing a bunch of refactoring on the main branch and am closing this PR and opening a new one based on the current main branch. After that, I expect to push the code into main fairly soon, I just wanna run it a bit, first, to make sure I've shaken out any potential rebasing bugs.
Dupes #134 to main