I assumed it was a shitpost, instead it is a real tweet. What a time to be alive.

Jokes aside the only real reason I can fathom for the collectibles company to call their mother is because they had used it as the contact number in the registry. I would be surprised if this was some kind of intimidation tactic instead of just miscommunication - in the sense they probably just wanted to legally intimidate the itch’s owner not their immediate family. They are not 2K ^/s.

I was reading @superkret@feddit.org and @MaggiWuerze@feddit.org exchange and I found it an interesting - albeit moot - topic. So I went and spent the last hour to download some data and filter it: I will post some numbers with no commentary. I will add my opinions after them in a spoiler.

imf.org GDP, current prices, Billion of U.S. dollars

2023 GDP Nominal
NATO 52392,344
BRICS 27330,345

2024 GDP Nominal (estimates)
NATO 55148,819
BRICS 28442,630

imf.org GDP, current prices, Purchasing power parity; billions of international dollars

2023 GDP PPP
NATO 63996,245
BRICS 66010,889

2024 GDP PPP (estimates)
NATO 66812,821
BRICS 70911,69

imf.org GDP based on PPP, share of world

2023 GDP PPPSH
NATO 34,731
BRICS 35,824

2024 GDP PPPSH (estimates)
NATO 34,339
BRICS 36,446

BRICS

Brazil, People’s Republic of China, Egypt, Ethiopia, India, Iran, Russian Federation, South Africa, United Arab Emirates

NATO

Albania, Belgium, Bulgaria, Canada, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Italy, Latvia, Lithuania, Luxembourg, Montenegro, Netherlands, North Macedonia, Norway, Poland, Portugal, Romania, Slovak Republic, Slovenia, Spain, Sweden, Republic of Türkiye, United Kingdom, United States

Actually Obtainium is mentioned (but thank you, checking back I saw I had a typo in the github link that I had missed, and I’ve now fixed it!), but this is the first time I hear about Accrescent: is it this App store?

You are right, and I forgot to add the link to it in the opening post. I’ll edit it in!

Silverbullet is like that. It is not an electron or native app, you have to run a server and then get to it from the browser.

TLDR it is best run with docker or podman, but IMHO it is pretty good.

It says it can lead to health issues… Not that it will… soooo…

I find it funny that this is the first video where I’m consistently getting the “This helps us protect our community” and “Log in to confirm that you are not a bot” errors while using an alternative Frontend.

I’m sure it’s just a random coincidence, but it is still funny to me.

This was an interesting question, so I took a quick dive in the docs, it seems it has an S3 integration to help with it, and some comments on the various supported services

More info here: https://owncast.online/docs/storage/

Still, depending on the chosen provider and the amount of viewers, it could be quite costly

On the contrary, in my opinion if they are clearly labelled as a joke, they are a great way for people who don’t understand them to ask why and, in the process, being a little more informed on what not to do and what it’s dangerous.

Especially because there’s really no risk of emulation in this case.

Could you consider using ISO 8601 style dates (YYYY-MM-DD) ? Or words for the months?

Aside from that: great job!

I feel there’s some kind of miscommunication going on here.

Probably I’m not understanding what you are putting forward, but to be clear: They are not doing this because they want to. They are doing it because they are forced to do it by the DMA.
It’s true that allegedly they were working on some kind of interoperability layer already. For years now. But no evidence of it being more than lip service to avoid being regulated has ever surfaced - as far as I know.

Which would have been in line with your “Do Nothing”.

as an unwilling Whatsapp user the ability to migrate without having to convince all my social circles to do anything but check a checkbox sounds like a huge step forward.

That’s the point. I feel it will not be a “simple checkbox”, and they will make it the most obnoxious process they can using the Best Dark Patterns the industry has to offer.

