jk.nipponalba.scot website
https://jk.nipponalba.scot
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.2 KiB
1.2 KiB
| date | draft | like-of | pleromaurl | posttype | sensitive | slug | visibility | title | xAuthor | xAuthorUrl | xPhoto | xContent | xPublished | xPostType |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020-11-25 16:41:40 | false | https://social.nipponalba.scot/notice/A1YYC4zXroQbc6AhaC | <nil> | like-of | false | 5fbe8944 | public | like-of | J K 🇯🇵🏴 | https://social.nipponalba.scot/users/jk | https://social.nipponalba.scot/media/201caaea1889f39529535e829117ad39acdd7db241be2c888363e72bda171c67.jpg?name=profile.jpg | OK, so I think the process will go like this: <br /><br />1. GET remote URL of reply status<br />2. GET remote context of reply status<br />3. From remote context get URL of original post<br />4. Curl original post (which is to an object rather than notice.. ) and grab the local ID of the original status from the redirect message..<br />5. GET local context of original status locally<br />6. Loop through each status entry in context array until you hit the one thats URL matches the remote URL of the status I am trying to reply to.. <br />7. From that record, grab the local ID of the same status and send the reply to it.. <br /><br />.. fun!(?!?!?!) | 2020-11-25T12:18:12+00:00 | reply |
