Yeah that’s probably the strongest point in favour of letting people pick what they want. But I guess a potential downside of that could be if people start stocking up mostly on only a few select items that everyone else also wants., leaving nothing behind for them. But I guess that’s mitigated by seeing that happen a few times then specifically trying to get even more of those select items going forward.
Yeah that’s a good point. If you can’t see what people are leaving behind, you can’t know what to stop taking more of. I guess you need to generate some short-term waste in order to properly tune things as needed, to hopefully reach a point where you’re reducing waste as much as possible in the longer term.
I wonder if letting people pick their own items really reduces waste more than the hamper system? What happens to items left on the shelf that no one takes? That’s probably the same stuff that would be ignored from a hamper? I’m admittedly pretty ignorant of food banks generally, but I would think that the hamper system would be trying to encourage people to eat whatever they get, to both reduce waste by making sure all items get out there from the bank, and to ensure there’s enough of everything coming in to go around evenly? I can see this maybe resulting in the better items going first, and a bunch of less desirable items always being left behind to rot. Does that tends to happen in this type of system?
Can confirm, I’m living there right now. People here tend to take proper personal responsibility for their own garbage and mess.
You shouldn’t be charged for unauthorized requests to your buckets. Currently if you know any person’s bucket name, which is easily discoverable if you know what you’re doing, that means you can maliciously rack up their bill just to hurt them financially by spamming it with anonymous requests.
Whoever thought it was good at coding? That’s not what it’s designed for. It might get lucky and spit out somewhat functional code sometimes based on the prompt, but it never constructed any of that itself. Not truly. It’s conceptually Googling what it thinks it needs, copying and pasting together an answer that seems like it might be right, and going “Here, I made this”. It might be functional, it might be pure garbage. It’s a gamble.
You’re better off just writing your own code from the beginning. It’s likely going to be more efficient anyways, and you’ll properly understand what it does.
The ending of Soma.
I still have an active Netflix account (for the odd thing I haven’t yet added to my self-hosted Jellyfin instance), and actually downgraded from the Premium tier to the Basic tier a few months ago when they started cracking down on password-sharing here in Canada.
Even though the Basic tier is “only 720p”, I barely notice the difference in quality since my TV (and a lot of other modern TVs) has built-in upscaling that works surprisingly well. And I’m the type that is really picky about picture quality, particular about codecs and encoding methods, and all that jazz. But I’m really happy that I managed to get onto the Basic tier before they removed it. I was prepared for a clear drop in quality in return for cost-savings, and I was okay with that, but was delighted to find nothing had noticeably changed after switching over.
The Basic tier checks all of my boxes, verifiably:
Sometimes I even wonder if my TV is even actually upscaling from 720p, or if Netflix is just quietly serving 1080p in reality, but was just continuing to advertise 720p to deter people from the cheaper plan to get them onto a more expensive one, with plans all along to phase this tier out.
My parents, who were previously sharing my account when I was on the Premium tier, ended up getting their own account also on the Basic tier. The net result is that Netflix makes less money off of the two of our accounts combined now compared to the single Premium account we shared before. So in the end, they ended up losing money, and we lost nothing of perceivable value.
I’ll probably end up cancelling our account at some point entirely, and my parents can continue to use their own account without being affected, so the forced split actually saved us all money and made our situations more future-proofed.
Contrary to popular belief, I actually think that the Basic tier could have ended up seeing more uptake in the long-run had people who only needed a single screen and wanted to save money, decided to try it, and notice that the picture quality was more than satisfactory enough, either due to the stream quality being better than advertised in reality, or due to the pretty good upscaling ability of modern TVs. I’m sure word would have gotten around from technically-minded people to the masses at some point, and we would have seen more people switching.
I’m sure Netflix did away with the Basic tier because they knew it could realistically put a dent in their profits at some point.
Oh yeah for sure. It’s just a matter of time. Out of all of these options, some will just fade away (some already have within weeks of initial release), and some will remain and just continue to get better as the development community continues to get a better picture of where all of the action is, and starts to want to be a part of it.
You’re seeing that toast about versions since backend version 0.18.0 switched away from using a websockets-based API to a REST API, and the Jerboa client app is (in a not-so-descriptive way) warning you that the backend you are connected to isn’t aligned with the app version in terms of what it expects of the backed. This should go away pretty soon as more servers update their backend version and the Jerboa app update hits more devices.
It’s awesome to see Lemmy getting lots of love, and choice in the mobile app space is great for everyone. But some part of me also kind of wishes that rather than spreading so much development effort out over so many mobile apps, that more developers would jump in and contribute to polishing up the official open source Lemmy mobile app, Jerboa. I can’t help but feel that it would be nice to see a focused effort somewhere in bringing that one in particular up to snuff, as a sort of “reference” app. And have a few others floating around out there just for some diversity and testing innovative ideas.
Maybe it’s already that way, I don’t know. It kind of feels like there’s a new Lemmy mobile app announced every couple of days.
I run all of my services in containers, and intentionally leave my Docker host as barebones as possible so that it’s disposable (I don’t backup anything aside from data to do with the services themselves, the host can be launched into the sun without any backups and it wouldn’t matter). I like to keep things simple yet practical, so I just run a nightly cron job that spins down all my stacks, creates archives of everything as-is at that time, and uploads them to Wasabi, AWS S3, and Backblaze B2. Then everything just spins back up, rinse and repeat the next night. I use lifecycle policies to keep the last 90 days worth of backups.
I think the benefit of knowing the names publicly might be the public’s ability to then no longer elect these people, which cuts off the foreign interference at the root, as far as can be done within the country. It might also act as a deterrent for future MPs knowing their names could be released if they too partake in this behavior. It would accomplish stamping out the problem and publicly shaming these people for the rest of their careers.
Not saying it’s realistically feasible or prudent overall to actually release them though.