

it goes back a while
It goes back at least to my teen years, which is… not remotely recent. (Edit: 90’s for the record)


it goes back a while
It goes back at least to my teen years, which is… not remotely recent. (Edit: 90’s for the record)


One of the reasons my pref is unpriveleged lxc.


Definitely suggested then, you’re also going to get drastically more features. If you remember a time when Plex plugins were available - its that. And more flexible.
Any intel-based chipset past 6th gen or so will be ok, 7+ recommended, 10th+ for AV1. If you aren’t doing any transcoding, just about anything will work include a pi.
This is what I’d do, but youre going to be limited to 2.5" + m.2 in the ultra small form factors (USFF, more NUC sized), while the SFF size you can get one (sometimes two) 3.5". So make sure to check the form factor of the machine!
Tons more computing power in either case, and the most reasonable price point IMO.


Only a little as far as animal health goes, my wife knows a lot though, and she knows quite a few vets who have let me abuse them with questions :) Majority is as I go along though for the non-tech side.


Similar but not the whole thing. I’m identifying more broadly (deer, horse, chicken, etc) but more focused on their movement and condition. Are their coats are healthy, their movements normal, so on.
Classification then changes which CV model is used to evaluate the rest.
Right now they are too big to be fast enough, and going smaller is breaking the model. N9t because there aren’t unnecessary bits to trim out, but because I’m not doing a good enough job at minimizing what’s actually needed.
I’ve been working on it for a while now, but still have a long way to go unfortunately.


In terms of my setup, there was basically no impact. I use Debian (servers and some workstations) and Arch (couple of laptops and a couple of miscellaneous task-oriented devices I want more recent builds on than Debian will give me)
Work? Different story, so much manual updating!
Otherwise just regular stuff this week like backups (monthly incl since yesterday was the 31st), reviewing changelogs for minor updates, etc.
Hit a bit of a wall in my animal identification tools I’m making, so I’m going back to do some more reading to see if I can find a way to improve efficiency more and make it smaller while maintaining accuracy.


Client dependent as to whether it shows the community its cross posted from.
Mostly because that crowd likes to come in and downvote anything they notice ai-related in any way, shape, or form, or they post comments I’ll need to remove. Despite tags being added so they could choose to filter those posts out instead.
Its less about the post and more about the general behavior of some people in that comm.


I’d prefer a new post there over a cross-post from here, personally.


Considering the vulnerabilities that have been found just this past year, I sure wouldn’t. Use a VPN.


I love seeing these updates Daniel! The new statistics page looks great, I’m going to give my local instance an update and check it out


Ah - that changes the perspective a bit, I’ll have to check it out later


Asahi is great, you can just run whatever.
Mine is mostly a host for my self- created small scale models, but its also a great jellyfin server. The M series is pretty solid for that, or really anything that has GPU loads is good (immich f9r example).
The m -series is great in terms of low power and solid output, highly recommended.


Since your last post, a few rules have been added, specifically adding the appropriate tag in the title, and an ai disclosure if required (and with Claude as a contributor, it is).
Please take a look at rules 7 & 8 and update accordingly, then send me a message.
Edit: all updated and unlocked


I believe they are pointing out that its “minefield” not “mindfield”.


Privately held, but venture capital backed.


Oof, this is worthy of its own post for the Plex users out there:



Please update the title with [AIP]
With my particular unit? Its not going to get any updates ever, the only way to install is over ADB, and changing the running app requires script changes and a reboot (or changing things to allow the on-screen navigation buttons, but that comes with other annoyances).
So sdk version isn’t changing, which is a potential compatibility issue going forward.
Its part of our rules here - take a look at rule 8.
It was recommended for !opensource@lemmy.ml not that long ago iirc, though I don’t know that they’ve adopted it.