@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.
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 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...
@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
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 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
@shellsharks @infosecpub @ivory @radiant @jknlsn
Have you done any testing with PixelFed yet? I think it should have a very similar interaction...
@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.