@aemaeth @infosecpub

I haven’t done any testing with pixelfed yet. Creating an account is on my list of things to do though. Testing would likely come sometime after that.

@jerry @infosecpub

‪@lemmyworld‬ users seem to be able to do this. Not sure how much effort you feel like putting into infosec.pub but enabling the ability to reply from Lemmy to mastodon originated posts seems huge.

Haven’t tried all of this with #kbin / #fedia yet so stay tuned…

@infosecpub so I can find someones Lemmy handle, search them on Mastodon, find their posts, then reply to those posts IN mastodon and it will reply natively within Lemmy.

Further, I can search for a Lemmy COMMUNITY in mastodon, browse posts and replies and respond to those as well natively within Mastodon. So a full-featured Lemmy browser could (seemingly) be built inside a Mastodon client. So interesting…

#lemmy #mastodon #fediversemigration @ivory @radiant @jknlsn

@joyjoy testing a reply to my new Lemmy friend… 😁

@sass @lemmyworld @infosecpub @[email protected] omg now I’m real confused 🤣. I can post to Lemmy instances from mastodon and randomly @ other Lemmy instances which will in turn create posts there too. @'ing my Mastodon handle works and then I can reply to that post.

It looks like a Lemmy user @joyjoy had no problem replying to my Mastodon-originated post so it would seem that strange issue may be isolated to infosec.pub.

#Fediverse got me spinning tho…

@infosecpub

One last funny thing I noticed (then I swear I’m done testing this for now), when you upvote a post on Lemmy (which still works despite replies being borked), it propagates to Mastodon as a star. How whimsical!

Oh and deletes propagate (mastodon->lemmy) which is cool.

@infosecpub Seems like a potential usability disaster imo. If people wise up to the ability to post to Lemmy instances (or infosec.pub specifically if the issue is isolated to that instance) from Mastodon than anyone who’s using Lemmy natively won’t be able to interact with that post. There’s no way of really easily seeing that it is of Mastodon origin outside inspecting the OP’s user info (which will denote I came from infosec.exchange). You can, as the OP respond to reply threads but for standard reply-ee’s you can only see/respond to the reply threads you started.

For those who don’t want to have separate identities across all these Fediverse services I can see the attraction of the cross-posting from Mastodon–> Lemmy but this is def an issue.

@jerry not sure if this is something tweakable on the Lemmy server either fixing the ability to respond to Mastodon-originated posts within Lemmy or disabling the ability to do this from Mastodon completely until it is sorted out by the Lemmy devs.

@infosecpub So for people who want to interact with #Lemmy from your existing #mastodon identity, it looks like you have some decent options. What’s interesting is this worked from my infosec.exchange account but when trying to post directly to infosec.pub from my mastodon.social account, it did not work. Could be a mastodon.social issue?

- Replying to it from a different account DID work in adding a reply to the infosec.pub post.

@jerry - fascinating behavior(s) here…

@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…