Pamasich

reluctance to stop dealing with Russia

Can you name examples?

We did always implement all the EU sanctions afaik.

In case you meant us not using Russian assets to help Ukraine like the EU does, iirc they’re using interest, not the actual assets, for that. Which I remember reading (but don’t have a source right now) isn’t possible for Switzerland due to how they are stored in commercial banks rather than central repositories. And just seizing them would be illegal. It’s not like we don’t want to (though that’s probably a factor too), but more like we can’t.

The Nazi gold is still very much a thing.

The Nazi gold was given back. It’s very much not a thing anymore. And back to the jews I mean, not Germany.

@TheracAriane@thebrainbin.org Should work like communities Search page -> username@instance (like TheracAriane@thebrainbin.org) -> it should start fetching it then follow to get new posts federated to brainbin.

How is it only a half solution?

The headline matches the article. So if the Verge is wrong there, it’s the entire article that’s wrong, not just the headline.

You’re conflating two changes the article claims they’re making. Do you have another source that you’re basing this on?

This article outlines two changes:

• a workflow for experienced users to install unverified apps, with safeguards in place to prevent scams
• a new account type for students and hobbyists that doesn’t require verification

This article is worded to make these two appear as individual changes, not the same change.

The company says it is now developing an “advanced flow that allows experienced users to accept the risks of installing software that isn’t verified.” This installation flow will include safeguards to protect people who are being coerced into installing a dangerous app, or tricked by a scammer, along with “clear warnings to ensure users fully understand the risks involved.”

Google is also working on a new developer account type for students and hobbyists, which won’t have to go through “full verification requirements,” but will only allow app installs on “a limited number of devices.”

Note the word “also” in the above quote.

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.

There are some platforms here that do have a karma system. Mbin does, and I think Piefed iirc had a similar but not same scoring system for users too.

This is the fediverse, I recommend finding peace with the fact you’ll run into different customs here.

OP created a microblog post, which means Mastodon is the target audience, not Lemmy. For Mastodon, it’s essential to include mentions, even to the person you’re replying to, because otherwise Mastodon won’t notify the user of the reply.

Since Mastodon is the target audience here, OP probably also expected replies to come from that side of the fediverse, not the threadiverse. Their instance by default doesn’t display your instance’s name next to your name, nor does it display your software there. So they probably weren’t aware the user they were replying to used Lemmy. Hence the mention.

We’re on the fediverse, get used to there being differences like this. Especially if you’re on an instance which portrays everything the same.

In this case, you’re looking at a microblog post and its replies, not a thread. It’s still posted in a community, because the user uses Mbin which does still require posts made from it to be associated with a community, and that’s why Lemmy displays it as a regular thread. But it’s not.

Since OP uses Mbin, which supports both, this being a microblog post specifically suggests their target audience is Mastodon, and they expected to get replies from Mastodon here. On Mastodon, explicit mentions are essential, as that’s how Mastodon decides whom to notify. The replied to user doesn’t get notified unless they are also mentioned in the post.

Mbin’s default behavior doesn’t help here, as it doesn’t show a user’s instance (so you have to click through to people’s profile to see their software, which OP probably doesn’t do, I don’t either), and includes the mentions by default for microblog replies (so removing them is more work than leaving them be).

something they wouldn’t dare do if Biden was still president and Lina Khan was still head of the FTC

Pretty sure the user folder has been onedrive for ages, including during Biden’s presidency.

Not everything is about politics.

You’re aware you can just link to all relevant pages in a single post, right? You can add links to your description.

programming.dev is a Lemmy instance, right? Then you should be able to use masked links via Markdown too. Like this: [text](link), it’ll display as clickable text.

What the person you’re arguing with is annoyed by is that you’re making a new post for every page you think is relevant. When you should be making one post that says all you want to say and links to all the pages you want to link to.

Depends. If you get Gruyere in the US, there’s zero relation to Switzerland there. The US declared gruyere a generic name and so its Swiss or French name protections are void there and thus no guarantee about origin is made.

In the EU there’s the difference between (Swiss) Gruyere and French Gruyere which are quite different according to Wikipedia.

However, JPlus is not merely a “preprocessor.” It actually parses Java source like a compiler, performs null-safety checks and boilerplate code generation on the generated parse tree, and finally produces standard Java code. In that sense, JPlus should be considered a compiler. The only difference is that its output is Java code

A preprocessor is basically a compiler which produces input for another compiler. Yes, it’s a compiler. The difference is that it produces source files, not bytecode.

From Wikipedia:

In computer science, a preprocessor (or precompiler)[1] is a program that processes its input data to produce output that is used as input in another program. […], which is often used by some subsequent programs like compilers.

The emphasis is mine.

Both Typescript and SASS are examples of preprocessors.

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.

Kotlin isn’t a superset, you can’t just compile a java file with kotlin and have it work afaik. That seems to be the point here.

This is more like a preprocessor anyway, like SASS to CSS. The compiler spits out Java source code, not jvm bytecode.

Notably, there is currently no ‘superset’ language that keeps Java syntax almost intact

There’s Groovy. Their examples use a bit different syntax, like a lack of semicolons, and Gradle might also give the wrong idea. But it’s fully compatible with Java source code iirc, just adds its own stuff on top and broadens the allowed syntax a bit.

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.