Would you pay a yearly fee to continue getting updates for your now no longer being updated but perfectly fine otherwise phone? I would.

Good question. At that point I’d explore replacing the OS altogether with GapheneOS or LineageOS.

When it comes to cars though, I don’t find FSD an appealing enough value to continue paying (or even begin to pay in the first place). But to your point, that doesn’t mean Tesla shouldn’t price it how they want and people to buy it if they wish.

I see where you’re coming from. And I also agree with the subscription heated seats.

I think we might actually be advocating for the same thing lol. I was making the argument that manufacturers should have a one-time price for things that are packaged along with the product (with the exception of features like FSD that requires a continuing service to operate and evolve), but jailbreaking static features like heated seats is fair game.

However, your post got me thinking… If it is reasonable for FSD to be a subscription model, how are FSD updates different than, let’s say, your phone having updates and security patches? We don’t currently pay for new versions of iOS or Android. Granted the complexity and stake of FSD is greater than a phone, it is similar fundamentally

Your original reply stated that “including heated seats and making you pay once to access it is fair game” is what prompted my reply. Users shouldn’t be paying for it if it comes with the product, disabled or not.

I have no qualms about subscriptions for FSD due to continuing developments and improvements, and the fact that it requires a service running AI/ML models to operate. However the drastic subscription cost changes over 3 years raises an eyebrow. From $5000 in 2019 to $15000 in 2022 is quite a drastic change. They certainly have the right to price how they want, but definitely an insane pricing model.

If you pay to add a feature to a product that was previously not available, sure, that makes sense. But in this case, at the point of the transaction, and they hand over the keys, the ownership of the product is now 100% transferred to the customer. They should and can do whatever they want with their property. A manufacturer equipping a feature because it’s cheaper is frankly not the customer’s problem.

Imagine buying a house but you only get access to certain rooms. They set the price, the customer just pays for it. If they want to cover the cost of adding the heated seats feature, then add it to the starting price.

I’m not advocating for anyone to buy a price they’re not comfortable with, but personally I reasoned that, having used Sync for nearly 10 years, it would be like paying 10 bucks for each of those years for an app that I have used the most out of all the apps in my life

Sync was a huge part of my life (will continue to be), and I am happy to compensate for that.

That is AWESOME! Congrats!

Yes that’s right, portainer stacks equate to compose… I might be wrong, but I remember reading somewhere a while back that they (and other container orchestration tools) were not permitted to reference “Docker” or its products (including compose) due to legal and licensing restrictions by Docker.

Not to the level of Reddit, but Docker has its fair share of questionable business decisions.

Portainer is definitely useful (I use it on a daily basis), but probably a bad place to start…

I started with the following progression:

1. Docker CLI
2. Docker-Compose
3. Writing my own scripts to build and manage docker-compose configs (purely optional and skippable)
4. Portainer
5. Purely optional, but in a professional setting, kubernetes and various container orchestration tools.

Good luck in your journey!

I took a look at Dashy, I think I see the confusion. If you are looking at this article, then yes they mention Code Server, but that’s purely in the context of using Dashy in a non-docker context. But to be honest, any text editor works.

But I think that’s a red herring. That in itself has nothing to do with docker.

What you’ll need to do, once you understand the fundamentals of running docker, pull images, start a container based on an imagine, is to expose a docker volume that points to /public/conf.yaml. A docker volume ensures that the file or directory it’s mapped to in the container is available and persists outside of the container. This allows you to persist files and directories without losing them once the container stops or restarts.

Once the volume is exposed, then you can use your favorite text editor to update the dashy config file. Code Server is fine, powerful, but overkill.

But first, try getting familiar with pulling, starting stopping docker images using the cli. Gotta start there first before tinkering with docker parameters like volumes.

I hope you realize that many innovations we use today on Earth is thanks to innovations created for space exploration. It’s unfortunate that many don’t seem think be able to see that.

https://en.m.wikipedia.org/wiki/NASA_spinoff_technologies

Given the sheer amount of data on Reddit, this is really not feasible nor scalable, nor is a long term solution. A simple CloudFlare configuration will quickly put an end to such a solution.

RSS exists, however only allows you to subscribe to subreddit posts, not comments.

This is why the API changes are such a big deal.

I’m currently juggling 3 different apps to find one that works best for me (Jerboa, Connect, wefwef.app via Hermit, and excitedly waiting for Sync for Lemmy). I’m also experimenting with setting up my own instance to learn more about federation.

I love the principle/values of Lemmy, what it stands for, being part of a growing platform and learning about it. But when I’m just looking for mindless time-wasting content to kill boredom, I find myself missing the quality of experience, the communities, the level of engagement and diversity content from Reddit. Many subreddits I used to follow for “dumb” content simply don’t exist on Lemmy, and I doubt it will gain inertia on Lemmy.