There isn’t enough AI code out there (yet) to cause this. IMO what’s really happening is that AI Code Review is finding vulnerabilities and creating ways to exploit them way faster than they can be patched by Human Dev teams. An easy example of this is the Linux exploits like Dirty Frag that came out last week and the week before.

It’s going to get worse before it gets better.

The current cost for what they’re calling “windows 365” is $99/yr per user.

Windows 365 Enterprise basic starts $31 per user per month and goes up from there.

I suspect you are confusing Windows 365 with Microsoft 365. The former includes a virtual (Cloud) PC and licensing for Windows and Office, the latter only provides Office licensing. Additionally the price point you quoted makes me think you are looking at Personal / Home pricing because Commercial & Government Office 365 pricing is calculated per user / per month and will vary wildly in price from $10 pu/pm to $50+ pu/pm.

Source.

I’m not the person who made the claim but Device Fingerprinting has been around for decades and Hardware ID is certainly part of that.

https://en.wikipedia.org/wiki/Device_fingerprint

“An estimated 18,000 to 40,000 consumer routers, mostly those made by MikroTik and TP-Link…”

To the surprise of absolutely no one.

This is a fast path to open source irrelevancy, since the US copyright office has deemed LLM outputs to be uncopyrightable.

This is a misunderstanding of US Copyright. Here’s a link to the compendium so you can verify for yourself.

Section 313 says “Although uncopyrightable material, by definition, is not eligible for copyright protection, the Office may register a work that contains uncopyrightable material, provided that the work as a whole contains other material that qualifies as an original work of authorship…”

This means that LLM created code that’s embedded in a larger work may be registered.

Section 313.2 says “Similarly, the Office will not register works produced by a machine or mere mechanical process that operates randomly or automatically without any creative input or intervention from a human author.”

Meaning that LLM created code CAN be registered as long as an author has some creative input or intervention in the process. I’d posit that herding an LLM system to create the code definitely qualifies as “creative input or intervention”. If someone feels it isn’t then all they need to do is change something, literally anything, and suddenly it becomes a derivative work of an uncopyrighted source and the derivative can then be registered (to a human) and be subject to copyright.

In short, it’s fine. Take a breath.

The whole thing doesn’t seem to add up.

Likely because we don’t know what the agreement is between OO and NC. They obviously have one because they’ve been partners for nearly a decade.

and clearly in violation of the idea of the AGPL

Dunno how that could be since the idea of requiring attribution is specifically called out in Section 7, item B.

I guess this is something courts will have to settle.

Almost certainly true.

How can you retain the original logo if you don’t have the right to use their trademarks?

I’m confused by that as well.

This feels like a sleazy attempt to find a loop hole in the AGPL language to restrict commercial use.

That cannot be the case; OnlyOffice has been working with Nextcloud for years to provide interoperability.

If Only Office doesn’t want people to do this, they could have very easily just chosen a different license from the beginning.

I don’t believe that “restricting commercial use” is the problem. In this article OnlyOffice has apparently been having problems with Nextcloud pushing past their licensing boundaries and even soliciting OnlyOffice’s customers directly.

Weird that in one photo the stop marking is in negative, and the next photo the stop marking is white?

The first photo is of the stencil, the second is from after it’s been painted.

You may not but many others DO.

Maybe we can get more people on the Fediverse

Once there’s enough people on the Fediverse it will get noticed by the Authorities and when that happens you’ll see instances start shutting down as they are unwilling, or unable, to comply with the Age Verification and Social Media laws that are being passed all over the globe.

I’m somewhat surprised that the NSFW instances haven’t already been hit by the Age Verification laws that many US States have but as soon as a single state, say Utah, notices the rest of them will pile on and the Fediverse will start to unravel.

This isn’t just a US problem either, there’s Age Verification and Social Media laws being proposed or already in effect in many Western Nations. Hell the two Australian instances are already afoul of the laws in their country so as soon as their Government notices they are going to have some difficult decisions to make.

If they said that about Lemmy i would tell them to fuck off

Lemmy will eventually be targeted by the various Age Verification and Social Media laws popping up all over the globe. More of them are being proposed and passed every week and the confusion and risk just grow higher.

As an example my home instance, lemmy.today, is run out of Washington State and they have proposed legislation that could impact us. HB2112 and HB1834 are just two examples.

Even if none of them pass in WA, and one of them surely will, it won’t too be much longer before the NSFW instances in the lemmiverse start getting targeted by the wide range of States who already have such laws. Instance operators do not have the money to challenge these laws in court so their options will be: comply, shut down, or get fined into oblivion / risk jail time.

