今日已更新 222 条资讯 | 累计 40667 条内容
关于我们

标签:#media

找到 282 篇相关文章

AI 资讯

How the Nostr journey is going for me?

A few years ago, I discovered the Nostr protocol 1 thanks to Jack (Jack Dorsey) 2 . I've been using it actively ever since. I already had an interest in distributed social networks for years. I tried ActivityPub 3 for a while, but something just didn't click. Around that time, Jack started ATProto 4 within Twitter, but something felt off there too. I hadn't even bothered trying the methods that came before those anyway. It always bothered me—and many others, of course—that the internet became so centralized when the web is distributed by nature. The main reason for this was social media platforms. The trend that started with guestbooks evolved into forums, then to Friendfeed-like walls, MySpace-like platforms, and eventually Facebook and Twitter. The internet, which had a much more distributed structure with blogs prior to Facebook and Twitter, suddenly started to centralize. Due to the maintenance costs of distributed structures and unsettled systems, humanity took the easy way out and chose centralization, as always. Facebook and Twitter grew steadily, and many other platforms alongside them transformed into centralized hubs using the exact same playbook. One of the things people realized too late was that centralized power always possesses the ability to manipulate, a fact that eventually came to light through the Facebook and Twitter lawsuits and similar cases over time. Moreover, there was no such thing as account ownership in any of these centralized systems; we were essentially no different from non-paying tenants (or tenants paying with our data). As time passed, we saw what happened when the landlords started evicting people. Nowadays, even just posting anti-government content can get you kicked out of these centralized platforms in an instant, and you have absolutely no ownership rights over your data or anything else. We've actually been living in a crappy system for a long time, and this system is still going on. From the era I caught onto, ActivityPub w

2026-08-21 原文 →
AI 资讯

How to Automate Scheduled X Posts with Codex and xurl

Most social-media automation tutorials stop at “call the API on a cron job.” That works, but it leaves the hard questions unanswered. Which account is the automation using? How does it avoid posting the same story twice? What happens when an API request times out after X has already accepted the post? And where should an AI agent’s editorial freedom end? I recently built a scheduled X publishing workflow with Codex and xurl , the official command-line client for the X API. The result is not just a timer attached to an AI prompt. It is a small publishing system with four distinct layers: An X developer application with read-and-write user authentication. xurl , which stores the credentials and communicates with the X API. A fixed-account Codex skill that verifies the identity before every write. A Codex scheduled task that researches, checks history, drafts, and publishes. That separation is the important part. Codex can make editorial decisions, but it cannot casually choose an account or improvise the publishing command. The skill owns the deterministic write boundary, while the scheduled task owns timing and editorial policy. In this article, I’ll show you how to build the same architecture. X developer settings, API packages, Codex features, and command-line options can change. The workflow below was verified in August 2026, but you should check the current upstream documentation before using it in production. What You Will Need Before starting, you will need: Codex on a Mac with access to Scheduled tasks. An X developer account and an application with read-and-write permissions. Homebrew. A dedicated or clearly identified X account for the automation. A local project containing the source material or editorial context the agent should use. You should also decide what the automation is allowed to publish before you give it access to an account. A good editorial policy is specific enough to reject a story, not merely broad enough to describe a topic. For example,

2026-08-17 原文 →