4905
results for "micro.blog"
-
If anyone’s curious, a little more detail about why this is a weird edge case: the API (conversation.js) that GWG is calling accepts a URL and returns post information in Micro.blog. The post URL exists from the ActivityPub user, so Micro.blog thinks it’s a good match and returns it. For ActivityPub, the permalink is the /2022/etc. version, and for feeds, the permalink is the p=6190 version.
[manton]
at
2022-12-15 21:11
-
This is really an issue with Micro.blog when there is a post that is duplicated across multiple accounts (in this case, a “real” Micro.blog account and an ActivityPub reference). This never used to happen before, so I need to see if I can make it smarter.
[manton]
at
2022-12-15 20:42
-
Because that’s the actual GUID that Micro.blog records and checks first when looking up URLs.
[manton]
at
2022-12-15 18:49
-
[manton]: Using https://micro.blog/conversation.js
GWG
at
2022-12-15 18:32
-
@GWG That’s strange. It looks like Micro.blog was getting an old copy of the feed. I cleared the “etag” value from Micro.blog for your feed and it’s updated now with the latest post.
[manton]
at
2022-12-15 17:36
-
[manton]: I have a rel-me to micro.blog, but not that I know of, re the connection. But if you tell me how I can tell you, I will do that
GWG
at
2022-12-15 17:31
-
[manton]: But, the dshanske profile should have the flight attendant comment, because it is in the jsonfeed that feeds micro.blog
GWG
at
2022-12-15 17:25
-
Right now, there’s no way that Micro.blog would know that [dshanske] is the same as [dshanske]@david.shanske.com, right?
[manton]
at
2022-12-15 17:16
-
@GWG Hmm. Yeah, that could happen if Micro.blog gets anything ActivityPub-related and doesn’t know that it’s the same as your other username.
[manton]
at
2022-12-15 17:15
-
Why is it suddenly different than https://micro.blog/dshanske
GWG
at
2022-12-15 17:09