GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Anthony (abucci@buc.ci)'s status on Thursday, 08-Feb-2024 09:44:45 JST Anthony Anthony
    • Paul Cantrell
    • datarama
    @datarama@hachyderm.io @inthehands@hachyderm.io I'm sorry to jump in, but I share these kinds of feelings (and I like to believe there are a fair number of us who do). It's one of the many reasons I'm so negative about today's generative AI technology. I studied AI in graduate school, and technically I might have cashed in on this but I purposely chose not to purpose a career at any of the FAANG companies or the major corporate research labs for precisely these reasons. I'd like to live to see the neoliberal era end, not grab its hand and help pull it further along.
    In conversation about a year ago from buc.ci permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:15:59 JST Paul Cantrell Paul Cantrell

      The are simply too damned many static site generators out there. Too many.

      I solved this problem in the obvious way: I wrote a new static site generator.

      In conversation Tuesday, 05-Dec-2023 06:15:59 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:17:03 JST Paul Cantrell Paul Cantrell
      in reply to

      Not public yet. I’ll share when it’s ready to share, but honestly, you probably don’t want it: it’s •exactly• what I need (or on its way to being that), so it almost certainly won’t be what you need.

      In conversation Tuesday, 05-Dec-2023 06:17:03 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:23:41 JST Paul Cantrell Paul Cantrell
      in reply to
      • Tikitu

      @tikitu
      This is approximately correct, I think

      In conversation Tuesday, 05-Dec-2023 06:23:41 JST permalink
    • Embed this notice
      Tikitu (tikitu@mastodon.social)'s status on Tuesday, 05-Dec-2023 06:23:42 JST Tikitu Tikitu
      in reply to
      • Paul Cantrell

      @inthehands seems like there should be roughly one static site generator out there for each static site out there.

      In conversation Tuesday, 05-Dec-2023 06:23:42 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:27:46 JST Paul Cantrell Paul Cantrell
      in reply to

      The thing is currently 261 lines of Ruby, and I already like it better than every alternative I’ve tried.

      Still missing a few key features (the big one is components / partials that have some way to bundle up their associated CSS + JS), so who knows, it might be 1000 lines of code in a few days here.

      Or I might actually try to make it fast, which will increase the size by ~100x and have me rewriting it in Swift or something.

      In conversation Tuesday, 05-Dec-2023 06:27:46 JST permalink
    • Embed this notice
      Jeff Miller (orange hatband) (jmeowmeow@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:28:50 JST Jeff Miller (orange hatband) Jeff Miller (orange hatband)
      in reply to
      • Paul Cantrell

      @inthehands My approach to understanding a thing tends to be comparing three examples, so "a personally fitted SSG" would be a welcome part of compare and contrast learning.

      There are many derivative static site generators which don't acknowledge that they are "Jekyll*, implemented in [language], plus [shiny feature!]"

      *For Jekyll, substitute Hugo or Pelican or Eleventy or...

      In conversation Tuesday, 05-Dec-2023 06:28:50 JST permalink
    • Embed this notice
      natnight (natknight@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:31:46 JST natnight natnight
      in reply to
      • Paul Cantrell

      @inthehands That’s where I ended up. It’s three hundred lines of Python. It’s a mess. It’s perfect for me. 🤷

      In conversation Tuesday, 05-Dec-2023 06:31:46 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:36:54 JST Paul Cantrell Paul Cantrell
      in reply to
      • Jeff Miller (orange hatband)

      @jmeowmeow
      Yeah, Jekyll, Hugo, Eleventy were examples I looked at, along with Astro and Nanoc. Three deal-killers:

      1. They’re all soooo complicated; figuring out how to fit inside their abstractions and avoid their unwanted help ultimately proved more trouble than building from zero

      2. Most of this site is migrating from a Rails app, wanted to stick with Ruby + Haml

      (2.5 Javascript annoys me, as do most templating langs; this project is supposed to be fun, and JS isn’t fun for me)

      …mainly…

      In conversation Tuesday, 05-Dec-2023 06:36:54 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Tuesday, 05-Dec-2023 06:38:37 JST Paul Cantrell Paul Cantrell
      in reply to
      • Jeff Miller (orange hatband)

      @jmeowmeow
      3. SSGs tend to have an attitude of “you want to write a bunch of web pages except in .md instead of .html,” but I want something that’s much more data-driven, with a clean data/presentation separation (borrowed heavily from Astro’s content collections approach here)

      In conversation Tuesday, 05-Dec-2023 06:38:37 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 06-Dec-2023 13:01:18 JST Paul Cantrell Paul Cantrell
      in reply to

      OK, I need a name for this thing.

      Its essential features that might be relevant for naming are:

      - Intentionally simple
      - Data / presentation separation
      - I am unreasonable for having written it at all, there are way too many SSGs out there already, just use an existing tool, Paul, what are you doing, do you have no sense at all

      Ridiculous suggestions welcome.

      In conversation Wednesday, 06-Dec-2023 13:01:18 JST permalink
    • Embed this notice
      dreffed (dreffed@infosec.exchange)'s status on Wednesday, 06-Dec-2023 13:13:42 JST dreffed dreffed
      in reply to
      • Paul Cantrell

      @inthehands "nsilk"

      In conversation Wednesday, 06-Dec-2023 13:13:42 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 06-Dec-2023 13:13:42 JST Paul Cantrell Paul Cantrell
      in reply to
      • dreffed

      @dreffed
      snice

      In conversation Wednesday, 06-Dec-2023 13:13:42 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 02:17:20 JST Paul Cantrell Paul Cantrell
      in reply to
      • Stu
      • John Wehrle

      “Superfluous” it is! Thanks, @tehstu and @CptSuperlative, and to everyone who gave suggestions.

      Working on it over holiday break, gradually rebuilding my personal site with it as I build up Superfluous itself. It’s…actually really good for my needs?! I still feel sheepish about building an SSG from scratch, which is clearly unnecessary, but it’s fun — and I’m a firm believe that fun is reason enough!

      In conversation Friday, 22-Dec-2023 02:17:20 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 04:50:40 JST Paul Cantrell Paul Cantrell
      in reply to

      OK, tossing a software terminology question out to the Fedi. Context:

      - Static site generator
      - Top-level separation between (1) data and (2) how data gets formatted / processed
      - (1) and (2) have user-visible names, are separate dirs in project root
      - (1) is basically a plain text DB (md, json, yaml, etc)
      - (2) may include: templates, scripting, partials, style, images, other static assets

      I’m calling (1) “data”. ••What should I call (2)?••

      Many options! I’m looking for your gut reaction.

      In conversation Friday, 22-Dec-2023 04:50:40 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 04:55:41 JST Paul Cantrell Paul Cantrell
      • Matthew Lyon

      @mattly It needs to be a noun. “Presentation” is one idea I was considering. It’s tough: it’s not strictly theme-related; it’s more like “all the content of the site, some of which may be data-driven templates.” But that’s definitely one in the mix.

      In conversation Friday, 22-Dec-2023 04:55:41 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 04:56:38 JST Paul Cantrell Paul Cantrell
      in reply to
      • Alex Michael Berry 🐈🐩

      @almibe Hmm, I think src = [this thing] + data

      In conversation Friday, 22-Dec-2023 04:56:38 JST permalink
    • Embed this notice
      Alex Michael Berry 🐈🐩 (almibe@fosstodon.org)'s status on Friday, 22-Dec-2023 04:56:39 JST Alex Michael Berry 🐈🐩 Alex Michael Berry 🐈🐩
      in reply to
      • Paul Cantrell

      @inthehands src

      In conversation Friday, 22-Dec-2023 04:56:39 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 04:57:16 JST Paul Cantrell Paul Cantrell
      in reply to
      • @jacquiharper

      @jacquiharper Hmm, yeah, that’s certainly what it does. Also includes images, static site text…but is that a transformation? Kind of

      In conversation Friday, 22-Dec-2023 04:57:16 JST permalink
    • Embed this notice
      @jacquiharper (jacquiharper@mastodon.world)'s status on Friday, 22-Dec-2023 04:57:18 JST @jacquiharper @jacquiharper
      in reply to
      • Paul Cantrell

      @inthehands In DITA, I believe the formatting portion is called a ‘transformation’ — may be analogous is I understand correctly

      In conversation Friday, 22-Dec-2023 04:57:18 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 04:58:31 JST Paul Cantrell Paul Cantrell
      in reply to
      • Theodore Painsworth

      @Itty53 Needs to be a directory name, not just class name. Hmmmm:

      mysite/
      data/
      controller/

      Not sure it would be natural to look for images in controller.

      In conversation Friday, 22-Dec-2023 04:58:31 JST permalink
    • Embed this notice
      Theodore Painsworth (itty53@mstdn.social)'s status on Friday, 22-Dec-2023 04:58:33 JST Theodore Painsworth Theodore Painsworth
      in reply to
      • Paul Cantrell

      @inthehands

      Actually rather a ControllerContext. Maybe.

      In conversation Friday, 22-Dec-2023 04:58:33 JST permalink
    • Embed this notice
      Theodore Painsworth (itty53@mstdn.social)'s status on Friday, 22-Dec-2023 04:58:34 JST Theodore Painsworth Theodore Painsworth
      in reply to
      • Paul Cantrell

      @inthehands

      How data is formatted, context.

      How data is processed, controller.

      So... you're describing a ContextController.

      My gut reaction anyway.

      In conversation Friday, 22-Dec-2023 04:58:34 JST permalink

      Attachments


    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 04:59:34 JST Paul Cantrell Paul Cantrell
      • Matthew Lyon

      @mattly Right right, fair enough! What I mean is I’m not sure about directory names that look like this:

      mysite/
      data/
      presenter/

      Would you naturally look for images and stylesheets in presenter? Hmm, well, maybe…

      In conversation Friday, 22-Dec-2023 04:59:34 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 05:01:58 JST Paul Cantrell Paul Cantrell
      • Matthew Lyon

      @mattly Ooo, fighting words! I’d say “data” is pretty clearly a collective noun (like water, sand, milk) when we’re talking about digital information.

      In conversation Friday, 22-Dec-2023 05:01:58 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 05:31:57 JST Paul Cantrell Paul Cantrell
      in reply to
      • Aijaz Ansari

      @aijaz This and variations on it are a clear frontrunner.

      In conversation Friday, 22-Dec-2023 05:31:57 JST permalink
    • Embed this notice
      Aijaz Ansari (aijaz@mastodon.social)'s status on Friday, 22-Dec-2023 05:31:58 JST Aijaz Ansari Aijaz Ansari
      in reply to
      • Paul Cantrell

      @inthehands Gut reaction: “Presentation.”

      In conversation Friday, 22-Dec-2023 05:31:58 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 09:01:30 JST Paul Cantrell Paul Cantrell
      in reply to

      “Presentation” is the clear winner, and it’s working well in context — in the code, and more importantly from the tool user’s perspective. I think I just needed some communal courage to slough off the Unix-flavored precedent and make a dir name that long. Thanks, everyone!

      In conversation Friday, 22-Dec-2023 09:01:30 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 22-Dec-2023 11:23:38 JST Paul Cantrell Paul Cantrell
      in reply to
      • Aijaz Ansari

      @aijaz
      oh hello flashbacks

      In conversation Friday, 22-Dec-2023 11:23:38 JST permalink
    • Embed this notice
      Aijaz Ansari (aijaz@mastodon.social)'s status on Friday, 22-Dec-2023 11:23:39 JST Aijaz Ansari Aijaz Ansari
      in reply to
      • Paul Cantrell

      @inthehands PRESEN~1

      😜

      In conversation Friday, 22-Dec-2023 11:23:39 JST permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Monday, 05-Feb-2024 02:58:24 JST Paul Cantrell Paul Cantrell
      in reply to

      UPDATE: I’ve been continuing to poke at this project in my spare time, and it’s going shockingly well.

      I will probably eventually document and share Superfluous for those who are interested — but I’m also really enjoying the old-school DIY feeling of scratching my own itch, without any expectations of wide adoption or monetization. It’s nice. Feels like an antidote to several things at once.

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Monday, 05-Feb-2024 04:14:52 JST Paul Cantrell Paul Cantrell
      • datarama

      @datarama I really hope you find a way to shed that AI brainworm that’s taken hold. It would bring me joy knowing that you’re building cool things just for the hell of it, even if I never get to see them!

      In conversation about a year ago permalink
      Matthew Lyon repeated this.
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Monday, 05-Feb-2024 04:17:06 JST Paul Cantrell Paul Cantrell
      in reply to
      • datarama

      @datarama Reminds me so much of how performing musicians felt about mechanical instruments (player piano) and then audio recording. For all the changes those things brought, even in the year 2024 people •still• love live performance, treasure it, seek it out — and more importantly, more people than ever are making music on their own, even though so many others could do more/better/whatever, in that 19th-century spirit of “piano is at the center of the home, is for the player first.”

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 07-Feb-2024 02:53:06 JST Paul Cantrell Paul Cantrell
      in reply to
      • datarama

      @datarama The point of my post above about the 19th century is that your concert-centric vision (“The spectacle, the joy of seeing a skilled performer applying their skills, the social context”) is a very specific view of what music is for — not the only one, but so dominant currently that it’s hard for us to imagine the alternatives.

      In conversation about a year ago permalink
    • Embed this notice
      datarama (datarama@hachyderm.io)'s status on Wednesday, 07-Feb-2024 02:53:07 JST datarama datarama
      in reply to
      • Paul Cantrell

      @inthehands (That is to say: Since software serves a purpose *beyond* existing, and we can fulfill that purpose without programming the software, then programming seems a lot more pointless than playing music - in music, the making of the music *is* the point, it is not a means towards that point.)

      In conversation about a year ago permalink
    • Embed this notice
      datarama (datarama@hachyderm.io)'s status on Wednesday, 07-Feb-2024 02:53:08 JST datarama datarama
      • Paul Cantrell

      @inthehands The second is that music serves no purpose beyond whatever it evokes simply by existing (and before recording, it only existed in the moment). Software serves some purpose - whether that be presenting a game world to interact with, generating pictures, doing accounting work or whatnot. Programming is the act of making software exist, and if we can make software exist without programming, then programming deteriorates into meaninglessness to an extent that performing music doesn't.

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 07-Feb-2024 02:55:09 JST Paul Cantrell Paul Cantrell
      in reply to
      • datarama

      @datarama There have been times and places when music needed no purpose beyond the music-maker’s experience.

      Piano music of the era of Chopin, Brahms, Schubert, etc. — probably Beethoven too — was not really for concert halls. It was for homes. People played it at home, sometimes for the household, sometimes just for themselves, sometimes for guests, but sometimes in the wee hours of the night for whatever ears the night had. Music that needs no audience, as my late teacher said.

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 07-Feb-2024 02:59:28 JST Paul Cantrell Paul Cantrell
      in reply to
      • datarama

      @datarama That mode of relating to music — a personal, quasi-private pursuit, centered on the home, and primarily for the player — was so pervasive in the piano’s history that there were once many hundreds of piano manufacturers in the US alone. “The big-screen TV of the 19th century,” I’ve heard it called. And the early 20th! It was the Great Depression that did it in — and radio to some extent, and to larger extent shifting values & economics post-war.

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 07-Feb-2024 03:00:45 JST Paul Cantrell Paul Cantrell
      in reply to
      • datarama

      @datarama I believe that this way of relating to creative work is now both radical and necessary, an antidote to several of the things that ail us now.

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Thursday, 08-Feb-2024 09:42:38 JST Paul Cantrell Paul Cantrell
      • datarama

      @datarama The radicalness of what I propose upthread is that Big Tech •can’t• destroy it, for the same reason that sequencers, no matter how good they are, no matter whether they can play things human never even could, still can’t replace the embodied pleasure of playing an instrument yourself.

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Thursday, 08-Feb-2024 09:44:41 JST Paul Cantrell Paul Cantrell
      in reply to

      @abucci I do not think the current generation of AI is going to fulfill the oligarchs’ wet dream of ruling the world.

      I •do• think it’s important for us to start thinking now about these questions about how concentration of power and wealth interacts with technological progress.

      In conversation about a year ago permalink
    • Embed this notice
      Anthony (abucci@buc.ci)'s status on Thursday, 08-Feb-2024 09:44:42 JST Anthony Anthony
      in reply to
      • Paul Cantrell
      • datarama
      @datarama@hachyderm.io @inthehands@hachyderm.io This article might be of interest in this regard: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4687740
      In conversation about a year ago permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Managing the Discontent of the Losers Redux: A Future of Authoritarian Neoliberalism or Social Capitalism?
        Neoliberalism eviscerated the value-sharing ethos of the post-war Golden Age (1945-73), seeking to maintain social cohesion in civil society by `managing the di
    • Embed this notice
      datarama (datarama@hachyderm.io)'s status on Thursday, 08-Feb-2024 09:44:44 JST datarama datarama
      in reply to
      • Paul Cantrell

      @abucci @inthehands I think the logical end point of where AI is currently heading (provided it keeps getting better) is that the neoliberal era *will* end. It will then be replaced by the neo-feudal era; a world of ultra-wealthy oligarchs presiding over hordes of desperate serfs competing for work where humans are still cheaper than robots.

      *Right fucking now*, think tanks are talking about how an AI can generate content for less energy than a human, given that humans need food and shelter.

      In conversation about a year ago permalink
    • Embed this notice
      Paul Cantrell (inthehands@hachyderm.io)'s status on Friday, 09-Feb-2024 07:33:25 JST Paul Cantrell Paul Cantrell
      • datarama

      @datarama @abucci Yeah, in the near term, I’m a lot more worried about the disruption caused by bad decisions prompted by AI hype / wishful thinking / misapplication / FOMO / panic than I am about the disruption caused by the tech itself actually being good at things.

      In conversation about a year ago permalink
    • Embed this notice
      datarama (datarama@hachyderm.io)'s status on Friday, 09-Feb-2024 07:39:30 JST datarama datarama
      in reply to
      • Paul Cantrell

      @abucci @inthehands I am a recovering academic myself! ;-)

      As I've said elsewhere: I'm not worried that the robot cultists will actually build an electronic god, or fuck it up and accidentally build an electronic satan. I'm worried about all the collateral damage from an infinite firehose of corporate money pumping into robot cultists who *think* they're building an electronic god.

      In conversation about a year ago permalink
    • Embed this notice
      Anthony (abucci@buc.ci)'s status on Friday, 09-Feb-2024 07:39:31 JST Anthony Anthony
      in reply to
      • Paul Cantrell
      • datarama
      @datarama@hachyderm.io @inthehands@hachyderm.io Oh I fully agree. I apologize, I should have finished my thought: having a bunch of people with power thinking that this is possible is dangerous. I don't believe that their fantasy world will ever be real, but I absolutely believe they wouldn't hesitate to hurt an enormous number of people in the process of trying to make it real.

      Oof, please don't get me started on academia...that's a week-long rant, minimum!
      In conversation about a year ago permalink
      Paul Cantrell repeated this.
    • Embed this notice
      datarama (datarama@hachyderm.io)'s status on Friday, 09-Feb-2024 07:39:32 JST datarama datarama
      in reply to
      • Paul Cantrell

      @abucci @inthehands I agree (and a lot of the publications on AI and society on arXiv read more like speculative fiction than like serious social science papers!).

      But it's terribly disturbing that actual academics are signing their names to that sort of thing.

      (And seeing Sam Altman talk about how he wants to "replace the median human" ... well, shit. I don't think they're anywhere near actually being *able* to do that, but we have an entire section of the tech industry *cheering* dystopia.)

      In conversation about a year ago permalink
    • Embed this notice
      Anthony (abucci@buc.ci)'s status on Friday, 09-Feb-2024 07:39:33 JST Anthony Anthony
      in reply to
      • Paul Cantrell
      • datarama
      I've read one of those "papers" and it was absurd and not credible, full of obvious reasoning errors. I fully believe that there are neoliberals and would-be barons who'd want nothing more than to have fully automated luxury capitalism, but it's a fantasy just as colonizing Mars is a fantasy.

      CC: @inthehands@hachyderm.io
      In conversation about a year ago permalink
    • Embed this notice
      datarama (datarama@hachyderm.io)'s status on Friday, 09-Feb-2024 07:39:34 JST datarama datarama
      in reply to
      • Paul Cantrell

      @abucci @inthehands As I said, *right now* there are respectable academics writing papers about how AI will allow "energy saving" because GPT-4 consumes less energy while writing a page of bullshit than a human being needs (because human beings require food and shelter, and take longer time).

      The thing *not* said in how this represents "saving" is chilling to consider.

      In conversation about a year ago permalink
    • Embed this notice
      Anthony (abucci@buc.ci)'s status on Friday, 09-Feb-2024 07:39:35 JST Anthony Anthony
      in reply to
      • Paul Cantrell
      @inthehands@hachyderm.io I don't recall if I shared this in thread yet but I think Dan McQuillan's thinking on this subject is good: https://danmcquillan.org/ai_thatcherism.html
      The real issue is not only that AI doesn't work as advertised, but the impact it will have before this becomes painfully obvious to everyone. AI is being used as form of 'shock doctrine', where the sense of urgency generated by an allegedly world-transforming technology is used as an opportunity to transform social systems without democratic debate.
      This shock doctrine process is clearly well underway.
      In conversation about a year ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: danmcquillan.org
        AI as Algorithmic Thatcherism
        from dan mcquillan

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.