GET together is a deliberately minimal social network that swaps the usual write-path for something far less conventional: posting happens through HTTP GET requests. The project’s landing page says it is "a social network with no POSTs," and its documentation leans into that design choice. In this system, a message is created by sending a GET request to the service, not by submitting a traditional form or API write call.
The site describes the model in blunt terms. Posts are public, the newest entries appear first, and that is essentially the product. The idea is not to simulate a large modern platform with timelines, recommendation layers, or private messaging. Instead, it exposes a tiny, almost schematic social feed whose mechanics are visible in the URL. The service appears to be designed as much to demonstrate protocol behavior as to function as a conventional network.
The documentation says a successful request returns the new post’s ID. Users can set a name and text, and the service allows replies through a parent parameter. There is also a feed endpoint that can return the list of posts or the replies to a particular post. The page explains that deletion is possible for your own posts and that hearts can be added or removed using a GET request as well. Even the moderation logic is spelled out in the documentation, including a check for profanity and crypto-related promotion.
That combination makes the project feel like a live experiment in protocol design. HTTP GET is normally associated with safe, idempotent retrieval, while POST is the standard way to create or mutate content. GET together deliberately flips that assumption. The project’s own instructions note that if a user leaves out an ID, the server will create one, but for safe retries they can provide a UUID and reuse it with the same cookie. That detail is a reminder that once request semantics are altered, even simple user flows start to require careful thought.
The service also warns users about privacy. The post text is part of the URL, which means messages can be exposed in places where URLs are logged, shared, or cached. The page explicitly tells users not to include private information. It also says cookies are optional for posting but needed if someone wants to delete their own content later, with a session cookie used to authorize the action. That setup reflects a broader tradeoff in the design: making the system simple to inspect does not make it safe by default.
The social layer is intentionally light. Names are not unique or verified, and the page says there is no special protection against impersonation beyond the basic naming rules. That makes the service less a full-blown platform and more a proof-of-concept with live endpoints. It is easy to imagine the project as a teaching tool for developers thinking about HTTP semantics, caching behavior, or the consequences of making mutating actions look like retrieval.
As a product, GET together is almost comically austere. As a demonstration, that austerity is the point. It turns a common web rule into the structure of the entire application and then documents the side effects that follow. For anyone used to social apps that hide their machinery, it offers the opposite experience: the machinery is the product, and the public feed is only one consequence of it.
