I work writing analytics and monitoring for industrial equipment. We have hundreds of sensors sending back realtime data.

There was a period of time where people were writing alerts for the sake of it (i.e we have this sensor, when should we alert on it).

Nowadays we're strictly failure mode driven, this has meant lots of sensors aren't used in the analytics. They are however available to the experts to plot them for a more holistic view if required.

We went through the same switch. Half our alerts had been firing for a while and nobody ever acted on them.

Not the original commenter. Just thought I would comment here. I'd be super interested in reading more information in why Bitwarden Lite is inadequate vs vaultwarden.

I don't self host Bitwarden so 90% of this doesn't really apply.

I did however want to comment on the tab changing it's favicon and title everytime you change to another tab. Quite a cool "advertising" method for what javascript can do.

Yea that threw me too. Very clever.

If the data is opensource on github, then in my opinion it should be fair game.

IMO this is unfair for GPL or similarly licensed code.

Seems ok for MIT like licensed code though

There's no difference. Either you need to follow the license or you don't. MIT has requirements still.

It's totally fair to use GPL code, it just means all the models built by Anthropic, OpenAI, etc. using GPL-licensed source are themselves bound by the GPL. Plus, any works created downstream using those AI tools.

We're on the verge of a golden age of software as soon as someone finds a court with courage.

Ah, you have much more faith in the legal system than I do. It's nice to dream, though.

I think AI will create an open source dark age. Gradually, we'll see a lot less new good open source code. A gradual shift back to the proprietary world. Simmilar to the 1950-1990 period.

Why would giving more people software freedom and the ability to reverse engineer nonfree code result in a dark age?

The data is not open source. They have open weights but the source data is never open.

I feel that's a false dichotomy. The code on github is freely available for people to read and learn from, leaked medical data isn't.

I feel that's a flase dichotomy. The code visible on github is freely available for anyone to read and learn from.

So would be your leaked medical record.

The point is not that this situation seems absurd. The point is that we need some point where we say whats ok or not.

And by ignoring licensing of public code already we moved it closer to the worse end of the spectrum

There are rules. I believe that search engine indexing follows these rules and that so called "training" is search engine indexing.

But a court may differ in the future.

Where do you draw the line though? They have an amazing reputation for quality fan products, they clearly feel it needs a new injection mould which aren't cheap investments.

I've got a Noctua NHD14 in my current build that I bought in 2011 and it performs perfectly still (including 2 free socket upgrades from Noctua).

> Where do you draw the line though?

When the additional engineering adds no extra end user value. e.g. You need the blades to be strong enough to not shatter or flex, but beyond some level of strength it adds no additional utility

Yes and no. At a holistic level yes but for the product Noctua produces they've designed in a specific tip clearance which they want to maintain with the different pigments for their efficiency/acoustic targets.

I work in a more traditional manufacturing business and we are poorly inplementingal AI tools allover just because our customers ask about it...

You should care because the install base could reduce drastically. Reducing the amount of Devs and contributions to the FOSS scene. This will degrade your experience

Agreed. I use meshcore and have multiple repeaters setup. I don't care about people using ai assisted coding but I think it should be disclosed especially if its closed source.

Now the trademark take over seems crazy especially given Andy hasn't contributed to the github project, only personal for profit add ons.

I do also think that the meshcore core team have "tacked on" and tried to enforce a stronger narrative with their anti ai coding bias.

It wasn't ai assisted coding, it was vibe coding from someone with no real coding background. A communication protocol can't be vibe coded, how do you enforce security if the person is unable to understand what the tool created?

Especially when they try to hide that they were using those tools in the first place

>It wasn't ai assisted coding, it was vibe coding from someone with no real coding background.

Can you elaborate on this?

I'd agree that is problematic. But that's not what the article said. The article just said he was using Claude Code a lot. It's ridiculous to equivocate those two things. That's what I have an issue with.

> only personal for profit add ons

In that context it is quite logical to take a trademark out once the project is mature enough so you can profit off other people's work.

Considering their user base does not like the hidden vibe coded idea I don't think this is bias but a sane rationalisation.

There’s a lot of framing in how questions are asked. I’m going to bet asking the community “Would you like more features if they’re made using AI assistance?” is going to get wildly different results.

"AI assistance" isn't really an honest representation of the claim of what happened is, though.

"I wrote an iPhone app, so now I have the right to trademark 'Apple'."

Yes but it's truly impressive to see it. It shows it can be done.

An 11th gen CPU/mobo that came out in 2020 can be dropped straight into this new chassis.

Or the newest display be can be dropped into your 2020 laptop/chassis.

I wish they booted them up in that video. Its one thing being able to plug parts in but its another for them to all work together.

Based on my experience upgrading my FW. There's probably drivers and bios updates needed to do the transfer

Back in 2002 I took the HDD from one PC, put it in a different PC, worked just fine. The worst thing that could happen is that the other one already had another disk so I had to change /etc/fstab to say "hdb" instead of "hda" and vice versa. Didn't take long for that to get fixed by specifying UUIDs and having initramfs sort it out.

IDK why it's not working for you but this should all just work without bothering with any configuration, drivers, or whatever.