No description
Find a file
2019-10-16 02:35:47 -04:00
docs eliminate need for js in various places 2019-10-13 22:59:02 -04:00
views add file 2019-10-13 23:00:53 -04:00
.hgtags
activity.go updated junk interface 2019-10-16 02:27:04 -04:00
avatar.go
bloat.go
database.go modestly better search, with parameters 2019-10-15 23:27:30 -04:00
deliverator.go delivery chan should buffer one 2019-10-16 02:35:47 -04:00
fun.go modestly better search, with parameters 2019-10-15 23:27:30 -04:00
go.mod updated junk interface 2019-10-16 02:27:04 -04:00
go.sum updated junk interface 2019-10-16 02:27:04 -04:00
hfcs.go convert to using library version of cache 2019-10-12 19:25:23 -04:00
honk.go some cleanups 2019-10-16 02:06:53 -04:00
hoot.go
LICENSE
Makefile
markitzero.go syntax highlighting because why not. go code or go home. 2019-10-10 00:40:29 -04:00
markitzero_test.go
README tighten up the README a bit 2019-10-15 15:57:18 -04:00
schema.sql
skulduggery.go
upgradedb.go set a dummy convoy for all blanks 2019-10-12 23:36:43 -04:00
util.go set a dummy convoy for all blanks 2019-10-12 23:36:43 -04:00
web.go some cleanups 2019-10-16 02:06:53 -04:00

honk

-- features

Take control of your honks.

An ActivityPub server focused on 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".

-- build

It should be sufficient to type make after unpacking a release.
You'll need a go compiler version 1.11 or later.

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: localhost:31337, /var/www/honk.sock, etc.)
servername: (public DNS name: honk.example.com)

Then run honk.
./honk

-- upgrade

cp honk.db backup.db
./honk upgrade
./honk

-- documentation

There is a more complete manual. This is just the README.