• 5 Posts
  • 115 Comments
Joined 1 year ago
cake
Cake day: August 15th, 2023

help-circle





  • I’d lean towards option 3. I view this site as an aggregator and I see plenty of broken images when scrollling through here. It’s not your job to host or proxy those images and working in infrastructure it lends to a lot lighter weight instance that’s easier for you to manage without having to worry about disk, or even worse, bandwidth costs.

    The only way I would see option 2 being more beneficial is if it was truly a temporary cache solution where the image gets pulled in 1 time, served out to all lemm.ee users for a period of time (say 24 hours). This would reduce the chance that you end up rate limited, while allowing users to still see the image served via lemm.ee

    The proxy on every request solution just seems poorly implemented to me for the reasons you say.







  • There’s nuance to this article. The cost is for the connected services portion, which usually includes the fee for the cellular connectivity the car has to enable the services, that’s not free and there is a cost to maintain that infrastructure. Additionally the “workaround” that someone provided still uses those connected services (again, not something that is just free to maintain).

    The shitty part that comes in is that Mazda removed the key fob remote start option from their newer vehicles. That being said though, nothing in the above statements is centered around “right to repair”. If you don’t want to pay for the connected services, then don’t, everything else in your car will still work.

    About the only way you could argue for it is a “bring your own SIM” approach but even then, where would it connect to? Who would pay to maintain that? You’d have to allow it to connect to a custom endpoint, but at that point guess what: you’re paying for the cellular connectivity and the server to host an API on to do what you want. That’s still an additional cost beyond what you paid for the car just like the connected services fee.