-
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
ActivityPub => ATProto hashtags #980
Comments
AS2:
...converted to AS1:
...converted to ATProto:
|
Are you sure it works? |
@austinhuang0131 looks like you're hitting #1010 |
It is in post text though... It's just that if the last line of the content consists solely of hashtags, then Mastodon will display it as a footer, it shouldn't have any effect on ActivityPub itself.
|
Good point! I haven't looked into this deeply yet. I'll follow up in #1010. |
Reopening, these seem to be unreliable. Eg here's one that didn't work: https://mastodon.online/@emarktaylor/112480973885137226 => https://bsky.app/profile/emarktaylor.mastodon.online.ap.brid.gy/post/3kszmvscesxh2 ...and here's one with two, one worked, one didn't 🤪: https://mastodon.online/@emarktaylor/112480873556819998 => https://bsky.app/profile/emarktaylor.mastodon.online.ap.brid.gy/post/3kszlfj5l2wf2 |
I think it's case-sensitivity. Mastodon apparently sends hashtags according to its database rather than the post content. I wonder if that affects further Unicode collation beyond case 😬 (In the first example, it's '#USPol'/ |
That's interesting. For testing I made this post. Mastodon. Bluesky. Neither registered as camel-cased in the JSON, even though the TuneTuesday tag is camel-cased on my Mastodon instance (I updated it myself long ago). Made another post. Mastodon. Bluesky. This time the tunetuesday hashtag looks good, but not the storysong one. Posted one final one. Mastodon. Bluesky. Does seem like the case sensitive thing is an issue, but it's kinda bothersome that it doesn't necessarily match what is on the OP's server. In the second post I think maybe the presence of the period directly following the storysong hashtag kept it from being processed properly? Just speculation there. |
Found this issue because I'm having the same issue with hashtags. Looks like it could indeed be case related. Working Not Working Update Ignore the working one, I was in a hurry and didn't notice the Mastodon post was bridged from Bluesky to Mastodon. 🤦🏻♂️ Here's one I did on Mastodon with lowercase hashtag and that didn't work in Bluesky either: https://mastodon.social/@hallenbeck/112490349136364796 => https://bsky.app/profile/hallenbeck.mastodon.social.ap.brid.gy/post/3kt5s3xsnfu22 |
Thanks for the examples, all! Looks like case sensitivity was definitely one root cause here, punctuation on either end of the hashtag in the post text was another, and occasionally hashtags at the beginning or end of the post text were another. I think I've fixed all of those. Example: https://indieweb.social/@snarfed/112554052674489553 => https://bsky.app/profile/snarfed.indieweb.social.ap.brid.gy/post/3ku23dhx4bho2 Sadly AS2 dropped AS1's That's pretty unusual though, so I'm tentatively marking this as fixed for now. Feel free to reopen or open new issues for other real world problems you all see. And thanks again for all the sleuthing! |
Not working yet. Example: https://indieweb.social/@laurenshof/112359491459258562 => https://bsky.app/profile/laurenshof.indieweb.social.ap.brid.gy/post/3krdoh7rypeb2
The text was updated successfully, but these errors were encountered: