Mark Change Detection app as unstable?
-
@james thanks for your answer.
Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:
https://changedetection.io/CHANGELOG.txt
Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.
Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.
That issues affected existing features, not new ones.
As you can see, there is a lot of active development.
Is very positive side, of course, as it means app is being actively maintained, but such frequent changes ca affect stability and break existing functionality.
Here updates activity:
https://git.cloudron.io/packages/changedetection-app/activity
In my opinion, level and frequency of updates makes app a bit unstable at the moment.
@dgtlmoon I wrote here about:
said in Mark Change Detection app as unstable?:
Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:
https://changedetection.io/CHANGELOG.txt
Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.
Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.
These problems affected instance from updates 0.50.28–0.50.38.
In the past, I've had similar issues with RSS generation, which is equally crucial for notifications.
Obviously, I don't want to dwell on the specific technical issues in this discussion, which are recommended - which, as noted, should be reported on your GitHub - but I did suggest marking the application as "unstable" due to these uncertainties in the releases which could disrupt the application's proper and normal functioning.
Everyone on this forum supports open source software and, eventually, recognizes its value by paying for licenses if with value. However, this doesn't mean we should necessarily settle.
I've been using Cloudron on various instances for over 5 years, with various paid licenses, and I've never never never had one problems with the stability of Cloudron or other apps. Also, amazing support, amazing forum, and a place where we try to help each other.
Therefore, I believe it's right to post observations when something isn't giving some troubles, always with the goal of improving and addressing each issue.
The request to delete the post also seems inappropriate: it's a form of censorship. On the contrary, it's important to explore these issues s community can make a more informed decision about whether and which solutions to use.
Obviously I disagree with the other forms of offense towards ChangeDetection.io and I thank you for the development work you are doing, as I immediately recognized in my first response post (where I wrote: As you can see, there is a lot of active development. Is very positive side, of course)
Thanks again for your efforts.
-
@dgtlmoon I wrote here about:
said in Mark Change Detection app as unstable?:
Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:
https://changedetection.io/CHANGELOG.txt
Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.
Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.
These problems affected instance from updates 0.50.28–0.50.38.
In the past, I've had similar issues with RSS generation, which is equally crucial for notifications.
Obviously, I don't want to dwell on the specific technical issues in this discussion, which are recommended - which, as noted, should be reported on your GitHub - but I did suggest marking the application as "unstable" due to these uncertainties in the releases which could disrupt the application's proper and normal functioning.
Everyone on this forum supports open source software and, eventually, recognizes its value by paying for licenses if with value. However, this doesn't mean we should necessarily settle.
I've been using Cloudron on various instances for over 5 years, with various paid licenses, and I've never never never had one problems with the stability of Cloudron or other apps. Also, amazing support, amazing forum, and a place where we try to help each other.
Therefore, I believe it's right to post observations when something isn't giving some troubles, always with the goal of improving and addressing each issue.
The request to delete the post also seems inappropriate: it's a form of censorship. On the contrary, it's important to explore these issues s community can make a more informed decision about whether and which solutions to use.
Obviously I disagree with the other forms of offense towards ChangeDetection.io and I thank you for the development work you are doing, as I immediately recognized in my first response post (where I wrote: As you can see, there is a lot of active development. Is very positive side, of course)
Thanks again for your efforts.
@p44 On the topic of issues in changedetection.io, I want to illustrate to you how insanely difficult it is to even get accurate issue/bug reporting from the general public, something that should take an hour to fix often takes over a week because people
- Dont follow the issue template
- Give misleading, wrong, often completely made up information
- Say they followed the instructions when they didnt
- Miss out critical things from the issue report - like the exact (except for password/host etc) info from the notification URLs
And then I come here and people calling it "A piece of shit", and yet, people cant even fill in a issue report with complete information
infuriating
-
@dgtlmoon yes, I can understand how frustrating is.
Inaccurate reporting is a big waste of time, specially from developers side, and specially when those rules are written and are ignored by most...
Thanks for sharing your concerns, also will help this forum to have better reports and to be better place.
About negative feedback on this thread, please don’t care, I’m sorry if you got a different image about this place.
-
@p44 I'm trying to track down this issue https://github.com/dgtlmoon/changedetection.io/issues/3591 is it possible that cloudron has deployed old code or incomplete code? I wonder if theres a way for publishers (me) to know if the code you're running on Cloudron is accurate to my release and not making the publisher look bad?
-
Late to this thread.
@svtx please don't use such wording. as you can tell, it's offensive and not constructive. technical discussions simply get derailed like this thread. you have used such language in other threads in the past too which I have ignored (like SUX and calling cloudron backups defunct).
@dgtlmoon I have removed the offensive wording . If the user continues, we will react accordingly.
FWIW, we use changedetection to track changes on the minecraft pages. It works quite reliably for us. Thanks for your great work!
-
Hello @svtx
@svtx said in Mark Change Detection app as unstable?:
As an adult, you should be able to deal with "strong" language (which I have honestly not even started using).
This remark does not improve this topic to a productive one in any way shape or form.
It is not your place to expect someone to handle something in a certain way.
Everyone human is different and should be considered as such.
We take great pride in our forum being an open and productive space.
Please keep this in mind for the future.
Take a days timeout to think about this. -
G girish locked this topic
Will lock it.