https://www.youtube.com/watch?v=uRuN2nqbJD4
It’s tiny, but it looks like it plays okay. 🤔
https://www.youtube.com/watch?v=uRuN2nqbJD4
It’s tiny, but it looks like it plays okay. 🤔
https://www.youtube.com/watch?v=uRuN2nqbJD4
It’s tiny, but it looks like it plays okay. 🤔
zbarcam-qt is much better than the gstreamer pipeline that I’ve been using before.
zbarcam-qt is much better than the gstreamer pipeline that I’ve been using before.
zbarcam-qt is much better than the gstreamer pipeline that I’ve been using before.
There were people playing on a soccer field nearby, I guess they got pretty soaked.
There were people playing on a soccer field nearby, I guess they got pretty soaked.
There were people playing on a soccer field nearby, I guess they got pretty soaked.
But hey, at least that Traefik update today went smoothly. So there’s that.
But hey, at least that Traefik update today went smoothly. So there’s that.
But hey, at least that Traefik update today went smoothly. So there’s that.
Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I *believe* it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I *think* I understand very well that the original twtxt crowd is disgruntled.)
That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.
Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I *believe* it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I *think* I understand very well that the original twtxt crowd is disgruntled.)
That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.
Put another way: Yarn.social is not twtxt. The content that we all have in our feeds really is much closer to a web forum or usenet or whatever. It’s threaded conversations. twtxt, as I *believe* it was originally intended, are short little status updates – that’s it. The formats of Yarn.social and twtxt might be very similar, but the content is vastly different and, in a way, incompatible. (As such, I *think* I understand very well that the original twtxt crowd is disgruntled.)
That proposed truncated feed doesn’t really provide any value, if you ask me. 🤔 It’d just be chaotic.
Seatbelts and cars are so much simpler than software. It is easy to see that you might crash your car into a tree and that a belt will help you here (if you’re going slow enough, yadda yadda).
If I write a library for a compression algorithm, how can I ever prepare for someone using this in, I don’t know, a medical device in a hospital, but then my code has a bug, crashes that device and a person dies? There are so many more indirections here than with cars and seatbelts. It is completely out of my control.
Anyway, I think we both made our points clear. I’m out, cheers! 👋 🥃
Seatbelts and cars are so much simpler than software. It is easy to see that you might crash your car into a tree and that a belt will help you here (if you’re going slow enough, yadda yadda).
If I write a library for a compression algorithm, how can I ever prepare for someone using this in, I don’t know, a medical device in a hospital, but then my code has a bug, crashes that device and a person dies? There are so many more indirections here than with cars and seatbelts. It is completely out of my control.
Anyway, I think we both made our points clear. I’m out, cheers! 👋 🥃
Seatbelts and cars are so much simpler than software. It is easy to see that you might crash your car into a tree and that a belt will help you here (if you’re going slow enough, yadda yadda).
If I write a library for a compression algorithm, how can I ever prepare for someone using this in, I don’t know, a medical device in a hospital, but then my code has a bug, crashes that device and a person dies? There are so many more indirections here than with cars and seatbelts. It is completely out of my control.
Anyway, I think we both made our points clear. I’m out, cheers! 👋 🥃
Yeah, we probably have to agree to disagree here.
I still think it would be better to put the burden of liability on the users – no matter if they’re private individuals or big companies. (And isn’t that already the case? Do we even have to solve a *legal liability problem*? Not talking about software quality here, that’s a whole other issue.)
> Trust me, if people got sued or went to jail, the tech industry would figure out really fast how to make these determinations.
Yeah, they would. It’s simple: No more free software, no more publicly available projects. The only software that would ever exist is software made by large corporations who can afford the appropriate insurances and lawyers.
What you’re proposing is either classifying software in advance as “dangerous” or “harmless” (I’d argue that’s impossible – as an extreme, think of libraries, they’d *all* be “potentially dangerous”), or threatening free software projects with lawsuits if, at some point in the future, these projects caused an accident.
Why would anyone publish free software or contribute to it under these conditions?
> Why should open source software development be any different?
IMHO because you can make software publicly available and anyone can use it for whatever they want, which the author has zero control over.
Anyway, have a good night, I’m gonna enjoy a couple of movies now. 👋 😊
Yeah, we probably have to agree to disagree here.
I still think it would be better to put the burden of liability on the users – no matter if they’re private individuals or big companies. (And isn’t that already the case? Do we even have to solve a *legal liability problem*? Not talking about software quality here, that’s a whole other issue.)
> Trust me, if people got sued or went to jail, the tech industry would figure out really fast how to make these determinations.
Yeah, they would. It’s simple: No more free software, no more publicly available projects. The only software that would ever exist is software made by large corporations who can afford the appropriate insurances and lawyers.
What you’re proposing is either classifying software in advance as “dangerous” or “harmless” (I’d argue that’s impossible – as an extreme, think of libraries, they’d *all* be “potentially dangerous”), or threatening free software projects with lawsuits if, at some point in the future, these projects caused an accident.
Why would anyone publish free software or contribute to it under these conditions?
> Why should open source software development be any different?
IMHO because you can make software publicly available and anyone can use it for whatever they want, which the author has zero control over.
Anyway, have a good night, I’m gonna enjoy a couple of movies now. 👋 😊
Yeah, we probably have to agree to disagree here.
I still think it would be better to put the burden of liability on the users – no matter if they’re private individuals or big companies. (And isn’t that already the case? Do we even have to solve a *legal liability problem*? Not talking about software quality here, that’s a whole other issue.)
> Trust me, if people got sued or went to jail, the tech industry would figure out really fast how to make these determinations.
Yeah, they would. It’s simple: No more free software, no more publicly available projects. The only software that would ever exist is software made by large corporations who can afford the appropriate insurances and lawyers.
What you’re proposing is either classifying software in advance as “dangerous” or “harmless” (I’d argue that’s impossible – as an extreme, think of libraries, they’d *all* be “potentially dangerous”), or threatening free software projects with lawsuits if, at some point in the future, these projects caused an accident.
Why would anyone publish free software or contribute to it under these conditions?
> Why should open source software development be any different?
IMHO because you can make software publicly available and anyone can use it for whatever they want, which the author has zero control over.
Anyway, have a good night, I’m gonna enjoy a couple of movies now. 👋 😊
> Firstly, contributing software to an open source project cannot be a blanket "get out of jail free" card. That's a sociopathic stance, on its face, and just cannot be accepted.
I don’t understand. Why is that sociopathic? (Language barrier here? I really don’t get what you mean.)
> But thirdly, […] And the same should happen in software. […]
How do you *really know* if a project has been used in dangerous situations? (If this changes in the future, are programmers that contributed in the past – when this project was not yet used in dangerous situations – also liable?)
> Firstly, contributing software to an open source project cannot be a blanket "get out of jail free" card. That's a sociopathic stance, on its face, and just cannot be accepted.
I don’t understand. Why is that sociopathic? (Language barrier here? I really don’t get what you mean.)
> But thirdly, […] And the same should happen in software. […]
How do you *really know* if a project has been used in dangerous situations? (If this changes in the future, are programmers that contributed in the past – when this project was not yet used in dangerous situations – also liable?)
> Firstly, contributing software to an open source project cannot be a blanket "get out of jail free" card. That's a sociopathic stance, on its face, and just cannot be accepted.
I don’t understand. Why is that sociopathic? (Language barrier here? I really don’t get what you mean.)
> But thirdly, […] And the same should happen in software. […]
How do you *really know* if a project has been used in dangerous situations? (If this changes in the future, are programmers that contributed in the past – when this project was not yet used in dangerous situations – also liable?)
We Germans always have to make an analogy with cars 😅, so here you go: If there’s a guy on the street offering you a car and he says, “oh, maybe it’ll drive, maybe it’ll explode, who knows – either way, the risk is yours, I’m just offering it”, you might still be interested in using that car for certain things. But you wouldn’t use it as an ambulance car or a taxi or whatever. Or you might actually do that after carefully inspecting it and/or fixing some things.
So, if there actually are any liability issues here in the current laws – I know nothing about that field, especially not when it comes to *corporations* –, I think this should be fixed at the user’s end. You run a hospital? Then there are certain standards for you and you’re liable for certain things. If that implies that you can no longer use, say, nginx, then that’s not nginx’s problem, but yours.
I would argue that you *cannot* hold programmers liable if they contribute to a free software project that is publicly available, because you don’t know how this software is going to be used.
(Plus, I have a hard time imagining how you as a programmer could prove that you’ve done a good job. What’s the criterium here? Clearly, it can’t be “no bugs ever”. So, what is it, “no damage above 1000 dollars” or something like that? What does the EU thingy say here?)
We Germans always have to make an analogy with cars 😅, so here you go: If there’s a guy on the street offering you a car and he says, “oh, maybe it’ll drive, maybe it’ll explode, who knows – either way, the risk is yours, I’m just offering it”, you might still be interested in using that car for certain things. But you wouldn’t use it as an ambulance car or a taxi or whatever. Or you might actually do that after carefully inspecting it and/or fixing some things.
So, if there actually are any liability issues here in the current laws – I know nothing about that field, especially not when it comes to *corporations* –, I think this should be fixed at the user’s end. You run a hospital? Then there are certain standards for you and you’re liable for certain things. If that implies that you can no longer use, say, nginx, then that’s not nginx’s problem, but yours.
I would argue that you *cannot* hold programmers liable if they contribute to a free software project that is publicly available, because you don’t know how this software is going to be used.
(Plus, I have a hard time imagining how you as a programmer could prove that you’ve done a good job. What’s the criterium here? Clearly, it can’t be “no bugs ever”. So, what is it, “no damage above 1000 dollars” or something like that? What does the EU thingy say here?)
We Germans always have to make an analogy with cars 😅, so here you go: If there’s a guy on the street offering you a car and he says, “oh, maybe it’ll drive, maybe it’ll explode, who knows – either way, the risk is yours, I’m just offering it”, you might still be interested in using that car for certain things. But you wouldn’t use it as an ambulance car or a taxi or whatever. Or you might actually do that after carefully inspecting it and/or fixing some things.
So, if there actually are any liability issues here in the current laws – I know nothing about that field, especially not when it comes to *corporations* –, I think this should be fixed at the user’s end. You run a hospital? Then there are certain standards for you and you’re liable for certain things. If that implies that you can no longer use, say, nginx, then that’s not nginx’s problem, but yours.
I would argue that you *cannot* hold programmers liable if they contribute to a free software project that is publicly available, because you don’t know how this software is going to be used.
(Plus, I have a hard time imagining how you as a programmer could prove that you’ve done a good job. What’s the criterium here? Clearly, it can’t be “no bugs ever”. So, what is it, “no damage above 1000 dollars” or something like that? What does the EU thingy say here?)
http://www.macscouter.com/stories/ShaggyShorts.asp#The%20Lever
Interestingly, it looks like it goes back to the 1950ies: https://www.reddit.com/r/NateTheSnake/comments/qobeny/tracing_nates_history/
http://www.macscouter.com/stories/ShaggyShorts.asp#The%20Lever
Interestingly, it looks like it goes back to the 1950ies: https://www.reddit.com/r/NateTheSnake/comments/qobeny/tracing_nates_history/
http://www.macscouter.com/stories/ShaggyShorts.asp#The%20Lever
Interestingly, it looks like it goes back to the 1950ies: https://www.reddit.com/r/NateTheSnake/comments/qobeny/tracing_nates_history/
I previously used xiate, which is based on GTK and VTE – and that’s the problem. Sooner or later, it’ll have to be ported from GTK 3 to GTK 4 and that’s not looking too good at the moment. GTK 4 is too slow. I’m not yet convinced that I *have to* give up xiate, but I still want to see how well st works for me.
I previously used xiate, which is based on GTK and VTE – and that’s the problem. Sooner or later, it’ll have to be ported from GTK 3 to GTK 4 and that’s not looking too good at the moment. GTK 4 is too slow. I’m not yet convinced that I *have to* give up xiate, but I still want to see how well st works for me.
I previously used xiate, which is based on GTK and VTE – and that’s the problem. Sooner or later, it’ll have to be ported from GTK 3 to GTK 4 and that’s not looking too good at the moment. GTK 4 is too slow. I’m not yet convinced that I *have to* give up xiate, but I still want to see how well st works for me.