i understand your pain
overview - docs - downloads - files - changes - changes rss
honk ## features Take control of your honks and join the federation. An ActivityPub server with minimal setup and support costs. Spend more time using the software and less time operating it. No attention mining. No likes, no faves, no polls, no stars, no claps, no counts. Purple color scheme. Custom emus. Memes too. Avatars automatically assigned by the NSA. The button to submit a new honk says "it's gonna be honked". The honk mission is to work well if it's what you want. This does not imply the goal is to be what you want. Besides microblogging, honk might also server as the basis for a custom ActivityPub server, a sort of integrated federation framework. But you may need to get your hands dirty. ## build It should be sufficient to type make after unpacking a release. You'll need a go compiler version 1.18 or later. And libsqlite3. Even on a fast machine, building from source can take several seconds. Development sources: hg clone https://humungus.tedunangst.com/r/honk ## setup honk expects to be fronted by a TLS terminating reverse proxy. First, create the database. This will ask four questions. ./honk init username: (the username you want) password: (the password you want) listenaddr: (tcp or unix: 127.0.0.1:31337, /var/www/honk.sock, etc.) servername: (public DNS name: honk.example.com) Then run honk. ./honk ## upgrade old-honk backup `date +backup-%F` ./honk upgrade ./honk ## documentation There is a more complete incomplete manual. This is just the README. ## guidelines One honk per day, or call it an "eighth-tenth" honk. If your honk frequency changes, so will the number of honks. The honk should be short, but not so short that you cannot identify it. The honk is an animal sign of respect and should be accompanied by a friendly greeting or a nod. The honk should be done from a seat and in a safe area. It is considered rude to make noise in a place of business. The honk may be made on public property only when the person doing the honk has the permission of the owner of that property. ## disclaimer Do not use honk to contact emergency services.
recent changes
| 1917:3f628b52fa27
on 2024-04-06 22:13:01 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
Tagged: tip
fixed! |
| 1916:c156daa8d779
on 2024-04-06 22:12:48 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
only fetch once for a search |
| 1915:f5e84e7fe357
on 2024-04-06 22:01:16 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
additional processing only for some activities |
| 1914:8e2437c1123d
on 2024-04-06 21:47:25 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
make a common.js file for some functions on all pages |
| 1913:7a88927cfe6c
on 2024-04-03 02:05:46 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
try to update the docs |
| 1912:69ceb1c33887
on 2024-04-03 01:52:22 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
make it optional to collect forwards |
| 1911:167f6b27f3a1
on 2024-04-03 00:35:38 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
backup code needs some more bludgeoning |
| 1910:f381c9b1afd0
on 2024-04-03 00:15:36 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
confine the madness to backup code, and hardlink attachments |
| 1909:88385ed9abbb
on 2024-04-02 08:46:10 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
fix export to work with data stores |
| 1908:633c76d8ca94
on 2024-04-02 08:39:48 -0400 EDT by Ted Unangst <tedu@tedunangst.com>
fix backup to work with various data stores |