Oh the irony of this comment.. calling others hypocritical and stupid when they themselves don't have the full context into the reason people beg for Sync... The irony is too strong
Nope, because I don't have an issue with paying for something that I like and enjoy. Don't like to pay? Nobody is forcing you to. Stop lambasting others for their choice.
I'm all for FOSS (currently working at a company that contributes heavily to FOSS) and am a huge supporter/contributor of FOSS, but the level of entitlement and superiority complex that I've seen from many in the FOSS community (including yours) is highly unappealing, and at times frankly revolting. That's what truly reeks and stains FOSS.
I guess it's a matter of perspective and subjective. I see it as paying back for a decade of practically free Sync experience for Reddit that I absolutely enjoyed, and as such I'm compensating the dev for that. Not saying others should apply the same logic (they shouldn't). But it being a scummy practice is really up to what posting users interpret as value.
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.
Same. The current price of Sync Ultra lifetime distributed over a decade of some of the best, consistent and polished experience I've seen in an app is gladly something I'd pay (and have already paid) just to support and thank lj
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.
As a Sync user, I support this comment. The fact that these debates occur is precisely due to the fact that people have the freedom of choice, and that's something to celebrate.
Sync doesn't have to be "better" or "worse" than other apps and vice versa. People should pick what they like. I pick it because it feels like home after having used it for almost 10 years. Doesn't mean it's better.
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.
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.
But continue evangelizing.