Mastodon: @canpolat@hachyderm.io

  • 99 Posts
  • 122 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle

























  • Apart from the historical value, the most important part of this article now is the “Note of reflection” added 10 years after it’s inception:

    If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.

    I don’t think this work flow is relevant any more even for teams that don’t do CD, to be honest. It was a messy work flow to begin with and I haven’t seen it applied successfully in practice.



  • That’s the main reason I don’t use any apps. I don’t think there is a real need to suspect the official UI. If one doesn’t trust the instance admins, then they should rather migrate.

    In case of an application running on a server, there is no reliable way to make sure that the source being shared is the source that is deployed. As I said, I don’t think you have any ulterior motives. I’m only trying to raise awareness around a specific problem with Lemmy. Perhaps I should create a separate post about this in relevant communities, if it hasn’t been done already.


  • I agree that this is a feature Lemmy lacks and would be great to have in the core. And thank you for taking the time to create it. However, asking for username and password is a security problem. I’m not attributing any ill intent to your work, but something like this can very well be used to harvest account credentials. So I would advise people to not use solutions like this.

    Unfortunately Lemmy doesn’t provide a better way to implement this kind of add-ons. Hopefully one day it will have a better Auth system. Until then, I think I will stick to the official UI and hope that this will come to core :)