I have no qualms about building for the future and educating. I fully support that. What I don’t support is the brigading and the lambasting of users who choose to purchase closed or proprietary products. That is their right as much as it is yours to advocate for FOSS.

If “taking everything from us” is the issue, there are appropriate channels and mechanisms to defend against that. If you don’t want your FOSS software to be used in a priority setting, apply the correct licensing models and pursue legal paths. GPL-licensed FOSS is generally and effectively avoided by for-profit organizations. If you purposefully choose MPL or Apache for your license models, that’s really your responsibility for legally protecting your FOSS IP. Apply the right licensing model, it is literally a single button to change it if your source is on GitHub.

I’ll be transparent as to why I paid. And I only speak for me, not any other Sync user. Sync has been the app I used the most in the past decade. Sync has been what I - personally and subjectively - found to be my ideal android app experience, above all other apps. The majority of the time my phone is on is with Sync open. And this was all for free, for nearly a decade.

Reddit has taken that away from me. And the reason I’m willing to pay is to compensate the Sync dev for the value he has personally given me. While I believe in FOSS, I believe more in the principle of fair trade. And I have judged that, in my specific circumstance, he has given me more in value over the past 10 years than the price he currently asks for. And again, I only speak for myself.

And yes, the source of information comes from the serving platform (whether that’s Reddit or Lemmy instances). I would have been willing to pay for a Reddit API key if that meant being able to keep Sync. But they don’t offer it. And once I am able to migrate my profile to a different instance, I plan on donating to that instance if they take donations.

I’ve done the same with any service that has given me value, including Wikipedia. Again, this is based on fair trade and value.

You are entitled to make any assumptions you want about my choice. I’m glad you have your criteria for choosing the platforms and apps you like, and I celebrate that.

Unfortunately, you don’t really know my reasoning for my choice of platform and app, so telling me to go to Reddit based on your mis-assumptions about why I like Lemmy and Sync really highlights the core issue here.

Anyway, good luck to you bud. I hope you have a great Friday.

Why do you assume that content is the reason I chose a platform? Why do you gatekeep and dictate people’s choices?

And also from the Sync discord:

No, defending FOSS is not what reeks, it’s how people zealously go about defending it that does.

But you’re right, no need to discuss further.

How does PPP relate in this scenario? The price of the goods (in this case Sync) is the same wherever in the world it is available and whatever currency it is offered in, no?

Took me a minute to process, but that is a powerful one. I’m going to borrow that. Thanks for sharing lol

As much as those atrocious combinations give me the shivers, especially docker on Windows, we really should be advocating for the freedom of choice (even if that choice might be the wrong one). People should be free to do what they want, and such freedom should be celebrated.

• nothing wrong with that

• nothing wrong with that

• the data collection modules have not been initialized in the Sync code

But continue evangelizing.

This type of comment and attitude is what reeks in FOSS. Really unfortunate.

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

Off topic, but I just have to ask… is your name a reference to the IBM database technology? Lol

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.

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.

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.