home.social

Search

629 results for “thomasfuchs”

  1. @thomasfuchs The I coveted, IIRC, was 3 megabytes for $5K (maybe 5MB for $3K) for an in the very early . Hard to imagine in this day of $10 32GB microsd cards and 8GB

  2. @thomasfuchs This is exactly what I was afraid of as the exodus/influx continues. I didn't predict it would the #journalists who couldn't adapt their behavior but want to change their new environment, though. Thanks for pointing this out.

    lesson for all of #digitalcivilsociety

    Don't be jerks
    philanthropy.blogspot.com/2022

  3. @thomasfuchs I concur as well. Also, this is a similar strategy that @mammoth is using for their app upon #MothSocial: mammoth.writeas.com/the-mammot

    People can always move to a different instance or setup their own later on. This is what I did.

  4. @gdlf @thomasfuchs
    > What a machine the #c64 was!

    Yes, not to mention what a machine it still is!

    I've just been playing #Lester, a polished and thoroughly enjoyable C64 game that was released only yesterday, not sure it even qualifies as #RetroGaming ;)

  5. @SpaceLifeForm @thomasfuchs

    Alternatively, use the NoScript plugin (Firefox on Android and desktop operating systems) and do not trust (default behaviour is to block, explicit blocking is possible too) Cloudflare.

    Note that this method does not prevent Cloudflare from knowing your IP-address, but effectively this tells them that they suck if you do not enable their invasive JavaScript code "to detetmine whether the connection is safe".

    A connection that is actually very much NOT safe; there's an Attacker in the Middle spying on everything bit exchanged if you continue. They even collect every password you enter on websites proxied by Cloudflare (blog.cloudflare.com/password-r).

    #CloudflareIsEvil #BigTechIsEvil #AitM #MitM #Cloudflare

  6. @gunstick @elithebearded @lmorchard @thomasfuchs I believe it was Dorian Gray who invented the "timn-sequence diagram" we all use today.
    #DorianGray #timn #uml

  7. @gunstick @elithebearded @lmorchard @thomasfuchs I believe it was Dorian Gray who invented the "timn-sequence diagram" we all use today.
    #DorianGray #timn #uml

  8. @gunstick @elithebearded @lmorchard @thomasfuchs I believe it was Dorian Gray who invented the "timn-sequence diagram" we all use today.

  9. @gunstick @elithebearded @lmorchard @thomasfuchs I believe it was Dorian Gray who invented the "timn-sequence diagram" we all use today.
    #DorianGray #timn #uml

  10. @gunstick @elithebearded @lmorchard @thomasfuchs I believe it was Dorian Gray who invented the "timn-sequence diagram" we all use today.
    #DorianGray #timn #uml

  11. Someone, possibly in collaboration with an LLM, is bound to invent it any day now. Of course, there's all of that old code to replace or integrate with and as long as people are deciding what to do and how to do that, it's likely to result in a big mess. #realistic

    @thomasfuchs @mark

  12. @BoredomFestival @thomasfuchs

    I'm a bit ashamed to admit that I once owned a quite extensive list of "unintended" opcodes in then popular microprocessors like the 6502 or the Z80, but somehow lost it after having finished university and moved on to later technologies. 😭

    So, at some time between the end of the 80s and now, my virtual cat or imagined dog must have eaten it. 😉

    May be you can still find that stuff on the interwebs, hidden somewhere in between all that AI slop. Wikipedia might help you.

    To give you a hint from ancient memories: The Z80 could architecturally access its registers in both 8 bit and 16 bit chunks - except for the IX and IY ones. Documented as index registers like the well-known HL one (i.e. concatenated H and L), they were portrayed as non-splittable. But they were as people found out, giving you more independently manipulatable registers for situations where you could take advantage of that capability. The IX/IY prefixes were functional pretty much everywhere. Later implementations of the Z80 architecture may have lost that undocumented capability.

    #legacy #microprocessor #programming #retrocomputing #noAI

  13. @BoredomFestival @thomasfuchs

    I'm a bit ashamed to admit that I once owned a quite extensive list of "unintended" opcodes in then popular microprocessors like the 6502 or the Z80, but somehow lost it after having finished university and moved on to later technologies. 😭

    So, at some time between the end of the 80s and now, my virtual cat or imagined dog must have eaten it. 😉

    May be you can still find that stuff on the interwebs, hidden somewhere in between all that AI slop. Wikipedia might help you.

    To give you a hint from ancient memories: The Z80 could architecturally access its registers in both 8 bit and 16 bit chunks - except for the IX and IY ones. Documented as index registers like the well-known HL one (i.e. concatenated H and L), they were portrayed as non-splittable. But they were as people found out, giving you more independently manipulatable registers for situations where you could take advantage of that capability. The IX/IY prefixes were functional pretty much everywhere. Later implementations of the Z80 architecture may have lost that undocumented capability.

    #legacy #microprocessor #programming #retrocomputing #noAI

  14. RE: hachyderm.io/@thomasfuchs/1163

    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.

    #law

  15. RE: hachyderm.io/@thomasfuchs/1165

    I wonder what they offer as alternative. I'd say, never ever use #HCaptcha because it's 100% accessibility nightmare. ReCaptcha is at least accessible.

  16. 🤖🧠 Why #algorithms do not generate #consciousness

    As #ThomasFuchs explains in the #Zoomposium, the difference lies in the fact that consciousness is always embodied.

    It is not just a process in the #brain or an #algorithm on a hard drive.

    Only a #system that experiences the “coherence” of its experience can truly understand.

    🎥 youtu.be/1ouxs6P3Enc

    📎philosophies.de/index.php/2022

    #Embodiment #PhilosophyOfMind #ArtificialIntelligence #MachineConsciousness #Algorithms #Digitalization

  17. 🤖 #ArtificialIntelligence – Where does #truth end? 🧠💻

    How far can #AI really think – or is it just pretending?

    In the #Zoomposium, we discuss with #ThomasFuchs why the illusion that AI could want to “live” is a fallacy, and why the #body plays a central role in decision-making and #consciousness.

    🎥 youtu.be/1ouxs6P3Enc

    📎philosophies.de/index.php/2022

    #embodiment #artificialintelligence #machineconsciousness #algorithms #digitalization #YuvalHarari #BigData #HomoDeus

  18. The secret role of #pain – More than just a #feeling 🤒 ✨

    What if pain were more than just a signal from the #body – what if it were a fundamental condition of #consciousness itself?

    In our #Zoomposium with #ThomasFuchs, we discuss the fascinating question of why pain not only “hurts” but is also functionally necessary.

    #Embodiment #Phenomenology #PhenomenalConsciousness #EmbodiedConsciousness #PhilosophyOfMind #CognitiveNeuroscience

  19. @SpaceLifeForm @thomasfuchs

    Alternatively, use the NoScript plugin (Firefox on Android and desktop operating systems) and do not trust (default behaviour is to block, explicit blocking is possible too) Cloudflare.

    Note that this method does not prevent Cloudflare from knowing your IP-address, but effectively this tells them that they suck if you do not enable their invasive JavaScript code "to detetmine whether the connection is safe".

    A connection that is actually very much NOT safe; there's an Attacker in the Middle spying on everything bit exchanged if you continue. They even collect every password you enter on websites proxied by Cloudflare (blog.cloudflare.com/password-r).

    #CloudflareIsEvil #BigTechIsEvil #AitM #MitM #Cloudflare

  20. @SpaceLifeForm @thomasfuchs

    Alternatively, use the NoScript plugin (Firefox on Android and desktop operating systems) and do not trust (default behaviour is to block, explicit blocking is possible too) Cloudflare.

    Note that this method does not prevent Cloudflare from knowing your IP-address, but effectively this tells them that they suck if you do not enable their invasive JavaScript code "to detetmine whether the connection is safe".

    A connection that is actually very much NOT safe; there's an Attacker in the Middle spying on everything bit exchanged if you continue. They even collect every password you enter on websites proxied by Cloudflare (blog.cloudflare.com/password-r).

    #CloudflareIsEvil #BigTechIsEvil #AitM #MitM #Cloudflare