home.social

#socratic — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #socratic, aggregated by home.social.

  1. I have 3 tetradrachems from about 420BCE. I use them to explain to my grandchildren that when these were pressed, Socrates was training some of our greatest philosophers(and subtly teaching an early version of the #socratic method) , Euripides plays were performed during his lifetime, and Alexander was ravaging….well…pretty much everything.

    Also, great images. Thanks.

    Also, thanks for the ALT text so I could participate.

  2. I have 3 tetradrachems from about 420BCE. I use them to explain to my grandchildren that when these were pressed, Socrates was training some of our greatest philosophers(and subtly teaching an early version of the #socratic method) , Euripides plays were performed during his lifetime, and Alexander was ravaging….well…pretty much everything.

    Also, great images. Thanks.

    Also, thanks for the ALT text so I could participate.

  3. #3goodthings
    💌 I organized my files and documents. Thank you, hole punch!
    ✂️ I completed another prototype for my paper project. Endless ideas means consistent production and play is needed and enjoyable.
    ✨ My affirmation practice is on day 20 and still feeling generative and new! I'll share more on that later.

    I really came on this platform to cultivate #AudaciousHope . I just learned about #Socratic hope from Duncan-Andrade and #buildingAntiRacistWhiteEducators #BARWE

  4. #3goodthings
    💌 I organized my files and documents. Thank you, hole punch!
    ✂️ I completed another prototype for my paper project. Endless ideas means consistent production and play is needed and enjoyable.
    ✨ My affirmation practice is on day 20 and still feeling generative and new! I'll share more on that later.

    I really came on this platform to cultivate #AudaciousHope . I just learned about #Socratic hope from Duncan-Andrade and #buildingAntiRacistWhiteEducators #BARWE

  5. #3goodthings
    💌 I organized my files and documents. Thank you, hole punch!
    ✂️ I completed another prototype for my paper project. Endless ideas means consistent production and play is needed and enjoyable.
    ✨ My affirmation practice is on day 20 and still feeling generative and new! I'll share more on that later.

    I really came on this platform to cultivate #AudaciousHope . I just learned about #Socratic hope from Duncan-Andrade and #buildingAntiRacistWhiteEducators #BARWE

  6. #3goodthings
    💌 I organized my files and documents. Thank you, hole punch!
    ✂️ I completed another prototype for my paper project. Endless ideas means consistent production and play is needed and enjoyable.
    ✨ My affirmation practice is on day 20 and still feeling generative and new! I'll share more on that later.

    I really came on this platform to cultivate #AudaciousHope . I just learned about #Socratic hope from Duncan-Andrade and #buildingAntiRacistWhiteEducators #BARWE

  7. #3goodthings
    💌 I organized my files and documents. Thank you, hole punch!
    ✂️ I completed another prototype for my paper project. Endless ideas means consistent production and play is needed and enjoyable.
    ✨ My affirmation practice is on day 20 and still feeling generative and new! I'll share more on that later.

    I really came on this platform to cultivate #AudaciousHope . I just learned about #Socratic hope from Duncan-Andrade and #buildingAntiRacistWhiteEducators #BARWE

  8. #ThisMachineKills 334. #Israel’s #AI Kill List: “Once you go automatic, target generation goes crazy.”

    soundcloud.com/thismachinekill

    So that you do not have to go to Twitter for the pdf they are talking about the link here

    static1.squarespace.com/static

    #Alignment #Socratic #OpenAI

    The Meaning Alignment Institute is a research organization with the goal of ensuring human flourishing in the age of AGI, through our unique expertise in meaning and values.

    meaningalignment.org/

    github.com/meaningalignment/df

  9. #ThisMachineKills 334. #Israel’s #AI Kill List: “Once you go automatic, target generation goes crazy.”

    soundcloud.com/thismachinekill

    So that you do not have to go to Twitter for the pdf they are talking about the link here

    static1.squarespace.com/static

    #Alignment #Socratic #OpenAI

    The Meaning Alignment Institute is a research organization with the goal of ensuring human flourishing in the age of AGI, through our unique expertise in meaning and values.

    meaningalignment.org/

    github.com/meaningalignment/df


  10. Working at is like owning second passport. His company was bought by Google
    Google's work culture is so homogenised that working at the company, and using its ID card to open different doors
    indiatoday.in/technology/news/

  11. "Know Thyself": A #Socratic Approach to Modern #STEM #Education
    The heart of Socratic #pedagogy is not merely the transmission of knowledge, but the fostering of wisdom and virtue. For Socrates, the key to wisdom was not only about accumulating information but about deep introspection and understanding oneself. If STEM education is to create not just skilled workers but also enlightened individuals, then it must be rooted in a deep awareness of self and society.
    msn.com/en-us/news/technology/

  12. "Know Thyself": A #Socratic Approach to Modern #STEM #Education
    The heart of Socratic #pedagogy is not merely the transmission of knowledge, but the fostering of wisdom and virtue. For Socrates, the key to wisdom was not only about accumulating information but about deep introspection and understanding oneself. If STEM education is to create not just skilled workers but also enlightened individuals, then it must be rooted in a deep awareness of self and society.
    msn.com/en-us/news/technology/

  13. "Know Thyself": A Approach to Modern
    The heart of Socratic is not merely the transmission of knowledge, but the fostering of wisdom and virtue. For Socrates, the key to wisdom was not only about accumulating information but about deep introspection and understanding oneself. If STEM education is to create not just skilled workers but also enlightened individuals, then it must be rooted in a deep awareness of self and society.
    msn.com/en-us/news/technology/

  14. "Know Thyself": A #Socratic Approach to Modern #STEM #Education
    The heart of Socratic #pedagogy is not merely the transmission of knowledge, but the fostering of wisdom and virtue. For Socrates, the key to wisdom was not only about accumulating information but about deep introspection and understanding oneself. If STEM education is to create not just skilled workers but also enlightened individuals, then it must be rooted in a deep awareness of self and society.
    msn.com/en-us/news/technology/

  15. "Know Thyself": A #Socratic Approach to Modern #STEM #Education
    The heart of Socratic #pedagogy is not merely the transmission of knowledge, but the fostering of wisdom and virtue. For Socrates, the key to wisdom was not only about accumulating information but about deep introspection and understanding oneself. If STEM education is to create not just skilled workers but also enlightened individuals, then it must be rooted in a deep awareness of self and society.
    msn.com/en-us/news/technology/

  16. @neil @tallship @tallship @smallcircles That got concatenated here on Hubzilla...

    Here it is again.

    Are we really discussing this now? And Is it the FOSS project you know that I’m thinking of? 🙂

    I’ve been mired in the Codeberg issue tracker lately and haven’t given chat the attention it deserves, but I’ve only got so much time (money) to spend in contributing to the project each week and I have had to draw a hard budget line at $1.2k/week. I wish I could afford to donate more money each week to the project, but I also have to spend time actually earning that money as well as spending it elsewhere on comfort items… Like watching movies or going to see a local musician or poet perform. Lolz…

    Anyway, here’s my take. MIT and BSD licenses are nice but subject to capture, and designed to work in a world that was generally without patent trolls in a sharing, institutional education environment.

    Scientists share - hypercapitalist corporations rip you off, inject proprietary closed sourced code into MIT licensed code they don’t have to show you (a mere copyright notice stating that the product contains at least some freely licensed code will suffice in satisfying the licensing terms)… And if there’s a novel “process” involved (i e., federating capabilities) they patent YOU and YOUR COLLEAGUES work for themselves.

    A few years back, I was stunned to find out that #Microsoft was receiving about $7 from every single #Android device shipped for #patents they hold related to Linux.

    But again, I digress…

    Okay…

    Basically, and for my part, I say “Copyleft”, in the most general terms, and if it’s software that is well suited as a self or commercially hosted SaaS offering environment, then #AGPL - but then, that begs your question: AGPL v3 or later, or AGPL v3 only?

    Yes, if you say, “or later”, then you run the risk of unfavorable licensing at some point in the future, but that’s not a certainty.

    But it is a constant, distinct possibility. Always has been.

    Being a pain in the ass to go from “3 only”, or to “or later”, or to some other constraint is an inconvenience - that’s all. Time, labor, money. That’s pretty much it when it comes to re-licensing. That cost goes down if #CONTRIBUTING.md specifies that contributors agree to the project re-licensing their contributions under some other #Copyleft license at some point in the future.

    To answer the rest of your question, I’mma just gonna get all #Socratic on you…

    ) Do you trust #RMS and the #FSF? - that used to be the question to ponder, because you were actually assigning control to them.

    ) What would #Linus do?

    Actually, what did Linus do?

    He chose #GPL v2 a long time ago when he re-licensed the #Linux kernel.

    He also chose GPL v2 “only” - and you can search on #PeerTube for videos that have him explaining why, and further, why he is happy that he didn’t choose, “or later”, and how he feels that, in retrospect, that would have been a very bad thing.

    So here’s my 2¢, and I’ve already expressed this in my typical “IMNSHO” fashion a couple of times before in the project’s Matrix room (if we’re talking about the same project), but I’ll give it again here one more time.

    A.) Do it now, rather than later, or do it yesterday if that’s possible yet (you may need to consult H.G. Wells or Einstein in that regard).

    B.) Use a Copyleft license - specifically, I’m advocating for AGPL - but as long as it’s Copyleft, preferably AGPL v3, my immediate concerns are alleviated. Whether that’s “only”, or “or later”, that’s of very little import AFAIC.

    C.) Ensure that CONTRIBUTING.md states that the project is at liberty to contribute patches to the deprecated, antecedent project in the form of patches gifted to them under the terms of the MIT license - after all, we want to be good neighbors and software stewards in the #FOSS space

    I’ve already discussed the simplicity of doing so in chat and consensus was roundly in favor with this approach, and also in doing it now.

    D.) Hard fork now.

    Finally, there had been much concern expressed from several of the other project members that we’re going to suffer recruiting issues by not being able to insure to potential new contributors that their efforts won’t be subject to #corporate or #special interest or #trademark lobby #capture, where they could likely see their blood, sweat, and tears released as #closed source #proprietary products, until such time as we do re-license under a Copyleft license.

    I hope that helps! 🙂

    #tallship



    .
  17. @neil @tallship @tallship @smallcircles That got concatenated here on Hubzilla...

    Here it is again.

    Are we really discussing this now? And Is it the FOSS project you know that I’m thinking of? 🙂

    I’ve been mired in the Codeberg issue tracker lately and haven’t given chat the attention it deserves, but I’ve only got so much time (money) to spend in contributing to the project each week and I have had to draw a hard budget line at $1.2k/week. I wish I could afford to donate more money each week to the project, but I also have to spend time actually earning that money as well as spending it elsewhere on comfort items… Like watching movies or going to see a local musician or poet perform. Lolz…

    Anyway, here’s my take. MIT and BSD licenses are nice but subject to capture, and designed to work in a world that was generally without patent trolls in a sharing, institutional education environment.

    Scientists share - hypercapitalist corporations rip you off, inject proprietary closed sourced code into MIT licensed code they don’t have to show you (a mere copyright notice stating that the product contains at least some freely licensed code will suffice in satisfying the licensing terms)… And if there’s a novel “process” involved (i e., federating capabilities) they patent YOU and YOUR COLLEAGUES work for themselves.

    A few years back, I was stunned to find out that #Microsoft was receiving about $7 from every single #Android device shipped for #patents they hold related to Linux.

    But again, I digress…

    Okay…

    Basically, and for my part, I say “Copyleft”, in the most general terms, and if it’s software that is well suited as a self or commercially hosted SaaS offering environment, then #AGPL - but then, that begs your question: AGPL v3 or later, or AGPL v3 only?

    Yes, if you say, “or later”, then you run the risk of unfavorable licensing at some point in the future, but that’s not a certainty.

    But it is a constant, distinct possibility. Always has been.

    Being a pain in the ass to go from “3 only”, or to “or later”, or to some other constraint is an inconvenience - that’s all. Time, labor, money. That’s pretty much it when it comes to re-licensing. That cost goes down if #CONTRIBUTING.md specifies that contributors agree to the project re-licensing their contributions under some other #Copyleft license at some point in the future.

    To answer the rest of your question, I’mma just gonna get all #Socratic on you…

    ) Do you trust #RMS and the #FSF? - that used to be the question to ponder, because you were actually assigning control to them.

    ) What would #Linus do?

    Actually, what did Linus do?

    He chose #GPL v2 a long time ago when he re-licensed the #Linux kernel.

    He also chose GPL v2 “only” - and you can search on #PeerTube for videos that have him explaining why, and further, why he is happy that he didn’t choose, “or later”, and how he feels that, in retrospect, that would have been a very bad thing.

    So here’s my 2¢, and I’ve already expressed this in my typical “IMNSHO” fashion a couple of times before in the project’s Matrix room (if we’re talking about the same project), but I’ll give it again here one more time.

    A.) Do it now, rather than later, or do it yesterday if that’s possible yet (you may need to consult H.G. Wells or Einstein in that regard).

    B.) Use a Copyleft license - specifically, I’m advocating for AGPL - but as long as it’s Copyleft, preferably AGPL v3, my immediate concerns are alleviated. Whether that’s “only”, or “or later”, that’s of very little import AFAIC.

    C.) Ensure that CONTRIBUTING.md states that the project is at liberty to contribute patches to the deprecated, antecedent project in the form of patches gifted to them under the terms of the MIT license - after all, we want to be good neighbors and software stewards in the #FOSS space

    I’ve already discussed the simplicity of doing so in chat and consensus was roundly in favor with this approach, and also in doing it now.

    D.) Hard fork now.

    Finally, there had been much concern expressed from several of the other project members that we’re going to suffer recruiting issues by not being able to insure to potential new contributors that their efforts won’t be subject to #corporate or #special interest or #trademark lobby #capture, where they could likely see their blood, sweat, and tears released as #closed source #proprietary products, until such time as we do re-license under a Copyleft license.

    I hope that helps! 🙂

    #tallship



    .
  18. @neil @tallship @tallship @smallcircles That got concatenated here on Hubzilla...

    Here it is again.

    Are we really discussing this now? And Is it the FOSS project you know that I’m thinking of? 🙂

    I’ve been mired in the Codeberg issue tracker lately and haven’t given chat the attention it deserves, but I’ve only got so much time (money) to spend in contributing to the project each week and I have had to draw a hard budget line at $1.2k/week. I wish I could afford to donate more money each week to the project, but I also have to spend time actually earning that money as well as spending it elsewhere on comfort items… Like watching movies or going to see a local musician or poet perform. Lolz…

    Anyway, here’s my take. MIT and BSD licenses are nice but subject to capture, and designed to work in a world that was generally without patent trolls in a sharing, institutional education environment.

    Scientists share - hypercapitalist corporations rip you off, inject proprietary closed sourced code into MIT licensed code they don’t have to show you (a mere copyright notice stating that the product contains at least some freely licensed code will suffice in satisfying the licensing terms)… And if there’s a novel “process” involved (i e., federating capabilities) they patent YOU and YOUR COLLEAGUES work for themselves.

    A few years back, I was stunned to find out that #Microsoft was receiving about $7 from every single #Android device shipped for #patents they hold related to Linux.

    But again, I digress…

    Okay…

    Basically, and for my part, I say “Copyleft”, in the most general terms, and if it’s software that is well suited as a self or commercially hosted SaaS offering environment, then #AGPL - but then, that begs your question: AGPL v3 or later, or AGPL v3 only?

    Yes, if you say, “or later”, then you run the risk of unfavorable licensing at some point in the future, but that’s not a certainty.

    But it is a constant, distinct possibility. Always has been.

    Being a pain in the ass to go from “3 only”, or to “or later”, or to some other constraint is an inconvenience - that’s all. Time, labor, money. That’s pretty much it when it comes to re-licensing. That cost goes down if #CONTRIBUTING.md specifies that contributors agree to the project re-licensing their contributions under some other #Copyleft license at some point in the future.

    To answer the rest of your question, I’mma just gonna get all #Socratic on you…

    ) Do you trust #RMS and the #FSF? - that used to be the question to ponder, because you were actually assigning control to them.

    ) What would #Linus do?

    Actually, what did Linus do?

    He chose #GPL v2 a long time ago when he re-licensed the #Linux kernel.

    He also chose GPL v2 “only” - and you can search on #PeerTube for videos that have him explaining why, and further, why he is happy that he didn’t choose, “or later”, and how he feels that, in retrospect, that would have been a very bad thing.

    So here’s my 2¢, and I’ve already expressed this in my typical “IMNSHO” fashion a couple of times before in the project’s Matrix room (if we’re talking about the same project), but I’ll give it again here one more time.

    A.) Do it now, rather than later, or do it yesterday if that’s possible yet (you may need to consult H.G. Wells or Einstein in that regard).

    B.) Use a Copyleft license - specifically, I’m advocating for AGPL - but as long as it’s Copyleft, preferably AGPL v3, my immediate concerns are alleviated. Whether that’s “only”, or “or later”, that’s of very little import AFAIC.

    C.) Ensure that CONTRIBUTING.md states that the project is at liberty to contribute patches to the deprecated, antecedent project in the form of patches gifted to them under the terms of the MIT license - after all, we want to be good neighbors and software stewards in the #FOSS space

    I’ve already discussed the simplicity of doing so in chat and consensus was roundly in favor with this approach, and also in doing it now.

    D.) Hard fork now.

    Finally, there had been much concern expressed from several of the other project members that we’re going to suffer recruiting issues by not being able to insure to potential new contributors that their efforts won’t be subject to #corporate or #special interest or #trademark lobby #capture, where they could likely see their blood, sweat, and tears released as #closed source #proprietary products, until such time as we do re-license under a Copyleft license.

    I hope that helps! 🙂

    #tallship



    .
  19. @neil @tallship @tallship @smallcircles That got concatenated here on Hubzilla...

    Here it is again.

    Are we really discussing this now? And Is it the FOSS project you know that I’m thinking of? 🙂

    I’ve been mired in the Codeberg issue tracker lately and haven’t given chat the attention it deserves, but I’ve only got so much time (money) to spend in contributing to the project each week and I have had to draw a hard budget line at $1.2k/week. I wish I could afford to donate more money each week to the project, but I also have to spend time actually earning that money as well as spending it elsewhere on comfort items… Like watching movies or going to see a local musician or poet perform. Lolz…

    Anyway, here’s my take. MIT and BSD licenses are nice but subject to capture, and designed to work in a world that was generally without patent trolls in a sharing, institutional education environment.

    Scientists share - hypercapitalist corporations rip you off, inject proprietary closed sourced code into MIT licensed code they don’t have to show you (a mere copyright notice stating that the product contains at least some freely licensed code will suffice in satisfying the licensing terms)… And if there’s a novel “process” involved (i e., federating capabilities) they patent YOU and YOUR COLLEAGUES work for themselves.

    A few years back, I was stunned to find out that #Microsoft was receiving about $7 from every single #Android device shipped for #patents they hold related to Linux.

    But again, I digress…

    Okay…

    Basically, and for my part, I say “Copyleft”, in the most general terms, and if it’s software that is well suited as a self or commercially hosted SaaS offering environment, then #AGPL - but then, that begs your question: AGPL v3 or later, or AGPL v3 only?

    Yes, if you say, “or later”, then you run the risk of unfavorable licensing at some point in the future, but that’s not a certainty.

    But it is a constant, distinct possibility. Always has been.

    Being a pain in the ass to go from “3 only”, or to “or later”, or to some other constraint is an inconvenience - that’s all. Time, labor, money. That’s pretty much it when it comes to re-licensing. That cost goes down if #CONTRIBUTING.md specifies that contributors agree to the project re-licensing their contributions under some other #Copyleft license at some point in the future.

    To answer the rest of your question, I’mma just gonna get all #Socratic on you…

    ) Do you trust #RMS and the #FSF? - that used to be the question to ponder, because you were actually assigning control to them.

    ) What would #Linus do?

    Actually, what did Linus do?

    He chose #GPL v2 a long time ago when he re-licensed the #Linux kernel.

    He also chose GPL v2 “only” - and you can search on #PeerTube for videos that have him explaining why, and further, why he is happy that he didn’t choose, “or later”, and how he feels that, in retrospect, that would have been a very bad thing.

    So here’s my 2¢, and I’ve already expressed this in my typical “IMNSHO” fashion a couple of times before in the project’s Matrix room (if we’re talking about the same project), but I’ll give it again here one more time.

    A.) Do it now, rather than later, or do it yesterday if that’s possible yet (you may need to consult H.G. Wells or Einstein in that regard).

    B.) Use a Copyleft license - specifically, I’m advocating for AGPL - but as long as it’s Copyleft, preferably AGPL v3, my immediate concerns are alleviated. Whether that’s “only”, or “or later”, that’s of very little import AFAIC.

    C.) Ensure that CONTRIBUTING.md states that the project is at liberty to contribute patches to the deprecated, antecedent project in the form of patches gifted to them under the terms of the MIT license - after all, we want to be good neighbors and software stewards in the #FOSS space

    I’ve already discussed the simplicity of doing so in chat and consensus was roundly in favor with this approach, and also in doing it now.

    D.) Hard fork now.

    Finally, there had been much concern expressed from several of the other project members that we’re going to suffer recruiting issues by not being able to insure to potential new contributors that their efforts won’t be subject to #corporate or #special interest or #trademark lobby #capture, where they could likely see their blood, sweat, and tears released as #closed source #proprietary products, until such time as we do re-license under a Copyleft license.

    I hope that helps! 🙂

    #tallship



    .
  20. @smallcircles @neil Are we really discussing this now? And Is it the FOSS project you know that I'm thinking of? 🙂

    I've been mired in the issue tracker lately, but I've only got so much time to spend.

    Here's my take. MIT and BSD licenses are nice but subject to capture, and designed to work in a world that was generally without patent trolls in a sharing, institutional education environment.

    Scientists share - corporations rip you off, injecting proprietary closed sourced code into MIT licensed code they don't have to show you (a mere copyright notice stating that the product contains at least some freely licensed code will suffice in satisfying the licensing terms)... And if there's a novel "process" involved (i e., federating capabilities) they patent YOU and YOUR COLLEAGUES work for themselves.

    A few years back, I was stunned to find out that #Microsoft was receiving about $7 from every single #Android device shipped for #patents they hold related to Linux.

    But again, I digress...

    Okay...

    Basically, and for my part, I say "Copyleft", in the most general terms, and if it's software that is well suited as a self or commercially hosted SaaS offering environment, then #AGPL - but then, that begs your question: AGPL v3 or later, or AGPL v3 only?

    Yes, if you say, "or later", then you run the risk of unfavorable licensing at some point in the future, but that's not a certainty.

    But it is a constant, distinct possibility. Always has been.

    Being a pain in the ass to go from "3 only", or to "or later", or to some other constraint is an inconvenience - that's all. Time, labor, money. That's pretty much it when it comes to re-licensing. That cost goes down if #CONTRIBUTING.md specifies that contributors agree to the project re-licensing their contributions under some other #Copyleft license at some point in the future.

    To answer the rest of your question, I'mma just gonna get all #Socratic on you...

    1. ) Do you trust #RMS and the #FSF? - that used to be the question to ponder, because you were actually assigning control to them.

    2. ) What would #Linus do?

    Actually, what did Linus do?

    He chose #GPL v2 a long time ago when he re-licensed the #Linux kernel.

    He also chose GPL v2 "only" - and you can search on #PeerTube for videos that have him explaining why, and further, why he is happy that he didn't choose, "or later", and how he feels that, in retrospect, that would have been a very bad thing.

    So here's my 2¢, and I've already expressed this in my typical "IMNSHO" fashion a couple of times before in the project's Matrix room (if we're talking about the same project), but I'll give it again here one more time.

    A.) Do it now, rather than later, or do it yesterday if that's possible yet (you may need to consult H.G. Wells or Einstein in that regard).

    B.) Use a Copyleft license - specifically, I'm advocating for AGPL - but as long as it's Copyleft, preferably AGPL v3, my immediate concerns are alleviated. Whether that's "only", or "or later", that's of very little import AFAIC.

    C.) Ensure that CONTRIBUTING.md states that the project is at liberty to contribute patches to the deprecated, antecedent project in the form of patches gifted to them under the terms of the MIT license - after all, we want to be good neighbors and software stewards in the #FOSS space

    I've already discussed the simplicity of doing so in chat and consensus was roundly in favor with this approach, and also in doing it now.

    D.) Hard fork now.

    Finally, there had been much concern expressed from several of the other project members that we're going to suffer recruiting issues by not being able to insure to potential new contributors that their efforts won't be subject to #corporate or #special_interest or #trademark lobby #capture, where they could likely see their blood, sweat, and tears released as #closed_source #proprietary products, until such time as we do re-license under a Copyleft license.

    I hope that helps! 🙂

    #tallship



    .
  21. #EarthlingEd does the Socratic debate method pretty well, here his opponent is not so much on the attack but a bit overwhelmed, although does seem to answer honestly and not resorting to facetiousness which many people do. yt.artemislena.eu/watch?v=BeWt
    #vegan #Debate #Socratic

  22. #EarthlingEd does the Socratic debate method pretty well, here his opponent is not so much on the attack but a bit overwhelmed, although does seem to answer honestly and not resorting to facetiousness which many people do. yt.artemislena.eu/watch?v=BeWt
    #vegan #Debate #Socratic

  23. #EarthlingEd does the Socratic debate method pretty well, here his opponent is not so much on the attack but a bit overwhelmed, although does seem to answer honestly and not resorting to facetiousness which many people do. yt.artemislena.eu/watch?v=BeWt
    #vegan #Debate #Socratic

  24. #EarthlingEd does the Socratic debate method pretty well, here his opponent is not so much on the attack but a bit overwhelmed, although does seem to answer honestly and not resorting to facetiousness which many people do. yt.artemislena.eu/watch?v=BeWt
    #vegan #Debate #Socratic

  25. If you don't know what methods of reasoning exist, like the #socratic method, I don't want your #forensics, #opinion, #journalism, #rebuttals, #rhetoric, or #apologetics. Let that to someone who thinks little.

  26. If you don't know what methods of reasoning exist, like the #socratic method, I don't want your #forensics, #opinion, #journalism, #rebuttals, #rhetoric, or #apologetics. Let that to someone who thinks little.

  27. If you don't know what methods of reasoning exist, like the #socratic method, I don't want your #forensics, #opinion, #journalism, #rebuttals, #rhetoric, or #apologetics. Let that to someone who thinks little.

  28. If you don't know what methods of reasoning exist, like the #socratic method, I don't want your #forensics, #opinion, #journalism, #rebuttals, #rhetoric, or #apologetics. Let that to someone who thinks little.

  29. @MolemanPeter on my journey to understanding my condition I read a bit on the topic. There is quite some research on the "neurology of meditation" that shoes surprising plasticity. Anecdotal accounts of top-down control of bottom-up process through meditation is no longer speculation or a result of weltanschauung. I wonder if #contemplation in #Socratic @philosophy, as mentioned by #HannahArendt in ch.1 of the Human Condition is the same thing.

  30. @MolemanPeter on my journey to understanding my condition I read a bit on the topic. There is quite some research on the "neurology of meditation" that shoes surprising plasticity. Anecdotal accounts of top-down control of bottom-up process through meditation is no longer speculation or a result of weltanschauung. I wonder if #contemplation in #Socratic @philosophy, as mentioned by #HannahArendt in ch.1 of the Human Condition is the same thing.

  31. @MolemanPeter on my journey to understanding my condition I read a bit on the topic. There is quite some research on the "neurology of meditation" that shoes surprising plasticity. Anecdotal accounts of top-down control of bottom-up process through meditation is no longer speculation or a result of weltanschauung. I wonder if #contemplation in #Socratic @philosophy, as mentioned by #HannahArendt in ch.1 of the Human Condition is the same thing.

  32. @MolemanPeter on my journey to understanding my condition I read a bit on the topic. There is quite some research on the "neurology of meditation" that shoes surprising plasticity. Anecdotal accounts of top-down control of bottom-up process through meditation is no longer speculation or a result of weltanschauung. I wonder if in @philosophy, as mentioned by in ch.1 of the Human Condition is the same thing.

  33. @MolemanPeter on my journey to understanding my condition I read a bit on the topic. There is quite some research on the "neurology of meditation" that shoes surprising plasticity. Anecdotal accounts of top-down control of bottom-up process through meditation is no longer speculation or a result of weltanschauung. I wonder if #contemplation in #Socratic @philosophy, as mentioned by #HannahArendt in ch.1 of the Human Condition is the same thing.

  34. In education we've been learning and teaching critical analysis for a while now--and that's okay. It helps us find the flaws in systems and the liars in groups. News is no longer news; it's commentary.

    Now we need to shift focus to solutions. And for that we need to be learning and teaching more #music more #poetry more #literature more #art more #Stories contemporary #mythology more #Socratic dialogue and #conversation.

    We've all become excellent analysts and critics.

    Now, let us #create !

  35. In education we've been learning and teaching critical analysis for a while now--and that's okay. It helps us find the flaws in systems and the liars in groups. News is no longer news; it's commentary.

    Now we need to shift focus to solutions. And for that we need to be learning and teaching more #music more #poetry more #literature more #art more #Stories contemporary #mythology more #Socratic dialogue and #conversation.

    We've all become excellent analysts and critics.

    Now, let us #create !

  36. In education we've been learning and teaching critical analysis for a while now--and that's okay. It helps us find the flaws in systems and the liars in groups. News is no longer news; it's commentary.

    Now we need to shift focus to solutions. And for that we need to be learning and teaching more #music more #poetry more #literature more #art more #Stories contemporary #mythology more #Socratic dialogue and #conversation.

    We've all become excellent analysts and critics.

    Now, let us #create !

  37. In education we've been learning and teaching critical analysis for a while now--and that's okay. It helps us find the flaws in systems and the liars in groups. News is no longer news; it's commentary.

    Now we need to shift focus to solutions. And for that we need to be learning and teaching more #music more #poetry more #literature more #art more #Stories contemporary #mythology more #Socratic dialogue and #conversation.

    We've all become excellent analysts and critics.

    Now, let us #create !

  38. In education we've been learning and teaching critical analysis for a while now--and that's okay. It helps us find the flaws in systems and the liars in groups. News is no longer news; it's commentary.

    Now we need to shift focus to solutions. And for that we need to be learning and teaching more #music more #poetry more #literature more #art more #Stories contemporary #mythology more #Socratic dialogue and #conversation.

    We've all become excellent analysts and critics.

    Now, let us #create !

  39. I seem to have skipped my . I created DeviantRobot.com and the Inspire Reflection YouTube channel. I am keen to encourage people to engage in the world of ideas and civil discourse. Things I’m interested in:

  40. Google discloses its acquisition of mobile learning app Socratic as it relaunches on iOS - Google publicly disclosed its acquisition of homework helper app Socratic in an announcement this we... more: feedproxy.google.com/~r/Techcr #artificialintelligence #e-learning #schoolwork #homework #socratic #students #edtech #google #mobile #school #apps #ios #ai