How would we like this auto-update to happen? In yarnd itself as a backend (optional)( feature? Out-of-band with a periodic tool that runs to check for new releases and manipulates the system?
How would we like this auto-update to happen? In `yarnd` itself as a backend (optional)( feature? Out-of-band with a periodic tool that runs to check for new releases and manipulates the system?
How would we like this auto-update to happen? In yarnd itself as a backend (optional)( feature? Out-of-band with a periodic tool that runs to check for new releases and manipulates the system?
Would we want the option to have instances auto-update? A banner could display alerting the poderator that an update is available.
> How would we like this auto-update to happen? In `yarnd` itself as a backend (optional)( feature? Out-of-band with a periodic tool that runs to check for new releases and manipulates the system?
Would we want the option to have instances auto-update? A banner could display alerting the poderator that an update is available.
How would we like this auto-update to happen? In yarnd itself as a backend (optional)( feature? Out-of-band with a periodic tool that runs to check for new releases and manipulates the system?
Would we want the option to have instances auto-update? A banner could display alerting the poderator that an update is available.
I think a banner along the top if a reasonable first step. And we can use the work you've already done there. It would also be related to yarnsocial/yarn#939
> > How would we like this auto-update to happen? In `yarnd` itself as a backend (optional)( feature? Out-of-band with a periodic tool that runs to check for new releases and manipulates the system?
>
> Would we want the option to have instances auto-update? A banner could display alerting the poderator that an update is available.
I _think_ a banner along the top if a reasonable first step. And we can use the work you've already done there. It would also be related to https://git.mills.io/yarnsocial/yarn/issues/939
Not sure if I was meant to be mentioned here. ;-) Haven't followed the yarnd development for quite some time.
I don't like automatic updates. It's the worst. Always happens at the most inconvient time ever. And then breaks stuff. But the really terrible thing is, you're not controlling it anymore yourself. Operating systems that do what they want is very hard and basically an unpredictable endeavor. It clearly goes against my train of thought. Sure, getting out security bug fixes is a nice thing, but it also opens up the doors for all sorts of malicious takeover attacks with such a code path. I don't trust software that does that.
It should be easy enough to implement a (periodic) automatic update yourself, if you truely want to live dangerously on the edge.
If you're still doing it, make it at least opt-in.
I'm sure you will find tons of much more solid argumentation out there why auto-update is something to avoid like the plague.
Not sure if I was meant to be mentioned here. ;-) Haven't followed the yarnd development for quite some time.
I don't like automatic updates. It's the worst. Always happens at the most inconvient time ever. And then breaks stuff. But the really terrible thing is, you're not controlling it anymore yourself. Operating systems that do what they want is very hard and basically an unpredictable endeavor. It clearly goes against my train of thought. Sure, getting out security bug fixes is a nice thing, but it also opens up the doors for all sorts of malicious takeover attacks with such a code path. I don't trust software that does that.
It should be easy enough to implement a (periodic) automatic update yourself, if you truely want to live dangerously on the edge.
If you're still doing it, make it at least opt-in.
I'm sure you will find tons of much more solid argumentation out there why auto-update is something to avoid like the plague.
Not sure if I was meant to be mentioned here. ;-) Haven't followed the yarnd development for quite some time.
You were, becuase I value your opinion 😅
I don't like automatic updates. It's the worst. Always happens at the most inconvient time ever. And then breaks stuff. But the really terrible thing is, you're not controlling it anymore yourself. Operating systems that do what they want is very hard and basically an unpredictable endeavor. It clearly goes against my train of thought. Sure, getting out security bug fixes is a nice thing, but it also opens up the doors for all sorts of malicious takeover attacks with such a code path. I don't trust software that does that.
What if we just did a notification?
It should be easy enough to implement a (periodic) automatic update yourself, if you truely want to live dangerously on the edge.
If you're still doing it, make it at least opt-in.
Absooutely.
I'm sure you will find tons of much more solid argumentation out there why auto-update is something to avoid like the plague.
I actually happen to agree with your stance btw, but I also recognize the pain users have to go through to get updates. So it's about stirking that balance.
> Not sure if I was meant to be mentioned here. ;-) Haven't followed the yarnd development for quite some time.
You were, becuase I value your opinion 😅
> I don't like automatic updates. It's the worst. Always happens at the most inconvient time ever. And then breaks stuff. But the really terrible thing is, you're not controlling it anymore yourself. Operating systems that do what they want is very hard and basically an unpredictable endeavor. It clearly goes against my train of thought. Sure, getting out security bug fixes is a nice thing, but it also opens up the doors for all sorts of malicious takeover attacks with such a code path. I don't trust software that does that.
What if we just did a notification?
> It should be easy enough to implement a (periodic) automatic update yourself, if you truely want to live dangerously on the edge.
>
> If you're still doing it, make it at least opt-in.
Absooutely.
> I'm sure you will find tons of much more solid argumentation out there why auto-update is something to avoid like the plague.
I actually happen to agree with your stance btw, but I also recognize the pain users have to go through to get updates. So it's about stirking that balance.
If it is a pull and not push mechanism, that can be deactivated, it might be okay. It's a balancing act to claim to be the better social media software without tracking and all the other bad things, but then still phoning back home.
I also recognize the pain users have to go through to get updates.
So what's the hard part here on the updates? Once that's known, the key problem – the process itself to do the update – can be tackled, improved and simplified. I could very well be completely wrong, auto-update seems more like a dirty bandaid on an infected wound. Doesn't get to the core.
> You were, becuase I value your opinion 😅
Thanks, mate! :-)
> What if we just did a notification?
If it is a pull and not push mechanism, that can be deactivated, it *might* be okay. It's a balancing act to claim to be the better social media software without tracking and all the other bad things, but then still phoning back home.
> I also recognize the pain users have to go through to get updates.
So what's the hard part here on the updates? Once that's known, the key problem – the process itself to do the update – can be tackled, improved and simplified. I could very well be completely wrong, auto-update seems more like a dirty bandaid on an infected wound. Doesn't get to the core.
So what's the hard part here on the updates? Once that's known, the key problem – the process itself to do the update – can be tackled, improved and simplified. I could very well be completely wrong, auto-update seems more like a dirty bandaid on an infected wound. Doesn't get to the core.
I'm not quite sure I follow this train of thought? 🤔
> So what's the hard part here on the updates? Once that's known, the key problem – the process itself to do the update – can be tackled, improved and simplified. I could very well be completely wrong, auto-update seems more like a dirty bandaid on an infected wound. Doesn't get to the core.
I'm not quite sure I follow this train of thought? 🤔
How would we like this auto-update to happen? In
yarnditself as a backend (optional)( feature? Out-of-band with a periodic tool that runs to check for new releases and manipulates the system?cc @lyse who has opinions on this.
Would we want the option to have instances auto-update? A banner could display alerting the poderator that an update is available.
I think a banner along the top if a reasonable first step. And we can use the work you've already done there. It would also be related to yarnsocial/yarn#939
Not sure if I was meant to be mentioned here. ;-) Haven't followed the yarnd development for quite some time.
I don't like automatic updates. It's the worst. Always happens at the most inconvient time ever. And then breaks stuff. But the really terrible thing is, you're not controlling it anymore yourself. Operating systems that do what they want is very hard and basically an unpredictable endeavor. It clearly goes against my train of thought. Sure, getting out security bug fixes is a nice thing, but it also opens up the doors for all sorts of malicious takeover attacks with such a code path. I don't trust software that does that.
It should be easy enough to implement a (periodic) automatic update yourself, if you truely want to live dangerously on the edge.
If you're still doing it, make it at least opt-in.
I'm sure you will find tons of much more solid argumentation out there why auto-update is something to avoid like the plague.
You were, becuase I value your opinion 😅
What if we just did a notification?
Absooutely.
I actually happen to agree with your stance btw, but I also recognize the pain users have to go through to get updates. So it's about stirking that balance.
Thanks, mate! :-)
If it is a pull and not push mechanism, that can be deactivated, it might be okay. It's a balancing act to claim to be the better social media software without tracking and all the other bad things, but then still phoning back home.
So what's the hard part here on the updates? Once that's known, the key problem – the process itself to do the update – can be tackled, improved and simplified. I could very well be completely wrong, auto-update seems more like a dirty bandaid on an infected wound. Doesn't get to the core.
I'm not quite sure I follow this train of thought? 🤔