-
Notifications
You must be signed in to change notification settings - Fork 48
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
Synchronisation stopped #1780
Comments
Hey, sorry for the trouble! Bridgy Fed received a few webmentions for your site on 2/13, so it stopped polling your feed. Let me know if you want me to switch it back to using your feed instead of webmentions. |
Hey Yes, I sent those Webmentions in an attempt to "manually" kick off the synchronisation. I don't mind having to send a WM, I can automate that. |
Looks like the post you sent the webmentions for, https://sequr.be/blog/2025/02/flashing-the-sonoff-powr3-with-tasmota/ , didn't have a link to https://fed.brid.gy, which it needs in order to be a valid webmention. https://fed.brid.gy/docs#web-how-post |
🤦♂️ you're right So just to confirm: if I add the link and re-send the WebMention, the article will be added? OR I request to undo the WebMention-based listing and the articles should be added through periodic scanning? |
Yes!
Also yes. Feed polling frequency varies from every 2 hours to once a day based on how frequently you post. |
Hi
I noticed my 2 most recent blog posts were not being picked up by Bridgy Fed.
See https://fed.brid.gy/web/sequr.be and https://sequr.be
Clicking the "Update profile" button did not trigger a refresh and sending a Webmention with a link to the latest blog post also didn't work.
See https://fed.brid.gy/docs#web-how-post
This issue coincides with changes to my site's feed (adding an Atom feed next to the existing RSS feed) and the addition of microformats to my site.
However, I don´t see how any of this would cause the sync to halt.
Any pointers on whether this is an issue on my end or something at Bridgy-Fed broke?
The text was updated successfully, but these errors were encountered: