# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 196325
# self = https://watcher.sour.is?offset=142725
# next = https://watcher.sour.is?offset=142825
# prev = https://watcher.sour.is?offset=142625
@abucci Many (most?) licenses in the world of free software explicitly deny any liability (is that how you say it in English? I think you know what I mean). So, if a user still uses that software for “potentially dangerous” things, who’s to blame? The software? Or the user?
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?)
@abucci Many (most?) licenses in the world of free software explicitly deny any liability (is that how you say it in English? I think you know what I mean). So, if a user still uses that software for “potentially dangerous” things, who’s to blame? The software? Or the user?
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?)
@abucci Many (most?) licenses in the world of free software explicitly deny any liability (is that how you say it in English? I think you know what I mean). So, if a user still uses that software for “potentially dangerous” things, who’s to blame? The software? Or the user?
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?)
@marado @prologic personally I think there are good arguments in favor of accountability standards for some open source projects. Not all, obviously. But it is insane to act as though open source contributors bear exactly 0 responsibility in cases where they know full well that they are contributing code to potentially dangerous projects, and/or know they will profit from those contributions. We don't do that in any other sphere of life and shouldn't be doing it with software either. People die from this shit, or lose their life savings.
Also, open source provides an avenue for companies to launder their own responsibilities. That loophole should be closed.
Anyway, it's not an open and shut caae of "absolutely no liability for open source developers ever." Frankly, software quality would improve tenfold virtually overnight if developers knew they could be sied for doing lousy work. That's not a "chilling effect", it's responsible regulation of potentially dangerous products.
@marado @prologic personally I think there are good arguments in favor of accountability standards for some open source projects. Not all, obviously. But it is insane to act as though open source contributors bear exactly 0 responsibility in cases where they know full well that they are contributing code to potentially dangerous projects, and/or know they will profit from those contributions. We don't do that in any other sphere of life and shouldn't be doing it with software either. People die from this shit, or lose their life savings.
Also, open source provides an avenue for companies to launder their own responsibilities. That loophole should be closed.
Anyway, it's not an open and shut caae of "absolutely no liability for open source developers ever." Frankly, software quality would improve tenfold virtually overnight if developers knew they could be sued for doing lousy work. That's not a "chilling effect", it's responsible regulation of potentially dangerous products.
Own your words. Don’t pour your limited keystrokes into a walled garden you don’t control or own. Twitter is not your blog.
Own your words. Don’t pour your limited keystrokes into a walled garden you don’t control or own. Twitter is not your blog.
If anyone of you pulls the code and compiles it - then please let me know :)
@prologic I think these proposals come from lawmakers that ignore the existence or the importance of the Open Source ecosystem; and indeed this moving forward as is would be tragic for *all* free software development. eg., out of my free time I've contributed a few patches to several twtxt/yarn related projects. I do not want to by liable for them, however.
Three hours of pool practice today. 👌 🎱
Three hours of pool practice today. 👌 🎱
Three hours of pool practice today. 👌 🎱
@prologic I will give it a shot today, that and to show attached images in the status would be great to have. I just need to figure out the curl for posting image, then the rest would be easy to implement :) I would use that a lot since I often post photos and such.
@stigatle Haven't you got media uploads working yet? 🤔
@stigatle Haven't you got media uploads working yet? 🤔
@stigatle Haven't you got media uploads working yet? 🤔
@prologic hehe, yeah! That's the way to get things done - use it daily, fix everything that needs to be fixed :)
@stigatle Nice! 👌 Especially on the dog fooding l 🤗
@stigatle Nice! 👌 Especially on the dog fooding l 🤗
@stigatle Nice! 👌 Especially on the dog fooding l 🤗
[47°09′59″S, 126°43′46″W] Reading: 1.22 Sv
@prologic By the way - can I call my application 'Yarn desktop client'? Is that OK with you? Or do you want it to have another name - but then have 'a desktop client for yarn' as information in readme etc?
I will release the sourcecode for the desktop client tonight. I will put it on github (sorry to anyone who prefer other places), but the reason is that I do not want my own git to be open for public. So I'll put it on github where I have all my other public projects. I have to write the readme, then add some info on the login page (link to source etc), then it's ready to release with the current features. I then hope others will give it a try and use it if they want :) I also have many other features I need to implement, but all the main features that makes it usable has been implemented, so I'm very pleased with it (And I use it all the time now).
“neniel” could also be a biblical angel
“neniel” could also be a biblical angel
“neniel” could also be a biblical angel
“neniel” could also be a biblical angel
“neniel” could also be a biblical angel
“neniel” could also be a biblical angel
@prologic That sounds great! I'm looking forward to doing that too here! We also go to the local lakes and such when it gets warm enough! Always nice to spend time in the water :)
@stigatle It's early evening over here and we went the day at a water park which was nice 👌
@stigatle It's early evening over here and we went the day at a water park which was nice 👌
@stigatle It's early evening over here and we went the day at a water park which was nice 👌
Good morning to you all! Started my day by walking about 5km around a lake that's next to the ocean, a really nice place to walk. It rains today, so not many people out (which I like). So now the dog is sleeping on the sofa. My daughter went to a friend for a visit today, and my son is just chilling and watching youtube. So it's a nice chill start to this Saturday :) Hope you all have a great day!
[47°09′33″S, 126°43′25″W] Bad satellite signal -- switching to analog communication
[47°09′44″S, 126°43′30″W] Transponder malfunction
I rally find this rhetoric quite counter productive 😢 
I rally find this rhetoric quite counter productive 😢
I rally find this rhetoric quite counter productive 😢
🧮 USERS:1 FEEDS:2 TWTS:570 ARCHIVED:63537 CACHE:2200 FOLLOWERS:13 FOLLOWING:14
just loving this little guy: (·,·). it's like he's looking through a crack: ‘come on, you'll understand the function definition’
just loving this little guy: (·,·). it's like he's looking through a crack: ‘come on, you'll understand the function definition’
just loving this little guy: (·,·). it's like he's looking through a crack: ‘come on, you'll understand the function definition’
just loving this little guy: (·,·). it's like he's looking through a crack: ‘come on, you'll understand the function definition’
just loving this little guy: (·,·). it's like he's looking through a crack: ‘come on, you'll understand the function definition’
just loving this little guy: (·,·). it's like he's looking through a crack: ‘come on, you'll understand the function definition’
Finally, like the Eclipse suggests, if the new proposed EU laws would go ahead, I too as an open source developer would also have to either a) Put up a notice stating that none of my software, libraires, tools can be used within the EU or b) Simply go closed source. -- This would be extremely sad 😢 and honestly at that point I would question even continuing to be a software developer at all.
Finally, like the Eclipse suggests, if the new proposed EU laws would go ahead, I too as an open source developer would also have to either a) Put up a notice stating that none of my software, libraires, tools can be used within the EU or b) Simply go closed source. -- This would be extremely sad 😢 and honestly at that point I would question even continuing to be a software developer at all.
Finally, like the Eclipse suggests, if the new proposed EU laws would go ahead, I too as an open source developer would also have to either a) Put up a notice stating that none of my software, libraires, tools can be used within the EU or b) Simply go closed source. -- This would be extremely sad 😢 and honestly at that point I would question even continuing to be a software developer at all.
The problem and difference though is that open source is produced, published and free at no cost to the consumer. I also find the situation a bit weird from a legal standpoint as I don't understand how the CRA and CLA can possibly override open source licenses that are also legal documents and a contract between the open source author(s) and consumers of that open source software/library/whatever.
The problem and difference though is that open source is produced, published and free at no cost to the consumer. I also find the situation a bit weird from a legal standpoint as I don't understand how the CRA and CLA can possibly override open source licenses that are also legal documents and a contract between the open source author(s) and consumers of that open source software/library/whatever.
The problem and difference though is that open source is produced, published and free at no cost to the consumer. I also find the situation a bit weird from a legal standpoint as I don't understand how the CRA and CLA can possibly override open source licenses that are also legal documents and a contract between the open source author(s) and consumers of that open source software/library/whatever.
@marado I see. Thanks, read that article and it makes the problem a bit clear, especially on the liability issue. So, it seems EU lawmakers are trying to fix an economical problem by introducing a new set of laws that regulate a large part of the software industry (open source) that has effectively zero revenue?! This seems to be a bit counter intuitive to me, how are open source developers able to deal with liability for something they produce and publish for free?
What seems to be at play here is the capability of open source that has enabled great software reuse by large commercial ventures is under threat by lawmakers that don't seem to fully grasp the landscape of open source.
The liability of software and products should be with the builders of that product. This is a bit of a tricky situation, because if you're building a skyscraper a it falls down because of faulty concrete pylon footings, who's at fault, who is liable? You or the company that poured the pylons?
@marado I see. Thanks, read that article and it makes the problem a bit clear, especially on the liability issue. So, it seems EU lawmakers are trying to fix an economical problem by introducing a new set of laws that regulate a large part of the software industry (open source) that has effectively zero revenue?! This seems to be a bit counter intuitive to me, how are open source developers able to deal with liability for something they produce and publish for free?
What seems to be at play here is the capability of open source that has enabled great software reuse by large commercial ventures is under threat by lawmakers that don't seem to fully grasp the landscape of open source.
The liability of software and products should be with the builders of that product. This is a bit of a tricky situation, because if you're building a skyscraper a it falls down because of faulty concrete pylon footings, who's at fault, who is liable? You or the company that poured the pylons?
@marado I see. Thanks, read that article and it makes the problem a bit clear, especially on the liability issue. So, it seems EU lawmakers are trying to fix an economical problem by introducing a new set of laws that regulate a large part of the software industry (open source) that has effectively zero revenue?! This seems to be a bit counter intuitive to me, how are open source developers able to deal with liability for something they produce and publish for free?
What seems to be at play here is the capability of open source that has enabled great software reuse by large commercial ventures is under threat by lawmakers that don't seem to fully grasp the landscape of open source.
The liability of software and products should be with the builders of that product. This is a bit of a tricky situation, because if you're building a skyscraper a it falls down because of faulty concrete pylon footings, who's at fault, who is liable? You or the company that poured the pylons?
Heading out to a water park today 😆 Last chance for the girls to have some fun before school starts back up next week 😉
Heading out to a water park today 😆 Last chance for the girls to have some fun before school starts back up next week 😉
Heading out to a water park today 😆 Last chance for the girls to have some fun before school starts back up next week 😉
@rlafuente tás a enviar mixed signals, que é muita bom foi o que eu ouvi na net!
Got up before 7 this morning, now it's 14,5 hours later - and I finally got to sit down for the first time today. Been a busy day, but a good one. Now it's time to relax a bit (code on the desktop client) and then relax for a bit. Tomorrow the weather is going to suck, but I'll still go for the usual weekend hikes with the dog, trying to plan a new place to walk tomorrow.
[47°09′07″S, 126°43′16″W] Saalmi, retransmit, please
[47°09′52″S, 126°43′38″W] --white noise--
What is the Bayesian version of calibration?
What is the Bayesian version of calibration?
What is the Bayesian version of calibration?
What is the Bayesian version of calibration?
What is the Bayesian version of calibration?
What is the Bayesian version of calibration?
@logout well done on 1337 days of gopher server uptime
@logout well done on 1337 days of gopher server uptime
in practice probably ~all systems with qualia are valenced systems, since valence is the primary axis along which qualia can vary~
in practice probably ~all systems with qualia are valenced systems, since valence is the primary axis along which qualia can vary~
in practice probably ~all systems with qualia are valenced systems, since valence is the primary axis along which qualia can vary~
in practice probably ~all systems with qualia are valenced systems, since valence is the primary axis along which qualia can vary~
in practice probably ~all systems with qualia are valenced systems, since valence is the primary axis along which qualia can vary~
in practice probably ~all systems with qualia are valenced systems, since valence is the primary axis along which qualia can vary~
What is the information bottleneck of epigenetics?
What is the information bottleneck of epigenetics?
What is the information bottleneck of epigenetics?
What is the information bottleneck of epigenetics?
What is the information bottleneck of epigenetics?
What is the information bottleneck of epigenetics?
[47°09′01″S, 126°43′00″W] Dosimeter fixed
