#disclaimer — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #disclaimer, aggregated by home.social.
-
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
(Ik ben overigens ook erg vóór de frase 'adopt, don't shop', en dat zal ik in een volgende levensfase (weer) doen. Voor nu maak ik een kat met Bagage niet blij met een vijfjarige. Dat empty nest-syndroom in de toekomst echter..! #disclaimer)
-
(Ik ben overigens ook erg vóór de frase 'adopt, don't shop', en dat zal ik in een volgende levensfase (weer) doen. Voor nu maak ik een kat met Bagage niet blij met een vijfjarige. Dat empty nest-syndroom in de toekomst echter..! #disclaimer)
-
(Ik ben overigens ook erg vóór de frase 'adopt, don't shop', en dat zal ik in een volgende levensfase (weer) doen. Voor nu maak ik een kat met Bagage niet blij met een vijfjarige. Dat empty nest-syndroom in de toekomst echter..! #disclaimer)
-
(Ik ben overigens ook erg vóór de frase 'adopt, don't shop', en dat zal ik in een volgende levensfase (weer) doen. Voor nu maak ik een kat met Bagage niet blij met een vijfjarige. Dat empty nest-syndroom in de toekomst echter..! #disclaimer)
-
Was this bizarre #disclaimer always in the #Waze release notes? I don’t remember seeing it before, and it sounds ominous.
Like, “if you’ve avoided updating so as not to install the Torment Nexus feature, please note this version definitely includes the Torment Nexus feature you didn’t want” ominous.
-
Was this bizarre #disclaimer always in the #Waze release notes? I don’t remember seeing it before, and it sounds ominous.
Like, “if you’ve avoided updating so as not to install the Torment Nexus feature, please note this version definitely includes the Torment Nexus feature you didn’t want” ominous.
-
Was this bizarre #disclaimer always in the #Waze release notes? I don’t remember seeing it before, and it sounds ominous.
Like, “if you’ve avoided updating so as not to install the Torment Nexus feature, please note this version definitely includes the Torment Nexus feature you didn’t want” ominous.
-
Was this bizarre #disclaimer always in the #Waze release notes? I don’t remember seeing it before, and it sounds ominous.
Like, “if you’ve avoided updating so as not to install the Torment Nexus feature, please note this version definitely includes the Torment Nexus feature you didn’t want” ominous.
-
Was this bizarre #disclaimer always in the #Waze release notes? I don’t remember seeing it before, and it sounds ominous.
Like, “if you’ve avoided updating so as not to install the Torment Nexus feature, please note this version definitely includes the Torment Nexus feature you didn’t want” ominous.
-
Movie TV Tech Geeks #TVFeatures #Disclaimer #AppleTV #CateBlanchett Apple TV's 7-Part Psychological Thriller Is a Forgotten but Brilliant Miniseries http://dlvr.it/TSVwW6
-
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
ADORO IL GENIO - STOP!
#Disclaimer:
1 - È un contenuto scorretto. Se non vi piacciono, evitate, continuate a scrollare.
2 - NESSUN animale è stato anche solo toccato nel realizzare questo contenuto.
3 - Come direbbe Gigi Proietti, #ncerompetercà#adoroilgenio #26aprile #comedy #humor #spot #commercial #commercials #SpotTV #ad #advert #advertising #video #comunicazione #pubblicità #pubblicita #acqua #acquaminerale #acquafrizzante #AI #acquanaturale #water
-
ADORO IL GENIO - STOP!
#Disclaimer:
1 - È un contenuto scorretto. Se non vi piacciono, evitate, continuate a scrollare.
2 - NESSUN animale è stato anche solo toccato nel realizzare questo contenuto.
3 - Come direbbe Gigi Proietti, #ncerompetercà#adoroilgenio #26aprile #comedy #humor #spot #commercial #commercials #SpotTV #ad #advert #advertising #video #comunicazione #pubblicità #pubblicita #acqua #acquaminerale #acquafrizzante #AI #acquanaturale #water
-
ADORO IL GENIO - STOP!
#Disclaimer:
1 - È un contenuto scorretto. Se non vi piacciono, evitate, continuate a scrollare.
2 - NESSUN animale è stato anche solo toccato nel realizzare questo contenuto.
3 - Come direbbe Gigi Proietti, #ncerompetercà#adoroilgenio #26aprile #comedy #humor #spot #commercial #commercials #SpotTV #ad #advert #advertising #video #comunicazione #pubblicità #pubblicita #acqua #acquaminerale #acquafrizzante #AI #acquanaturale #water
-
ADORO IL GENIO - STOP!
#Disclaimer:
1 - È un contenuto scorretto. Se non vi piacciono, evitate, continuate a scrollare.
2 - NESSUN animale è stato anche solo toccato nel realizzare questo contenuto.
3 - Come direbbe Gigi Proietti, #ncerompetercà#adoroilgenio #26aprile #comedy #humor #spot #commercial #commercials #SpotTV #ad #advert #advertising #video #comunicazione #pubblicità #pubblicita #acqua #acquaminerale #acquafrizzante #AI #acquanaturale #water
-
ADORO IL GENIO - STOP!
#Disclaimer:
1 - È un contenuto scorretto. Se non vi piacciono, evitate, continuate a scrollare.
2 - NESSUN animale è stato anche solo toccato nel realizzare questo contenuto.
3 - Come direbbe Gigi Proietti, #ncerompetercà#adoroilgenio #26aprile #comedy #humor #spot #commercial #commercials #SpotTV #ad #advert #advertising #video #comunicazione #pubblicità #pubblicita #acqua #acquaminerale #acquafrizzante #AI #acquanaturale #water
-
𝗖𝗗𝗔 𝘄𝗶𝗹 𝗱𝗶𝘀𝗰𝗹𝗮𝗶𝗺𝗲𝗿 𝘃𝗼𝗼𝗿 𝗶𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲𝗿𝘀: 𝗵𝗮𝘀𝗵𝘁𝗮𝗴 #𝗡𝗶𝗲𝘁𝗗𝗲𝘀𝗸𝘂𝗻𝗱𝗶𝗴
Je baby een lepel boter geven zodat die beter doorslaapt, vitaminepillen voor je huid of investeren in crypto omdat het een snelle weg naar rijkdom zou zijn. Het zijn adviezen die miljoenen keren worden bekeken op social media, maar enig bewijs bij die claims ontbreekt.
-
𝗖𝗗𝗔 𝘄𝗶𝗹 𝗱𝗶𝘀𝗰𝗹𝗮𝗶𝗺𝗲𝗿 𝘃𝗼𝗼𝗿 𝗶𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲𝗿𝘀: 𝗵𝗮𝘀𝗵𝘁𝗮𝗴 #𝗡𝗶𝗲𝘁𝗗𝗲𝘀𝗸𝘂𝗻𝗱𝗶𝗴
Je baby een lepel boter geven zodat die beter doorslaapt, vitaminepillen voor je huid of investeren in crypto omdat het een snelle weg naar rijkdom zou zijn. Het zijn adviezen die miljoenen keren worden bekeken op social media, maar enig bewijs bij die claims ontbreekt.
-
𝗖𝗗𝗔 𝘄𝗶𝗹 𝗱𝗶𝘀𝗰𝗹𝗮𝗶𝗺𝗲𝗿 𝘃𝗼𝗼𝗿 𝗶𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲𝗿𝘀: 𝗵𝗮𝘀𝗵𝘁𝗮𝗴 #𝗡𝗶𝗲𝘁𝗗𝗲𝘀𝗸𝘂𝗻𝗱𝗶𝗴
Je baby een lepel boter geven zodat die beter doorslaapt, vitaminepillen voor je huid of investeren in crypto omdat het een snelle weg naar rijkdom zou zijn. Het zijn adviezen die miljoenen keren worden bekeken op social media, maar enig bewijs bij die claims ontbreekt.
-
𝗖𝗗𝗔 𝘄𝗶𝗹 𝗱𝗶𝘀𝗰𝗹𝗮𝗶𝗺𝗲𝗿 𝘃𝗼𝗼𝗿 𝗶𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲𝗿𝘀: 𝗵𝗮𝘀𝗵𝘁𝗮𝗴 #𝗡𝗶𝗲𝘁𝗗𝗲𝘀𝗸𝘂𝗻𝗱𝗶𝗴
Je baby een lepel boter geven zodat die beter doorslaapt, vitaminepillen voor je huid of investeren in crypto omdat het een snelle weg naar rijkdom zou zijn. Het zijn adviezen die miljoenen keren worden bekeken op social media, maar enig bewijs bij die claims ontbreekt.
-
𝗖𝗗𝗔 𝘄𝗶𝗹 𝗱𝗶𝘀𝗰𝗹𝗮𝗶𝗺𝗲𝗿 𝘃𝗼𝗼𝗿 𝗶𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲𝗿𝘀: 𝗵𝗮𝘀𝗵𝘁𝗮𝗴 #𝗡𝗶𝗲𝘁𝗗𝗲𝘀𝗸𝘂𝗻𝗱𝗶𝗴
Je baby een lepel boter geven zodat die beter doorslaapt, vitaminepillen voor je huid of investeren in crypto omdat het een snelle weg naar rijkdom zou zijn. Het zijn adviezen die miljoenen keren worden bekeken op social media, maar enig bewijs bij die claims ontbreekt.
-
RE: https://hachyderm.io/@thomasfuchs/116377687987470957
When a company ends support for the last version of a given #software product compatible with any subset of the supported #hardware, or ends support for a given software product altogether, or ends support for a software-controlled hardware product, the warranty #disclaimer, limitation of #liability, indemnity, and related #EULA terms should be deemed without force or effect regarding any future harms resulting from software defects unless the company releases all information and legal permissions necessary for arbitrary independent parties to patch those defects and distribute and install those patches.
Either release the complete and corresponding source code (including any keys necessary to install or run a compiled version) with a license to make and distribute fixes, or fix your up stuff forever, or face unlimited liability for the consequences of your refusal to fix or allow fixing.
-
RE: https://hachyderm.io/@thomasfuchs/116377687987470957
When a company ends support for the last version of a given #software product compatible with any subset of the supported #hardware, or ends support for a given software product altogether, or ends support for a software-controlled hardware product, the warranty #disclaimer, limitation of #liability, indemnity, and related #EULA terms should be deemed without force or effect regarding any future harms resulting from software defects unless the company releases all information and legal permissions necessary for arbitrary independent parties to patch those defects and distribute and install those patches.
Either release the complete and corresponding source code (including any keys necessary to install or run a compiled version) with a license to make and distribute fixes, or fix your up stuff forever, or face unlimited liability for the consequences of your refusal to fix or allow fixing.
-
RE: https://hachyderm.io/@thomasfuchs/116377687987470957
When a company ends support for the last version of a given #software product compatible with any subset of the supported #hardware, or ends support for a given software product altogether, or ends support for a software-controlled hardware product, the warranty #disclaimer, limitation of #liability, indemnity, and related #EULA terms should be deemed without force or effect regarding any future harms resulting from software defects unless the company releases all information and legal permissions necessary for arbitrary independent parties to patch those defects and distribute and install those patches.
Either release the complete and corresponding source code (including any keys necessary to install or run a compiled version) with a license to make and distribute fixes, or fix your up stuff forever, or face unlimited liability for the consequences of your refusal to fix or allow fixing.
-
RE: https://hachyderm.io/@thomasfuchs/116377687987470957
When a company ends support for the last version of a given #software product compatible with any subset of the supported #hardware, or ends support for a given software product altogether, or ends support for a software-controlled hardware product, the warranty #disclaimer, limitation of #liability, indemnity, and related #EULA terms should be deemed without force or effect regarding any future harms resulting from software defects unless the company releases all information and legal permissions necessary for arbitrary independent parties to patch those defects and distribute and install those patches.
Either release the complete and corresponding source code (including any keys necessary to install or run a compiled version) with a license to make and distribute fixes, or fix your up stuff forever, or face unlimited liability for the consequences of your refusal to fix or allow fixing.
-
RE: https://hachyderm.io/@thomasfuchs/116377687987470957
When a company ends support for the last version of a given #software product compatible with any subset of the supported #hardware, or ends support for a given software product altogether, or ends support for a software-controlled hardware product, the warranty #disclaimer, limitation of #liability, indemnity, and related #EULA terms should be deemed without force or effect regarding any future harms resulting from software defects unless the company releases all information and legal permissions necessary for arbitrary independent parties to patch those defects and distribute and install those patches.
Either release the complete and corresponding source code (including any keys necessary to install or run a compiled version) with a license to make and distribute fixes, or fix your up stuff forever, or face unlimited liability for the consequences of your refusal to fix or allow fixing.
-
You stated: <<What it actually says is "AI is _permitted_ to make mistakes; _you are liable_ for the results, whether you check them or not". Except "you" is generally not even the person building, installing, or even using the AI. It's the person the AI is used on.>>
Way back in the early 2000s, there was a system called "Dragon Dictate". The goal was to eliminate #human #transcriptionists with automated speech-to-text (sound familiar?) The system had to be trained on your voice and vocabulary. Once properly trained it could do a pretty good job, I'll guess 95-98%. It was better suited to output that was stereotyped (mostly the same), and structured (such as radiology reports and operative notes).
Regardless of how the note/report was generated, the professional who spoke the words had a obligation to at least scan the output and sign it (yes, with an ink pen!). Once signed it became part of the "legal medical record" open to misinterpretation, copying, lawsuits, etc. etc.
Once Dragon Dictate became routine (and they fired all the transcriptionists) I started to notice this little #disclaimer at the bottom:
"If portions of this note are confusing or indecipherable please feel free to call me with questions or concerns." Sounds a lot like #AI to me! I polite way to summarize this is:
👉 They were trying to force me to be their copy-editor. 👈
It cast the entire content in doubt.
Consider for a moment the difference between saying "The scan does not show cancer." and "The scan does show cancer." That "not" is doing a lot of work, and is very easy to miss when you're talking fast and never intend to read your own note ever again.
More subtle is the grammatical error in the first sentence. "This note was #dictated using Dragon text to speech recognition software." Either they changed their product name to "Dragon Text", in which case the capitalization is off. Or they transposed words and it should read "speech to text" or "speech recognition" with no text.
👉 In other words, they didn't even proof-read their own disclaimer! 😱
#MedicalRecords #Medicine #SpeechToText #Liability #Risk #SignalToNoise -
You stated: <<What it actually says is "AI is _permitted_ to make mistakes; _you are liable_ for the results, whether you check them or not". Except "you" is generally not even the person building, installing, or even using the AI. It's the person the AI is used on.>>
Way back in the early 2000s, there was a system called "Dragon Dictate". The goal was to eliminate #human #transcriptionists with automated speech-to-text (sound familiar?) The system had to be trained on your voice and vocabulary. Once properly trained it could do a pretty good job, I'll guess 95-98%. It was better suited to output that was stereotyped (mostly the same), and structured (such as radiology reports and operative notes).
Regardless of how the note/report was generated, the professional who spoke the words had a obligation to at least scan the output and sign it (yes, with an ink pen!). Once signed it became part of the "legal medical record" open to misinterpretation, copying, lawsuits, etc. etc.
Once Dragon Dictate became routine (and they fired all the transcriptionists) I started to notice this little #disclaimer at the bottom:
"If portions of this note are confusing or indecipherable please feel free to call me with questions or concerns." Sounds a lot like #AI to me! I polite way to summarize this is:
👉 They were trying to force me to be their copy-editor. 👈
It cast the entire content in doubt.
Consider for a moment the difference between saying "The scan does not show cancer." and "The scan does show cancer." That "not" is doing a lot of work, and is very easy to miss when you're talking fast and never intend to read your own note ever again.
More subtle is the grammatical error in the first sentence. "This note was #dictated using Dragon text to speech recognition software." Either they changed their product name to "Dragon Text", in which case the capitalization is off. Or they transposed words and it should read "speech to text" or "speech recognition" with no text.
👉 In other words, they didn't even proof-read their own disclaimer! 😱
#MedicalRecords #Medicine #SpeechToText #Liability #Risk #SignalToNoise -
You stated: <<What it actually says is "AI is _permitted_ to make mistakes; _you are liable_ for the results, whether you check them or not". Except "you" is generally not even the person building, installing, or even using the AI. It's the person the AI is used on.>>
Way back in the early 2000s, there was a system called "Dragon Dictate". The goal was to eliminate #human #transcriptionists with automated speech-to-text (sound familiar?) The system had to be trained on your voice and vocabulary. Once properly trained it could do a pretty good job, I'll guess 95-98%. It was better suited to output that was stereotyped (mostly the same), and structured (such as radiology reports and operative notes).
Regardless of how the note/report was generated, the professional who spoke the words had a obligation to at least scan the output and sign it (yes, with an ink pen!). Once signed it became part of the "legal medical record" open to misinterpretation, copying, lawsuits, etc. etc.
Once Dragon Dictate became routine (and they fired all the transcriptionists) I started to notice this little #disclaimer at the bottom:
"If portions of this note are confusing or indecipherable please feel free to call me with questions or concerns." Sounds a lot like #AI to me! I polite way to summarize this is:
👉 They were trying to force me to be their copy-editor. 👈
It cast the entire content in doubt.
Consider for a moment the difference between saying "The scan does not show cancer." and "The scan does show cancer." That "not" is doing a lot of work, and is very easy to miss when you're talking fast and never intend to read your own note ever again.
More subtle is the grammatical error in the first sentence. "This note was #dictated using Dragon text to speech recognition software." Either they changed their product name to "Dragon Text", in which case the capitalization is off. Or they transposed words and it should read "speech to text" or "speech recognition" with no text.
👉 In other words, they didn't even proof-read their own disclaimer! 😱
#MedicalRecords #Medicine #SpeechToText #Liability #Risk #SignalToNoise -
You stated: <<What it actually says is "AI is _permitted_ to make mistakes; _you are liable_ for the results, whether you check them or not". Except "you" is generally not even the person building, installing, or even using the AI. It's the person the AI is used on.>>
Way back in the early 2000s, there was a system called "Dragon Dictate". The goal was to eliminate #human #transcriptionists with automated speech-to-text (sound familiar?) The system had to be trained on your voice and vocabulary. Once properly trained it could do a pretty good job, I'll guess 95-98%. It was better suited to output that was stereotyped (mostly the same), and structured (such as radiology reports and operative notes).
Regardless of how the note/report was generated, the professional who spoke the words had a obligation to at least scan the output and sign it (yes, with an ink pen!). Once signed it became part of the "legal medical record" open to misinterpretation, copying, lawsuits, etc. etc.
Once Dragon Dictate became routine (and they fired all the transcriptionists) I started to notice this little #disclaimer at the bottom:
"If portions of this note are confusing or indecipherable please feel free to call me with questions or concerns." Sounds a lot like #AI to me! I polite way to summarize this is:
👉 They were trying to force me to be their copy-editor. 👈
It cast the entire content in doubt.
Consider for a moment the difference between saying "The scan does not show cancer." and "The scan does show cancer." That "not" is doing a lot of work, and is very easy to miss when you're talking fast and never intend to read your own note ever again.
More subtle is the grammatical error in the first sentence. "This note was #dictated using Dragon text to speech recognition software." Either they changed their product name to "Dragon Text", in which case the capitalization is off. Or they transposed words and it should read "speech to text" or "speech recognition" with no text.
👉 In other words, they didn't even proof-read their own disclaimer! 😱
#MedicalRecords #Medicine #SpeechToText #Liability #Risk #SignalToNoise -
You stated: <<What it actually says is "AI is _permitted_ to make mistakes; _you are liable_ for the results, whether you check them or not". Except "you" is generally not even the person building, installing, or even using the AI. It's the person the AI is used on.>>
Way back in the early 2000s, there was a system called "Dragon Dictate". The goal was to eliminate #human #transcriptionists with automated speech-to-text (sound familiar?) The system had to be trained on your voice and vocabulary. Once properly trained it could do a pretty good job, I'll guess 95-98%. It was better suited to output that was stereotyped (mostly the same), and structured (such as radiology reports and operative notes).
Regardless of how the note/report was generated, the professional who spoke the words had a obligation to at least scan the output and sign it (yes, with an ink pen!). Once signed it became part of the "legal medical record" open to misinterpretation, copying, lawsuits, etc. etc.
Once Dragon Dictate became routine (and they fired all the transcriptionists) I started to notice this little #disclaimer at the bottom:
"If portions of this note are confusing or indecipherable please feel free to call me with questions or concerns." Sounds a lot like #AI to me! I polite way to summarize this is:
👉 They were trying to force me to be their copy-editor. 👈
It cast the entire content in doubt.
Consider for a moment the difference between saying "The scan does not show cancer." and "The scan does show cancer." That "not" is doing a lot of work, and is very easy to miss when you're talking fast and never intend to read your own note ever again.
More subtle is the grammatical error in the first sentence. "This note was #dictated using Dragon text to speech recognition software." Either they changed their product name to "Dragon Text", in which case the capitalization is off. Or they transposed words and it should read "speech to text" or "speech recognition" with no text.
👉 In other words, they didn't even proof-read their own disclaimer! 😱
#MedicalRecords #Medicine #SpeechToText #Liability #Risk #SignalToNoise -
Ich glaube ein Post dieser Art ist heutzutage nötig.
-
Ich glaube ein Post dieser Art ist heutzutage nötig.
-
Ich glaube ein Post dieser Art ist heutzutage nötig.
-
Ich glaube ein Post dieser Art ist heutzutage nötig.
-
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis -
If you're in need of a thread-safe, native #C++, implementation of #DBus I recommend DBus-ASIO. (As seen at #FOSDEM!)
https://github.com/dbus-asio/dbus-asio #disclaimer #imadethis