@infosecpub Alright so that works. Just @[community]@[lemmy server] with the first line being the title some new lines and then the body. As you might expect, it posts from my mastodon handle.
Attempting to "reply" to this post sends infosec.pub into a long spin. Not sure if that's just an instance issue or if responding to a Mastodon-originated post on my Lemmy account is causing the issue.
Let's see what happens when I reply to this post via Mastodon...
@infosecpub So that *immediately* propagated the reply TO the infosec.pub post. COOL! Replying to the post within Lemmy still seems to be struggling though...
@infosecpub Alright so that works. Just @[community]@[lemmy server] with the first line being the title some new lines and then the body. As you might expect, it posts from my mastodon handle.
Attempting to "reply" to this post sends infosec.pub into a long spin. Not sure if that's just an instance issue or if responding to a Mastodon-originated post on my Lemmy account is causing the issue.
Let's see what happens when I reply to this post via Mastodon...
@infosecpub So that *immediately* propagated the reply TO the infosec.pub post. COOL! Replying to the post within Lemmy still seems to be struggling though...
@shellsharks @infosecpub Test test
When I tried replying from Lemmy (using Jerboa) I just got a "language_not_allowed" error and it didn't work.
@AGTMADCAT @shellsharks @infosecpub
Yeah it's weird, it's like a post originating from Mastodon can be interacted with from Mastodon but natively within Lemmy it is borked.
@sass @shellsharks @infosecpub This is the best bug and I love it.