

You have to subscribe to a community
It sounds like they did think that far, but that has its own problems for them.
my subscription to the community remains pending
I’m a #SoftwareDeveloper from #Switzerland. My languages are #Java, #CSharp, #Javascript, German, English, and #SwissGerman. I’m in the process of #LearningJapanese.
I like to make custom #UserScripts and #UserStyles to personalize my experience on the web. In terms of #Gaming, currently I’m mainly interested in #VintageStory and #HonkaiStarRail. I’m a big fan of #Modding.
I also watch #Anime and read #Manga.
#fedi22 (for fediverse.info)


You have to subscribe to a community
It sounds like they did think that far, but that has its own problems for them.
my subscription to the community remains pending
This only applies though if it’s a per-device passkey that uses a private key stored securely that cannot be exported.
If the private key can be exported, it can be stolen and the factors becomes invalid.
But people also store their private key in cloud solutions (some here mentioned doing that) which just makes the factor invalid anyway, since then it’s not device-bound anymore, and it’s the device that verifies your identity with those methods.
Like, what if someone hacks the cloud service storing the passkeys and steals them? Not really any different from storing passwords in a cloud, and that one isn’t called 2FA either.


This isn’t an accusation, but was this comment written with AI? There’s a glaring logical error here which I think a human would catch easily, but an LLM (which is just a natural language generator, not a logic processor) could possibly overlook.
Specifically, your arguments don’t really make a lot of sense. They’re also not targeted at my claim. It reads more like a defense of JPlus. To which I want to clarify, I merely took issue with the specific claim I quoted, I wasn’t trying to say there’s no point to JPlus. There’s no need to defend JPlus in general. So I’m going to dismiss runtime behaviors since that has nothing to do with the syntax.
Groovy introduces dynamic typing
Java has dynamic typing already. Groovy introduced it first, but it’s not a Groovy exclusive feature anymore. It’s also optional.
additional syntax
There being additional syntax doesn’t matter if it’s optional. We’re talking here about whether Java code works in Groovy/JPlus, and it does. Not the other way around. At least that’s what I understood.
JPlus also adds the nullsafe and elvis operators, so it also adds additional syntax and JPlus code won’t work when compiled with Java directly.
Groovy is highly compatible with Java and most Java code runs in Groovy without changes. However, it’s not 100% identical.
JPlus also doesn’t guarantee being 100% identical. It says “mostly” the same.
Basically, none of the arguments really compare the two in the context given. The runtime behavior is the only real difference listed here, but that’s irrelevant in the context of them being supersets.


Notably, there is currently no ‘superset’ language that keeps Java syntax almost intact
There’s groovy iirc.


Discourse decided to do its thread context in a way that’s currently incompatible with projects like Mbin or Lemmy. Those expect threads to be represented by some kind of post (Page, Article, Image, etc objects), while Discourse decided to use an OrderedCollection, with the first item being the opening post.
Even if Lemmy decided to add support for OrderedCollection threads, there’s another issue though: the barrier for initial federation is too high. Discourse only gives you the fediverse handle of its categories, but to federate them in, you need their JSON-LD URL, not the handle. And Discourse decided to use separate URLs for its HTML and JSON-LD pages, with no way to derive the latter from the former. So to initiate federation with a Discourse category, you have to manually do a WebFInger query to get its URL to then give it to your instance. I think most people probably fail this hurdle, either out of laziness or lack of know-how.
Also, I don’t know about Lemmy, but the Mbin instance I’m using seems incapable of processing Discourse categories anyway. Not sure why that is.
That means Lemmy is entirely reliant on Discourse users replying to posts that are visible to Lemmy, similar to Lemmy-Mastodon interaction. But with less users, hence less overall interaction frequency.
@TheracAriane@thebrainbin.org Should work like communities Search page ->
username@instance(likeTheracAriane@thebrainbin.org) -> it should start fetching it then follow to get new posts federated to brainbin.