The web I want vs. the one we have

Textcasting, WordPress, and ActivityPub

  • The blog’s “textcasting” idea is interpreted as syndicating text from a home base (e.g., a blog) out to multiple social platforms.
  • Commenters note this already exists via ActivityPub and tools that connect WordPress to the fediverse.
  • One plugin is highlighted as enabling any WordPress site to act as a social node; some think this should be in WordPress core.
  • Vision: your own site as your social profile, publishing once and syndicating everywhere (POSSE-style), while you retain control of source content.
  • Some see this as basically a more open, self-hosted version of cross-posting tools; unclear what is fundamentally new beyond better integration.

Open Web vs. Siloed Communities

  • Several dislike “web elegies,” arguing the web still connects like-minded people and that the right response is to keep building things.
  • Others counter that many independent forums, mailing lists, and site-centered communities have died or shrunk; most activity moved into silos (Discord, Reddit, etc.).
  • Discord is heavily debated:
    • Pro: ad-light, simple, good for real communities, keeps out bots/advertisers, comparable to updated AIM/IRC.
    • Con: proprietary, walled, requires registration/phone, poor for durable, searchable knowledge; locks helpful info away from the web and newcomers.
  • Hosting independent forums is seen as harder now due to costs, scraping, spam, moderation burden, and legal risk.

Nostalgia, Community Design, and Generations

  • Some note every generation thinks “their” internet era was the golden age (similar to recurring jokes about TV shows).
  • A few reminisce about deeper past interactions (email, forums, IRC) versus today’s shallow, fragmented engagement.
  • HN is cited as deliberately designed for content quality over relationship-building (no avatars, limited UI “sugar”).

Technical vs. Non-Technical Leadership

  • The blog’s frustration with non-technical gatekeepers sparks debate:
    • Some argue leaders don’t need to know implementation details (e.g., time/space tradeoffs), only business outcomes.
    • Others say ignorance of core technical realities leads to bad decisions and “Boeing-style” failures.
  • There’s disagreement over whether technical people inherently struggle to understand non-technical users; some call that an unfair stereotype.

AI Summaries and Reading Habits

  • One commenter uses ChatGPT-style summaries to triage what to read, likening it to an abstract.
  • Others prefer traditional skimming and worry that offloading this “mundane” cognition is counterproductive or intellectually dulling.