mirror of
https://git.sr.ht/~tsileo/microblog.pub
synced 2024-07-02 08:16:53 +00:00
68884d9afa
The sensitive text feature was implemented with <label> and hidden
checkbox <input> elements. There were two issues with this
implementation:
1. The user couldn't navigate to the "show/hide more" button using
keyboard.
2. The label indicates two actions at the same time ("show/hide more"),
making it unclear what the function of the checkbox was and what the
current show/collapse state was.
As it is generally preferrable to use built-in HTML elements for the
best semantic, this commit moves to use the <details> and <summary>
elements for the sensitive text feature. The browser will open/collapse
the content in <details> automatically when the user clicks on the
<summary>, and keyboard navigation support is built-in.
This commit also changes the button to display "show more" or "show
less" depending on the state for visual clarity. This button is hidden
from the accessibility tree using `aria-label="false"`, as the <details>
element already exposes its state to the tree and we want to avoid
duplicated information.
A few caveats:
* The "show/hide sensitive content" button for sensitive attachments
hasn't been changed yet as I'd like to get more feedback about the new
implementation.
* As the summary/content warning text itself is also part of the
<summary> tag, the user can now also click on them to toggle the
visibility of the sensitive text. This may not be desirable as the
current interface does not make it clear that this could happen; the
user may try to select some text from the summary and be surprised
by the sensitive text being expanded. One way to improve this would
be to add an event listener to the summary text and call
`preventDefault`, but this would introduce JavaScript code.
|
||
|---|---|---|
| alembic | ||
| app | ||
| data | ||
| docs | ||
| misc | ||
| scripts | ||
| tests | ||
| .build.yml | ||
| .dockerignore | ||
| .flake8 | ||
| .gitignore | ||
| alembic.ini | ||
| AUTHORS | ||
| boussole.json | ||
| docker-compose.yml | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| poetry.lock | ||
| pyproject.toml | ||
| README.md | ||
| tasks.py | ||
microblog.pub
A self-hosted, single-user, ActivityPub powered microblog.
Instances in the wild:
- microblog.pub (follow to get updated about the project)
- hexa.ninja (theme customization example)
- testing.microblog.pub
There are still some rough edges, but the server is mostly functional.
Features
- Implements the ActivityPub server to server protocol
- Federate with all the other popular ActivityPub servers like Pleroma, PixelFed, PeerTube, Mastodon...
- Consume most of the content types available (notes, articles, videos, pictures...)
- Exposes your ActivityPub profile as a minimalist microblog
- Author notes in Markdown, with code highlighting support
- Dedicated section for articles/blog posts (enabled when the first article is posted)
- Lightweight
- Uses SQLite, and Python 3.10+
- Can be deployed on small VPS
- Privacy-aware
- EXIF metadata (like GPS location) are stripped before storage
- Every media is proxied through the server
- Strict access control for your outbox enforced via HTTP signature
- No Javascript
- The UI is pure HTML/CSS
- Except tiny bits of hand-written JS in the note composer to insert emoji and add alt text to images
- IndieWeb citizen
- IndieAuth support (OAuth2 extension)
- Microformats everywhere
- Micropub support
- Sends and processes Webmentions
- RSS/Atom/JSON feed
- Easy to backup
- Everything is stored in the
data/directory: config, uploads, secrets and the SQLite database.
- Everything is stored in the
Getting started
Check out the online documentation.
Credits
- Emoji from Twemoji
- Awesome custom goose emoji from @pamela@bsd.network
Contributing
All the development takes place on sourcehut, GitHub is only used as a mirror:
Contributions are welcomed, check out the contributing section of the documentation for more details.
License
The project is licensed under the GNU AGPL v3 LICENSE (see the LICENSE file).