Counterfeit

It’s spelled correctly right there in the title.

I tried Grocy for a while, but eventually stopped. Data entry was a huge pain.

Using the iOS companion app to scan grocery items into the app resulted in data issues that prevented me updating the item in the web app later. The only recourse was to add the items by hand in the web app, but then go in to each one separately with the mobile app to register the barcode. This also resulted in losing the additional metadata about the products that the mobile app would automatically configure if you onboarded the items through the mobile app, as it was able to look up additional data online and prefill a lot of stuff.

At the end of the day, it was too much of a hassle. I do like the idea, and may come back to Grocy again, but for now I have to pass.

Yeah it’s Traefik for me as well! Heavy docker user, of course - it’s nice just tossing some labels into my Portainer stacks and letting Traefik figure it out. If I wasn’t so invested with containers I’d be using nginx.

Clickbait title. What the article says is that honey made by Kelulut bees, which is considered a premium product, is being counterfeited by taking regular honey and adding things like vinegar to it to try and make it taste the same.

The honey is still real honey, it’s just not made by Kelulut bees.

If saving money is a concern, and I had an iPhone 12 (actually I do, but just the regular Pro, not the Max) then I’d stick with what I had, for a number of reasons. The big two being a) existing investment in the ecosystem - most of us have spent hundreds of dollars on apps over the years, and b) the iPhone 12 is not bad tech, and should last for years with nothing more than a battery replacement.

All the *arrs are in the same Github repo.

It’s not as relevant today as it used to be, that’s for sure. Originally it was to limit transcoding of 4K content (which used to be a lot harder), and also to avoid the HDR tone mapping issues with 4K content during transcoding, both of which are largely resolved with newer hardware and Plex software updates.

The only reason I keep them separated now is because most of the folks I share with can’t direct stream 4K content anyway, and so I only share out the 1080p libraries in Plex. It keeps bandwidth usage down and limits having to go to hardware transcoding, which can reduce quality and introduces startup delays. The library I use locally indexes both the 1080p and 4K content, so Plex will always prefer the 4K if it’s there.

If diskspace ever became an issue, I’d probably consider merging the libraries again.

You’re taking it too literally, and missing much of the nuance between philosophy of design and actual implementation details.

The movies app manages movies. That’s its one thing. No need to overcomplicate it. Unix ‘find’ for instance, finds files. That’s its one thing. ‘find’ also lets you filter the results, but that doesn’t change its purpose of finding files.

The fact that *arr apps don’t do things, or are bad at things, has nothing to do with the Unix philosophy. Were these apps combined into a monolith, the same issues would need to be addressed.

There is no right or wrong in a design philosophy. It’s all trade offs. I don’t know anyone who says Unix (or the metaverse) is successful because of a design philosophy. What matters is what you deliver.

I do wish I didn’t need to run a second Radarr instance to have both 1080p and 4K media.