Industry
Part of Telling whether a niche social network is still alive or just dormant
Niche social networks facts: how to verify four claims
Niche social networks facts: a method for checking claims about independence, privacy, community control and open-source code against available evidence.
To assess niche social networks facts, start with the same four claims. Small networks make them: we are independent, we are private, we are run by the community, we are open source. Each is checkable to a degree, none is checkable completely, and the degree is what a careful reader needs to know before deciding whether the claim is worth anything.
This page takes the four claims in turn: what each actually asserts when you press on it, which public evidence bears on it, where to find that evidence by name, how to read it, and where the checking stops. The method is the one used for claims made by a large service about itself, with smaller documents and more gaps.
What to take away
- Each claim decomposes into two or three narrower assertions, and the narrower ones are the ones with evidence.
- The evidence is the network's own documents, the public record of its operating entity (Companies House for a UK company, the state business register for a US one), and, where it exists, its published source code. Nothing else counts.
- Where the checking stops, write "unverified from outside" and stop. A small network's claims are not less honest than a large one's; they are just less documented.
"We are independent"
Pressed, this means three things: not owned by a larger company, not funded by one, and not dependent on one's infrastructure in a way that could end the network.
Ownership. Read the terms of service and privacy policy for the operating entity. If a company is named, its public registry record (the business registry for the jurisdiction the terms invoke) shows who its officers are and sometimes who its shareholders are. For a UK company that registry is Companies House, whose free company search shows the registered address, the date of incorporation and current and resigned officers. For a US company it is the business entity search of the Secretary of State or Division of Corporations in the state of incorporation, often Delaware. If no entity is named, the network is run by an individual or an informal group, and independence is true in the trivial sense that there is nothing to be owned. Record which.
Funding. Look for a funding page, a donations page, a sponsor list, or a statement of how bills are paid. Small networks often take member money through Open Collective, Liberapay or Patreon; an Open Collective page in particular shows income and expenses publicly, which is the closest thing to accounts a volunteer-run network will publish. Where the network has taken outside money, it will usually say so somewhere, because investors and sponsors like to be named. Silence is not evidence of independence; it is absence of evidence, and the entry says "funding not stated".
Infrastructure dependence. The network runs on someone's hosting and uses someone's services for mail, storage, and payments. Whether any of those could end the network is rarely stated. The most that can be checked from outside is whether the network has said anything about it, and the honest field is usually "not stated".
The checking stops at the registry and the network's own statements. It does not extend to investigating the people involved, and it should not.
"We are private"
Pressed, this means: the operator collects little, shares little, and what members post is not visible beyond the intended audience.
Collection. The privacy policy lists what is collected. Read it for the categories and the purposes, and quote them. A short policy is not a private policy; a short policy is often one that has not been written carefully. Look for what happens to a deleted account and what is retained afterwards.
Sharing. The same policy names who receives data and why. "Service providers" and "partners" are categories to note; a policy that names none has either no sharing or no policy.
Visibility. Test it. Make an account, post something distinctive, and look for it logged out and in a web search a week later, which tests whether search engine indexing reaches material members assume is private. Search the exact phrase in quotation marks in Google and in Bing, and add the site: operator with the network's domain to limit the results to that network. Then look at what the network's own search and directory expose about a member who has not opted into anything. This is the one part of the claim that a reader can settle personally, and it is worth doing before trusting any of the rest. The notes on what can be tested on a messaging service cover the equivalent tests for private messages.
The checking stops at the policy and the visibility test. What the operator actually does with the data it holds is unverifiable from outside, for a small network exactly as for a large one.
"We are run by the community"
Pressed, this means: decisions about rules and direction are made by members, and there is a stated way that happens.
Governance documents. Look for a page describing how moderators are chosen, how rules change, and how disputes are settled. A network that is genuinely community-run will have written this down, because a community needs it in writing to function. A network that has not written it down is run by whoever holds the server credentials, whatever the about page says.
Visible process. Look for a public record of a decision being made: a vote, a discussion thread that ended in a rule change, an announcement that cites the process. One instance of the process being used is worth more than a page describing it.
The last resort. Whoever controls the domain, the hosting account, and the database is the last word on any dispute, and no governance document changes that. The honest entry records both the stated process and the fact that the operator retains final control, because both are true. Federation changes the shape of this without removing it: on a network built on ActivityPub, the W3C's decentralized social networking protocol, each server's operator holds that last word for the accounts on that server, and members can leave for another server rather than appeal.
"We are open source"
Pressed, this means: the code that runs the network is published under a license that permits inspection and reuse, and the published code is what is actually running.
The repository. Find it, usually on GitHub, GitLab or Codeberg, read the license, and note whether releases are tagged and dated in version control. Look for a license approved by the Open Source Initiative: the GNU AGPL, the GNU GPL, the MIT License and the Apache License 2.0 are the ones you will meet most. The AGPL matters most for a network, because it requires the operator of a modified server to offer that modified source to the people using it over the network. An unlicensed repository is published but not open; a repository with no releases in a long time is open but possibly abandoned.
The match. Whether the running network is the published code is hard to check and rarely stated. Some software exposes a version identifier; where it does, compare it to the repository. Mastodon, for example, is published under the AGPLv3, and a Mastodon server reports its software version through its public instance information, which can be compared with the tagged releases in the Mastodon repository. Where software does not expose a version, the entry says "version correspondence not verifiable". Deployment often includes configuration and additions that are not in the repository, and that is normal, but it means "open source" describes the starting material rather than the running thing.
What open source does not mean. It does not mean the data is exportable, the network is federated, or the operator is accountable. It means the code can be read. The decentralized networks overview covers why architecture and governance are separate questions.
The shape of the record
| Claim | Narrow assertions | Evidence found | Result |
|---|---|---|---|
| Independent | Ownership, funding, infrastructure | Registry record; funding page or its absence; nothing on infrastructure | Partly supported; funding not stated |
| Private | Collection, sharing, visibility | Policy sections quoted; visibility test with dates | Supported on visibility; policy quoted; practice unverifiable |
| Community-run | Governance documents, visible process, last resort | Documents present or absent; one example or none | As found |
| Open source | License, releases, correspondence | Repository, license, release dates; version match or not | As found |
Four rows, filled honestly, are the whole of what an outsider can say. For each row, note the instrument used: the Companies House or state register entry, the funding page, the dated search results, the governance page, the repository and its license file. They will not tell a reader whether the network is good, or whether it will exist next year. The niche social networks overview covers how to judge whether a small network is alive; this page is about whether what it says about itself holds up.
Common questions
Is a small network's claim less trustworthy than a large one's?
Less documented, which is different. A large operator has lawyers who make policies precise and filings that make ownership public. A small one has an about page. The claims are equally checkable in kind and unequally checkable in depth, and the entry should say how deep it got.
The operator answered my questions directly. Does that count?
As a statement by the operator, dated, quoted, and marked as such. It is better than silence and it is not a document. If it contradicts a published page, record both.
What if the network is run by one person who says so plainly?
Then "independent" and "community-run" resolve immediately and honestly: it is that person's, and they say so. That is a clearer position than most, and worth recording without penalty.
Should the record name the people involved?
It should name the operating entity where one exists and where the network itself names it. It should not go looking for individuals beyond what the network publishes about itself. The purpose is to check a claim, not to profile anyone.
