Pretty cool! I've also been playing around with GLM 5.2 this week and was equally impressed. At work we're running it locally on some crazy expensive hardware as a test before starting another project so it's great to see people taking this massive FOSS model release and running it on an average machine, even if it's not terribly practical at this point.
I prefer CoMaps' tile styling, they did a bunch of updates to it early on to differentiate it from OrganicMaps, IMO it's much nicer.
CoMaps also has a better system for distributing map data now which isn't bound to app updates. Not sure if this has made its way back to the other app, but it's quite nice.
I've been using GLM 5.2 a lot this past week, it's been replacing Opus 4.8. I mostly do front-end web development and haven't noticed much of a quality difference.
Sure, "it's just frontend", but that's actual use enough for me to take it seriously.
Yes, CoMaps lets users submit basic data that updates OSM for addresses and POIs. It's a harder problem than you may initially think too, quite often the delivery format of OSM data differs in schema from the DB format. In the case of OrganicMaps and CoMaps, they both generate offline-optimized map formats for distribution.
Navidrome is so sick! I've been a full album listener for years, but switching to it was a great excuse to make sure my music library was FLAC only and tagged with good MusicBrainz metadata. If you're a self-hosting / NAS person already and you have a music library of digital files it's a no brainer.
Brand guidelines and web design pretty much don't exist any more as far as I can tell. Gotta get it out yesteday, and the only way to do that is vibe coding, styling be damned.
Noticed that Jellyfin had inched out Plex when sorting by popularity on the TrueNAS app catalogue the other day (45,178 installs vs Plex's 42,225). The existance of this project seems to confirm that the dev ecosystem around it is getting stronger!
I got Claude to make me the exact same graph a few weeks ago! I had hypothesized that we'd see a sharp drop off, instead what I found (as this project also shows) is a rather messy average trend of outages that has been going on for some time.
The graph being all nice before the Microsoft acquisition is a fun narrative, until you realize that some products (like actions, announced on October 16th, 2018) didn't exist and therefore had no outages. Easy to correct for by setting up start dates, but not done here. For the rest that did exist (API requests, Git ops, pages, etc) I figured they could just as easily be explained with GitHub improving their observability.
I'm going to guess this is because the image to depth data, while good, is not perfectly accurate and therefore cannot be a shared ground truth between multiple images. At that point what you want is a more traditional structure from motion workflow, which already exists and does a decent job.
I think SideFX was the first to do that with Houdini. It's one of my favourite micro-UX features of high-end graphics software, coming in at a close second to Nuke's use of both linear and non-linear scales for slider values.
Yes, and when working with footage shot with anamorphic lenses one will have to render the footage as non-square pixels, mapped to the square pixels of our screens, to view it at its intended aspect ratio. This process is done either at the beginning (conforming the footage before sending to editorial / VFX) or end (conforming to square pixels as a final step) of the post-production workflow depending on the show.
What a bummer. It seems like what they're asking for here (a written agreement that users will be able to access 3rd party app stores) would be a win win win for Core Devices, Rebble, and users. Core Devices gets to look like a super good guy (ideally driving interest in the product), Rebble gets to look like a huge winner maintaining something for the community (as they are), and users get an open ecosystem.
There's still a chance for a win here, but looks like the door is closing.
You can see everything in your field of vision, but the area DIRECTLY in the centre has the highest level of detail. This image has high frequency animated details that are not cognisized equally by your entire FOV. The animated bit right in the middle at any given time is where your brain processes the most detail and also where you are looking.