That’s what I meant by admins/mods, thus I still think my point is still valid: not private, but not exactly public.

It’s not exactly public, IIRC? Like, admins/mods have access, so it’s not private by any means, but I wouldn’t really call it public.

Yep, exactly that. It’s a little more complex, thus the different term (defederation), but from user-perspective it’s exactly that: a server block.

Thanks for the ping :)

Can you send me some details? What community are you trying to post to, what instance are you posting from? What fields are you filling out? Self-hosted or the one at https://schedule.lemmings.world/?

PHP_EOL depends on your host system, it’s \r\n on Windows.

I don’t really want to use what Lerdorf intended, PHP <= 4 was horrible, 5.x was mainly getting slowly rid of nonsense and with 7.x PHP started its slow path of redemption and entered its modern era.

While Lerdorf’s vision was great at that time for its intended use case, I wouldn’t want to build anything serious in it.

Every troll server gets defederated from by everyone. And every troll gets banned on the normal servers. I think the federated nature is a blessing, those assholes have their own part of the internet which is usually far from my part of the internet.

In PHP it exists as well. I try to use PHP_EOL but when I’m lazy I simply do “\n”.

PHP: 0.3*

* with default precision

That guy is great. But nothing beats his JS developer interview: https://www.youtube.com/watch?v=Uo3cL4nrGOk

I said better, not more secure. It’s not as easy to accidentally leak the message. It’s equally easy to intentionally leak it.

I mean, have you ever read anything about any dictatorship?

But if you officially operate somewhere, they can sue you, I thought that was common knowledge?

Anyway, not complying with local laws and operating in the country can get you in some serious trouble. And the trouble will escalate until you comply or pull out of the country.

Kim Jong Un can sue anyone. Like, they can sue Signal if they want. Sure, they have no way to enforce it, but they can sue (and win the case). It’s not like this would be a first, that happened quite a few times. Especially in dictatorship.

There is a reason: you will be sued out of existence. And the bit about North Korea made me laugh, so thanks.

Yep. Sadly, Lemmy will move on to implement this exact horrible mess in future versions.

The current ChatMessage approach is much better than crazy shenanigans with to/cc/mentions.

I shared a bit about exactly this here: https://lemmyverse.link/lemmings.world/comment/14476151

Using Laravel as a framework should be the first red flag, I yet have to meet a Laravel dev who understands architecture (and I interviewed quite a bit of them). That framework is several anti-patterns bundled into a nice package.

I actually like how Lemmy handles it, it warns you that it’s unencrypted and that it recommends Matrix

It also uses an entirely separate AP type that’s not used for anything else (ChatMessage) unlike Mastodon which uses Note, which is also used for: Mastodon posts and comments, Lemmy comments, most likely others.

ChatMessage type also has strict requirements about recipients, the chances to leak them are slimmer. Additionally, if the target app does not support the type, it’s very unlikely it will handle it at all, but Note will most likely be handled in some way.

In conclusion, Lemmy PMs are very hard to leak accidentally (still very easy to leak intentionally).

Sadly, Lemmy will be moving to Mastodon-style PMs.

You know they can’t legally operate there if they don’t follow the law, right?

Pulling out is the only form of protest they have as a company. The rest is up to its users.

Anyway, if it happened, you could still use Signal anyway, perhaps with the help of a relay like other countries who prefer spying over privacy.

I did elaborate a bit in a sibling comment.