Already the general public is not interested in the alternatives or the concept of interoperability - wanting something that Just Works™ - putting in front even the smallest step (and some scary text!) will make the percentage of willing people become even lower.
And that’s not all. As it is portraited in the article by the Threema’s spokeperson it is pretty clear that Meta will just try to make the maintenance of the communication layer as cumbersome as they can - both technically and bureaucratically.
They are explicitly the ones keeping the reins of the standard, the features, the security model, the exchanged data and who, how and when will be approved.

So from one side if they make it hard and scary enough to tank the use rate, they will have the excuse of not being there enough people to give priority to fix it or add features, and from the other side if maintaining the interoperability will be difficult and time consuming enough, the people and businesses from the alternatives or wrappers will not have the incentive to do or keep doing it for the long haul. As we can already see in the article.

Is it better than nothing? Sure, probably. Will it be a slow cooking, easy to break, easy to get excluded from, just bare minimum to comply to the letter but not the spirit of the law? I feel that’s a pretty good bet to make.

Let’s be clear: I will be extremely happy if all the red flags and warning bells that I saw in the article will just end up being figments of my imagination. But yes, I’m very pessimistic - maybe even too much - when I see these kind of corporate speech and keywords.

“One of the core requirements here, and this is really important, is for users for this to be opt-in,” says Brouwer. “I can choose whether or not I want to participate in being open to exchanging messages with third parties. This is important, because it could be a big source of spam and scams.”

Let me translate this for you: "We will make users hop on the most cumbersome, frustrating and inefficient way we can think of to enable interoperability. And making it defaulted to off will mean people using other apps will need to find other channels to ask for it to be enabled on our users’ end, making it worthless.

And don’t forget: we will put a bunch of scary warnings, and only allow to go all in, with no middle ground or granularity!"

Great stuff, thank you. I can’t wait.

“We don’t believe interop chats and WhatsApp chats can evolve at the same pace,” he says, claiming it is “harder to evolve an open network” compared to a closed one.

Ah, so they are going for the Apple’s approach with iMessage and Android sms. Cool, cool.

I hope my corporate-to-common translator is broken, because this does just sound bad.

…is that a Goa’uld? Scary!

Yeah. GDPR should have been implemented as a mandatory part of HTML or even HTTP that interacts with a builtin browser feature.

Well, it kind of is. The Do Not Track header has recently seen a court win in Germany (source):

It turned out that the judge agreed with vzbv, ruling that the social media giant is no longer allowed to warn users it doesn’t respect DNT signals. That’s because, under GDPR, the right to opt out of web tracking and data collection can also be exercised using automated procedures.

And it is basically the same in California too Source

GPC is a valid do-not-sell-my-personal-information signal according to the California Consumer Privacy Act (CCPA), which stipulates that websites are legally required to respect a signal sent by users who want to opt-out of having their personal data sold.

Any foundation model is trained on a subset of common crawl.

All the data in there is, arguably, copyrighted by one individual or another. There is no equivalent open - or closed - source dataset to it.

Each single post, page, blog, site, has a copyright holder. In the last year big companies have started to change their TOS to make that they are able to use, relicense and generally sell your data hosted in their services as their own for the intent of AI training, so potentially some small parts of common crawl will be licensable in bulk - or directly obtained from the source.

This does still leave out the majority of the data directly or indirectly used today, even if you were willing to pay, because it is unfeasable to search and contract every single rights holder.

On the other side of it there have been work to use less but more heavily curated data, which could potentially generate good small, domain specific, models. But still they will not be like the ones we currently have, and the open source community will not be able to have access to the same amount and quality of data.

It’s an interesting problem that I’m personally really interested to see where it leads.

Give technitium a go, my woes diminished drastically with that.

The Dark Crystal (1982)

You should add some mushrooms in it.

I don’t know why but they are on a separate branch: 0.18.5_release_notes

Reading the commits it seems they want to keep them on join-lemmy, instead of having a changelog/releases file in the github.

They first added the 0.18.5 changes and then deleted the full content of the releases file and put to go to https://join-lemmy.org/news