this post was submitted on 14 Jun 2023
7 points (100.0% liked)

Discussions related to Infosec.pub

1128 readers
1 users here now

founded 1 year ago
MODERATORS
 

@infosecpub testing posting from #mastodon

Testing, testing, 1, 2, 3...

you are viewing a single comment's thread
view the rest of the comments
[–] shellsharks@infosec.exchange 2 points 1 year ago (18 children)

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

[–] shellsharks@infosec.exchange 3 points 1 year ago (17 children)

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

[–] AGTMADCAT@infosec.exchange 3 points 1 year ago (2 children)

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

[–] sass@mastodon.social 2 points 1 year ago (1 children)

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

[–] AGTMADCAT@infosec.exchange 1 points 1 year ago

@sass @shellsharks @infosecpub This is the best bug and I love it.

load more comments (14 replies)
load more comments (14 replies)