I’m not happy about it but in IMO Lemmy is living on borrowed time.

Content like this is why I come here.

4 US states; California, New York, Colorado, and Illinois.

This isn’t about user permissions, its about the operating mode of the CPU.

https://insightplus.bakermckenzie.com/bm/data-technology/brazil-digital-eca-brazils-child-and-adolescent-statute-a-new-framework-for-online-protection-of-children-and-adolescents_2

Colorado and New York will have this same law soon. Brazil already does.

Where in the bill does it say that?

I appreciate that you provided a link to the bill in your previous comment and I’m taking my response directly from there. Here’s a quote of the first sentence of the bill summary.

"The bill requires a developer to request an age signal with respect to a particular user from an operating system provider or a covered application store when the developer’s application is downloaded and launched. " (Emphasis Mine).

Okay so maybe it’s a bad summary, let’s look at the text of the bill. On the 2nd page it says:

“The bill requires a developer to request an age signal with respect to a particular user from an operating system provider or a covered application store when the developer’s application is downloaded and launched.” (Emphasis mine).

Then again on Page 5:

“(2) (a) A DEVELOPER SHALL REQUEST AN AGE SIGNAL WITH RESPECT TO A PARTICULAR USER FROM AN OPERATING SYSTEM PROVIDER OR A COVERED APPLICATION STORE WHEN THE DEVELOPER’S APPLICATION IS DOWNLOADED AND LAUNCHED.”

So yeah, the bill literally says it in both the summary and the text.

So what is an application?

From Page 3 “APPLICATION” MEANS A SOFTWARE APPLICATION THAT BE RUN OR DIRECTED BY A USER ON A DEVICE." Huh, no ambiguity there.

And where would that make sense? What would Notepad or File Explorer do with my age range? That would make no sense at all.

Ask Colorado and California, it’s their legislation.

And yes, as a professional developer I would definetely comply and use this API instead of bothering my customers…

That’s good because if you don’t then you cannot have users in California nor in Colorado (assuming this legislation passes in Colorado).

…every time by askIng them to confirm their age, but since I’ve never worked on any age restricted software in the first place, it does not affect any of my products.

**Why do you think that matters?**There is no exception for your apps in the the Colorado or California legislation! You as a dev MUST comply with this law. If you choose not too then I hope you are prepared to deal with up to a $2,500 fine per user that turns out to be a minor!

“6-30-104. Enforcement - penalties.3 (1) A PERSON THAT VIOLATES THIS ARTICLE SHALL PAY A CIVIL PENALTY OF NO MORE THAN TWO THOUSAND FIVE HUNDRED DOLLARS FOR EACH MINOR AFFECTED BY EACH NEGLIGENT VIOLATION, OR NO MORE THAN SEVEN THOUSAND FIVE HUNDRED DOLLARS FOR EACH MINOR AFFECTED BY EACH INTENTIONAL VIOLATION. THE ATTORNEY GENERAL SHALL ASSESS AND RECOVER THE PENALTY IN A CIVIL ACTION .”

Hmmm, okay well what is an “app store”, maybe your app is distributed in a way that allows you to sidestep the law?

"(5) (a) “COVERED APPLICATION STORE " MEANS A PUBLICLY AVAILABLE INTERNET WEBSITE , SOFTWARE APPLICATION, ONLINE SERVICE, OR PLATFORM THAT DISTRIBUTES AND FACILITATES THE DOWNLOAD OF APPLICATIONS FROM THIRD- PARTY DEVELOPERS TO USERS OF DEVICES .”

Soooo, if you’re stuff is available on Google, Apple, Microsoft, Samsung, GOS, STEAM, EA, or anyone else’s app store you need to comply. If your stuff is distributed from your own website you need to comply. If your stuff is distributed from GitHub you need to comply. If your stuff is distributed via package manager on Linux (that’s a software application!) then you need to comply.

Colorado’s legislation is slightly smarter than California’s in that it at least carves out some exceptions regarding applications for Enterprise, Commercial, and Government use but there are still caveats.

tl;dr This law and California’s clearly and specifically apply to applications as well as Operating Systems, are not “neat”, and its easy to predict that most F/OSS developers absolutely will not comply with these restrictions.

This bill is not “neat”. It literally REQUIRES every piece of software in existence to query for the users age bracket. Do you think that any F/OSS software devs are going to comply with this horseshit?

As near as I can tell the HP PSC 1315 was released in 2004, over two decades ago. I can see how it’s aggravating for you but there can’t a double handful of those clunkers still working anywhere in the world. There’s no way it could be worth it to HP to rewrite drivers for the 10 or so people still using them.

Switch to Linux. :)