user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
385e51723bddca2156bf9f7781fd9719bd5b9162 blob 949 bytes (raw)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
marketing guide for public-inbox

TL; DR: Don't market this.

If you must: don't be pushy and annoying about it.  Slow down.
Please no superlatives, hype or BS.

It's online and public, so it already markets itself.
Being informative is not a bad thing, being insistent is.

Chances are, you're preaching to the choir; or the folks you're
trying to convince are not ready for everything our project
represents to the resistance against centralization.

Baby steps...

There's never a need for anybody to migrate to using our
software, or to use any particular instance of it.  It's
designed to coexist with other mail archives, especially
other installations of public-inbox.

Most importantly, we take victories even when our software
doesn't get adopted.  Freedom from lock-in is more important
than the adoption of any software.

Every time somebody recognizes and rejects various forms of
lock-in and centralization is already a victory for us.
debug log:

solving 385e517 ...
found 385e517 in https://80x24.org/public-inbox.git

Code repositories for project(s) associated with this inbox:

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).