In IT it may be the case. In foodtech it is a problem. This may sound reassuring, as we don’t really want much of the stuff being sold in the US here in the EU. But, for new approaches regarding food production the EU regulatory environment is unfortunately a morass. There are lots of regulation which is neither fact or experience based, for example around insects, or ecological labelling.

Looks very interesting. How much work would it be to get this code signed for the Mac?

Not much, but you might want to donate to help the author offset the Apple Developer account cost :^)

I think it's pretty simple. I'm just focused on the core features right now but I definitely plan to sign it in the next 1-2 weeks. Thanks :)

I wouldn't make the Apple Developer dance a priority unless you intend to sell a commercial signed version.

Few reasons.

1. It's 100$ a year, which isn't pocket change when it's making you no revenue.

2. Apple likes to randomly deny developer accounts.

3. They have no issue with outright rejecting apps with vague reasoning.

4. Plenty of high quality raw editing apps already exist for OSX.

If someone really wants to use it on OSX you've provided clear instructions.

I find it absolutely bizarre that people post about stuff they are seemingly have no idea about. Like, code signing & notarization provides clear quality of life improvement for many users. And your reasons are just plain wrong.

1. 100$ is a pocket change for many people. Depending where you live. I think it is enough of a barrier to force a thoughtful action. Also, to compare, cheapest certificates for signing windows software are like 450$/year. Microsoft has a hosted service now for $15/year, but that is still in beta. Both of those options are significantly more expensive than 99$/year Apple charges.

2. No, Apple does not deny randomly access to developer accounts. Also, this is quite besides the poin.

3. Code Signing has absolutely nothing to do with submitting your app to app store, or anything Apple has to approve of. Like, why even write about something you have no idea about?

4. True. Not sure how it is relevant.

100$ a year is a lot of money if you aren't planning I'm selling anything. The instructions to build from scratch or run it without signing aren't difficult.

I've literally had to argue with Apple for months to get my account approved.

It was not a fun process, eventually they did grant me an account, but then just keep up an old hobbyist game I was wasting that 100$ a month.

I ended up just recompiling for WebGL and uploading to itch.

Going through the hoops for code signing and getting account doesn't make sense if OP isn't going to sell it on the app store.

Finally, it's not like this is the only raw editor.

How many people.

A: Will pick an open source feature lite raw editor which isn't going to be as good as Darktable or Lightroom.

And

B: Aren't willing to build from source or literally run a single terminal command to run the unsigned version.

Now, if OP wants to sell it on the app store then I'm completely wrong. But otherwise it's not a good use of time.

You're free to reach out to OP and offer them 100$ + another 300$ for time spent having to apply for a Developer account.

The story misses that lactic acid bacteria are fairly common in honey and seem to be out competing other bacteria and have anti microbial effects.

https://pmc.ncbi.nlm.nih.gov/articles/PMC7949542/

I've recently been embracing the idea of co-evolutionary pressure. Reading the article I thought that if it was just the dryness, bacteria would have evolved to tap such a rich energy source. Hence the biology of bees must have something to do with the preservative nature of honey. I'm feeling vindicated!

I think co-evolution should be investigated for encoder-decoder architecture training.

The idea being that you pair multiple decoders with each encoder, and multiple encoders with each decoder (randomly sample if large populations). The selective pressure is a feedback loop between the encoder and decoder populations that requires the members to produce and interpret the latent vector as well as possible. In theory, this creates a form of generalization pressure wherein the encoders and decoders must perform well with a wide range of possible up/down stream states. I think with large enough populations, this could be robust to premature convergence and overfitting.

I remember playing around with RapidMiner about 10 years ago and it had a hyper parameter optimizing primitive that uses evolutionary search. It was quite pleasing. RapidMiner doesn't do any of the modern stuff though. Asking chatgpt turns up mostly pretty old (abandoned) projects from around 2017.

That looks great!

Do you have any suggestion for how to learn how to hook this up to Logic for anyone who hasn’t used midi before?

I wonder how this would perform under live stage lighting conditions, i.e coloured strong lights and high contrast.

Open the app and open Logic Pro. Create a MIDI track on Logic, try waving to the app it should automatically receive MIDI message from all channels and all MIDI devices.

Then if you want to filter the track to receive specific MIDI channel from specific device, for example AirBending channel 2, then find it in the dropdown in the MIDI inspector section in the same MIDI track.

Very cool. I’ll have to test that.

Started reading a preview of that. It starts really well. Thanks.

We experienced the same when we walked down the hill to go shopping in Laguna Niguel, CA. Stopped by cops for walking to the store. Nothing more happened.

Thanks. That was surprisingly in depth about the different factions and specifically about genejacks

SMS (and equivalent direct messages,I hardly get any spam), missed calls, parking reminders and a few things from my car. The rest is blocked.

It feels like the tools are used as a shortcut to not read documents, and then have the tools produce output from the shortcut taken. What did they accentually learn that they will retain afterwards?

What is this thing for?

That is going to be a hard no in so many contexts. Hospitals, gyms, many work environments, my house, the list is going to be long. We know the companies can’t keep their government from forcing access at some point or another. We also know at some point a zero day exploit will allow pin point targeting of who you want to spy on. We see this already on mobile phones.

Edit: When I read the archive link above I can’t actually see the quote referenced.