alemi
7f996aa2c1
basically relays send us a lot of announce activities to share posts but we don't care about those activities: it's db bloat and it increases the shares count. keep a table keeping track of followed relays and lazily skip activities by them, just fetch. IMPORTANT relays are only loaded at startup, so if you subscribe to a new relay restart your server once it accepts!!! |
||
|---|---|---|
| apb | ||
| src | ||
| web | ||
| .editorconfig | ||
| .gitignore | ||
| .rustfmt.toml | ||
| .tci | ||
| Cargo.toml | ||
| README.md | ||
μpub
micro social network, federated
μpub aims to be a private, lightweight, modular and secure ActivityPub server
μpub is currently being developed and can do most basic things, like posting notes, liking things, following others, deliveries and browsing
all interactions must happen with ActivityPub's client-server methods (basically POST your activities to your outbox), and there's a simple frontend
a test instance is usually available at feditest.alemi.dev
upub's stock frontend is also being developed and can be viewed usually at feditest.alemi.dev/web
about security
most activitypub implementations don't really validate fetches: knowing an activity/object id will allow anyone to resolve it on most fedi software. this is of course unacceptable: "security through obscurity" just doesn't work
μpub correctly and rigorously implements and enforces access control on each object based on its addressing
most instances will have "authorized fetch" which kind of makes the issue less bad, but anyone can host an actor, have any server download their pubkey and then start fetching
μpub may be considered to have "authorized fetch" permanently on, except it depends on each post:
- all posts marked public (meaning, addressed to "https://www.w3.org/ns/activitystreams#Public"), will be fetchable without any authorization
- all posts not public will require explicit addressing and authentication: for example if post A is addressed to example.net/actor
- anonymous fetchers will receive 404 on GET /posts/A
- local users must authenticate and will be given said post only if it's addressed to them
- remote servers will be given access to all posts from any of their users once they have authenticated themselves (with http signing)
note that followers get expanded: addressing to example.net/actor/followers will address to anyone following actor that the server knows of, at that time
contributing
all help is extremely welcome! if my cgit looks too scary there's a github mirror you can open issues or PRs on. get in touch with me (fedi is fine, but a mail works too), i'd be thrilled to showcase the project to you!
progress
- barebone actors
- barebone activities and objects
- activitystreams/activitypub compliance (well mostly)
- process barebones feeds
- process barebones inbox
- process barebones outbox
- http signatures
- privacy, targets, scopes
- simple web client
- announce (boosts)
- threads
- editing
- searching
- media
- user fields
- mastodon api
- hashtags, discovery
- polls
- lists
- more optimized database schema
what about the name?
μpub (or simply upub) means "micro-pub", but could also be read "upub", "you-pub" or "mu-pub"
frontend
μpub aims to be compatible with multiple frontends via the mastodon api, but a simple custom ui is also being worked on
