From a posted need to completed help
HelpBLESS says on its website that people can post needs for free and that a human reviews every need before publication. Posts have no expiration date, and users do not have to reach a funding target. The platform also says 14 of its 16 categories of help require no payment, with examples including an hour of childcare, transportation to an appointment, a second opinion on a lease and a working laptop.
The DEV Community account focuses on the information people need to turn those posts into workable arrangements. A request should explain the task, when it needs to happen, the general location and what would count as completion. Asking for a ride to a Tuesday morning medical appointment, two hours of box-moving on Saturday or a ladder for a weekend repair gives a potential helper something concrete to assess.
Brief form fields for the task, deadline and expected effort can reduce the back-and-forth needed to arrange help. Offers need comparable detail: relevant skills, availability, travel limits and the amount of help someone can commit to. A two-hour Saturday commitment, a limit of a few miles or an offer of one car trip sets expectations for both participants.
The process also needs a way to confirm an arrangement, record that a request has been fulfilled and cancel without difficulty when circumstances change. The account warns that requests left unanswered and offers that never materialize undermine confidence in the board.
Separating public requests from private arrangements
The account recommends drawing a clear line between information needed to assess a request and information needed to carry it out. Public posts should not expose home addresses, phone numbers, email addresses or sensitive medical and financial details. Information about children and other vulnerable people also requires protection.
A neighborhood can provide enough location context for an initial decision; an exact address usually does not belong in that public exchange. Contact information and precise meeting arrangements should be shared privately, only after a match and only with the participant involved. In-platform messages or a mediated contact process can support that separation where available.
Privacy protections should extend to the form prompts and default visibility settings, as well as options to edit or delete a fulfilled request. Urgent appeals warrant particular care because people under pressure may disclose more than is safe.
HelpBLESS says identity verification is optional. Members can add photo, ID and address badges, but the platform says each badge represents only what it actually checked.
A broader set of security recommendations appears in "Securing Mutual Aid," an October 2025 white paper published by the UC Berkeley Center for Long-Term Cybersecurity and produced with Fight for the Future. Drawing on cybersecurity risk assessments and interviews with six mutual-aid organizations, it sets out practices and design principles for secure platforms.
The report recommends collecting as little user data as possible, neither selling nor sharing it, and supporting pseudonymous or role-based accounts. Its recommendations also include app-based multi-factor authentication as the default, zero-knowledge encryption, open-source software that can be audited, and adherence to WCAG accessibility guidelines.
Rules, reports and the limits of automation
For moderation, the HelpBLESS account emphasizes rules that explain both prohibited conduct and the consequences of violations. Those rules should address scams, impersonation, recurring off-topic posts, unverifiable fundraising claims, and requests for money or personal information. Even on a small board, the handling of a few reports can establish expectations for everyone else.
Someone who reports a post should receive a visible acknowledgment, including when a review is still pending. Comparable cases should receive consistent treatment, and users need a straightforward way to appeal mistakes. Automated tools can flag suspicious links, repeated posts or language associated with scams, but sensitive decisions that depend on context should receive human review, with a brief explanation recorded.
The Buy Nothing Project offers one published example of response standards. The hyperlocal gifting network says its support team reviews reports about posts or users and takes action within 24 hours. It also states a zero-tolerance policy for abuse, with violating content and users removed within 24 hours.
The network's scale was already substantial by September 2020. Vox reported then that Buy Nothing, founded in 2013, had more than 1.2 million participants in 25 countries and described it as Facebook's largest network of hyperlocal, volunteer-run gifting groups.
That same Vox report documented a pandemic-era dispute in a Brooklyn Buy Nothing group. Moderators determined which items qualified as "essential," deleted a request for a folding cart to make mutual-aid deliveries and turned off comments. Some members subsequently formed a separate group, Crown Heights Share.
Fees and access to payment services
For gifts involving money, HelpBLESS says it discloses its platform fee in advance. According to the site, the remaining amount goes to the person requesting help, without hidden charges.
The Berkeley report identifies a separate financial risk: payment-service deplatforming. Services such as PayPal and Venmo can temporarily or permanently ban accounts or restrict their functions, a risk the report describes as major for mutual-aid groups. It recommends giving platforms multiple payment routes so funds are not dependent on a single method.
Preserving dignity and measuring follow-through
The DEV Community account also argues against public rankings and language that categorizes people by how desperate they appear. Requesters should retain control over how much detail they disclose, so asking for assistance does not require unnecessary public exposure.
For assessing a board's health, it recommends looking beyond posting volume to completed matches, response times, the proportion of offers that result in help and the time needed to resolve reports.
