-
Notifications
You must be signed in to change notification settings - Fork 52
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
Update previously sent webmentions when they change, eg content, author name, etc (not planned) #907
Comments
good question! out of curiosity, if you find one of the webmentions on your bridgy page - click "Older →" a few times if necessary - and then click its retry button, does that fix the link? |
At a guess it’s about 1000 web mentions down the list. Is there an easier way to find it that clicking “older”?
… On 4/01/2020, at 1:13 PM, Ryan Barrett ***@***.***> wrote:
good question! out of curiosity, if you find one of the webmentions on your bridgy page - click "Older →" a few times if necessary - and then click its retry button, does that fix the link?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <https://github.com/snarfed/bridgy-fed/issues/61?email_source=notifications&email_token=ABKCJGY3G46WBTOWRZIGFILQ37IDNA5CNFSM4KCS7272YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICL5II#issuecomment-570736289>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKCJG3QPZPFVWWQFMF732LQ37IDNANCNFSM4KCS727Q>.
|
otherwise, this is CMS/web server specific, so your best bet is to ask in #indieweb-wordpress or on https://github.com/pfefferle/wordpress-webmention or https://github.com/pfefferle/wordpress-semantic-linkbacks . 🤞 |
Ha, the wordpress-webmention crowd sent me to you.
… On 4/01/2020, at 1:17 PM, Ryan Barrett ***@***.***> wrote:
otherwise, this is CMS/web server specific, so your best bet is to ask in #indieweb-wordpress or on https://github.com/pfefferle/wordpress-webmention <https://github.com/pfefferle/wordpress-webmention> or https://github.com/pfefferle/wordpress-semantic-linkbacks <https://github.com/pfefferle/wordpress-semantic-linkbacks> . 🤞
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <https://github.com/snarfed/bridgy-fed/issues/61?email_source=notifications&email_token=ABKCJG6YYIY2AA6OXG2IEUTQ37ISLA5CNFSM4KCS7272YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICMBCA#issuecomment-570736776>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKCJG6GQFT5R454S4VI4LTQ37ISLANCNFSM4KCS727Q>.
|
sadly no. at a high level, updating old webmentions when something changes like this is a good use case, but not something Bridgy currently supports, largely due to scale. it's sent over 1.6M webmentions already, so watching them all and detecting changes that might affect any of them is a much bigger challenge than i plan to tackle, especially since i don't currently guarantee that Bridgy even stores all of those sent webmentions. I'm open to design proposals and PRs though! in the meantime, you're right, you could definitely update these links manually yourself! @dshanske et al can hopefully help there. |
Editing the links manually can be done... I referred because I thought there might be something to track this at the Bridgy level. |
The links should be editable ob the comment edit fields, which field is greyed out? |
Probably easier to show it:
… On 4/01/2020, at 2:10 PM, David Shanske ***@***.***> wrote:
The links should be editable ob the comment edit fields, which field is greyed out?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#907?email_source=notifications&email_token=ABKCJG3H5YST5KVMBZ7F47TQ37OZVA5CNFSM4KCTNI2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICNULI#issuecomment-570743341>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKCJGYUAX4WV7JZCUI6WULQ37OZVANCNFSM4KCTNI2A>.
|
You probably know this, but it may be useful for others later. When you scroll back through bridgy webmentions the URL includes ?responses_before=2019-05-27T21:09:05.926421#
All I had to do was find the date stamp on the original comment, tinker with the URL… and bingo.
Refreshing the webmention didn’t fix the link though…
|
thanks @billbennettnz! good idea. I'll keep this issue open here to track the larger idea of tracking all sent webmentions and resending when they change. I'm also surprised that retrying didn't work. could you post the bridgy webmention source URL? or a link to your user page with the right |
Hm, assuming you are (at least temporarily - like for a couple of months) storing webmentions in a database … a form to search it would be handy. I'd assume, @billbennettnz would have the link to the webmention he was asked to update, so being able to search for that one, would help here as well. What other fields could be generally of interest? |
@Ryuno-Ki yes! agreed. luckily, bridgy already supports that! you can plug a silo or original post URL into the Resend for post text box on your user page, and it will resend all the webmentions it knows about. this issue is more involved though. it's about updating replies (etc) from people who have changed their username. that's complicated for a handful of reasons beyond just finding and resending past webmentions. (fortunately, username changes are relatively rare!) |
Related: #137 |
For the record, Bridgy does currently detect and resend recent webmentions when they change. For example, if someone comments on a GitHub issue, and then edits their comment, Bridgy would notice the change and resend the comment. ("Recent" here isn't based on time as much as post velocity. Bridgy will generally see changes to responses on the last 10-50 or so of the user's posts.) |
This might be something you could add to the FAQ.
I have a couple of Twitter webmentions on my WordPress site where the original poster has changed their Twitter handle. These appear as broken links. In at least one case, I know the replacement Twitter handle. I'm told it's possible to update web mentions, but the fields are greyed out on the Wordpress comment edit page. How can I update the web mention?
The text was updated successfully, but these errors were encountered: