Neil Chudleigh launches GET Together with the wrong HTTP method
GET Together is a public feed built around a method defined as safe and read-only: the former PartnerStack CTO adds ownership, privacy and moderation controls to the experiment.
By RuntimeWire Staff · Published
Primary source: GET Together
Why it matters
GET Together turns a protocol joke into a compact lesson: even a social feed with a handful of endpoints immediately needs ownership, retries, privacy rules, abuse controls and moderation.
Neil Chudleigh (@neilsuperduper) launched GET Together, a public social network where publishing a message requires an HTTP GET request, on September 7th. The original Hacker News launch submission describes the same premise: users do not need POST to post. GET is normally used to retrieve data; GET Together uses it to write posts, add hearts, delete messages and build reply threads.
Chudleigh is a former PartnerStack CTO whose public profiles also link him to Superwhisper, an AI voice-to-text application, and Homerow, a keyboard navigation tool for macOS. He co-founded PartnerStack with Bryn Jones, Jonathan Mendes and Luke Swanek and took the SaaS partnerships platform through Y Combinator's Summer 2015 batch. PartnerStack raised a $29 million Series B in 2021, led by 3L Capital with participation from Whitecap Venture Partners, HarbourVest and existing investor RRE Ventures.
AppDirect acquired PartnerStack on April 14th, 2026.
The public-profile links do not establish Chudleigh's ownership or financial interest in Superwhisper or Homerow. Crunchbase lists his studies as mechanical engineering and computer science at Western University. GET Together fits that builder profile: one technical rule becomes the product, then the implementation follows the rule farther than good judgment normally permits.
The protocol violation is the interface
GET Together has no conventional account setup or API keys. A user supplies a nickname and up to 280 characters through the query string:
curl -G 'https://gettogether.dev/post' \
--data-urlencode 'name=your_nickname' \
--data-urlencode 'text=hello everyone'
The server returns JSON with a post ID. Chudleigh included equivalent examples for Python, JavaScript, Go and Rust, making the posting interface usable from a terminal or a few lines of code.
The rest of GET Together follows the same constraint. /feed returns posts as JSON. /heart adds or removes a reaction. /delete removes a post when the request carries the correct owner cookie. Replies are created by calling /post with a parent ID. Every action uses GET.
That design cuts the product down to an unusually legible set of primitives. Names can contain two to 20 letters, numbers or underscores, and they are neither unique nor verified. Cookies are optional for publishing. Users who retain the gt_session cookie can later delete their posts. A caller can also supply a UUID, allowing a failed request to be retried without creating a duplicate.
The retry mechanism addresses an application problem that the HTTP method choice creates. The HTTP semantics standard defines GET as a safe, essentially read-only method for requesting a current representation. GET Together's documented endpoints instead use GET to change server state whenever someone publishes, reacts or deletes.
That mismatch is the experiment's main technical hazard. GET Together makes the method itself an unreliable guide to what the request will do.
The message is part of the URL
GET Together's sharpest tradeoff is visible before a request reaches the server: the nickname and message are carried in the URL. The homepage warns users to keep private information out of posts because the text is public and appears in the request URL.
That warning matters beyond the public feed. URLs can surface in browser histories, server logs, proxy systems and analytics tooling. MDN's web privacy guidance advises developers against placing sensitive information in URLs because URL data can also travel through referral information. GET Together discloses the constraint plainly; the product depends on users understanding it before pasting anything personal into a command line.
The design also removes the usual friction between composing a message and publishing it. There is no account recovery, profile setup or identity check. A valid request is enough. That makes GET Together approachable for developers and creates immediate moderation pressure for a public service.
The closest functional comparisons are account-based short-form networks, including Bluesky and Mastodon. Bluesky is built around the AT Protocol, while Mastodon distributes communities across independently operated servers. GET Together documents no comparable federation, portability or persistent identity layer. It is a chronological public feed reduced to posts, replies, hearts and deletion.
Even the smallest feed needs controls
GET Together answers the abuse problem with a posting interval and automated checks. The product homepage limits users to one post every 10 seconds. No supported hourly or daily posting limits are disclosed in the supplied homepage material.
The homepage says new posts and names are checked for English profanity and crypto content. Crypto, Bitcoin, memecoins and token promotion are prohibited. Reports trigger an automated abuse review; clear violations are hidden, while reporting alone does not remove a post. The service also publishes a separate rules page.
Those controls carry much of the product story. Chudleigh reduced publishing to a URL, yet the social layer still required ownership cookies, deletion behavior, nested replies, reporting, identity disclaimers, automated checks and rate limiting. The protocol joke made the posting interface smaller while leaving the work of operating a public conversation intact.
GET Together arrives as a compact project from an engineer whose previous work includes venture-backed B2B infrastructure. Its ambitions are narrower: a chronological public feed, a handful of endpoints and a premise developers can understand immediately. No reliable usage count is available because the supplied snapshots displayed inconsistent post totals.
The one-line posting call is followed by the machinery that makes the experiment usable. That inventory gives GET Together weight beyond the HTTP gag. Chudleigh has produced a small, inspectable demonstration of how quickly a social product accumulates obligations, even when its feature list ends at posts, replies and hearts.