Oneric/akkoma
1
0
Fork 0
forked from AkkomaGang/akkoma
Code Pull requests Activity
Working copy for sending patches. May be force-pushed any time.
15634 commits 16 branches 84 tags 297 MiB
Elixir 96.8%
HTML 2.3%
CSS 0.5%
Shell 0.3%
Find a file
Exact
Oneric bc84698087 [TESTING] dbsearch: actually rank search results 
Until now we always sorted search matches by id (basically: most recent)
and grabbed the first couple. However, if no special input modifiers are
used websearch_to_tsquery creates a pretty loose search vector and the
most recent matches might be far from the most relevant matches.

Thus rank results by their relevancy instead. Normalisation mode 16
takes the amount of unique words of a post into account since a
post with 500 unique words matching a 5 word query is likely less
relevant than a post consisting entirely out of the 5 queried words.

Let’s hope this improves on our notoriously bad search.

The tradeoff here being more costly queries. ON a simplified mockup
query without any filtering or joins with activities, the planner’s
cost estimate didn’ŧ change much, but measured wall clock time for
a single query increased from ~1.7ms to 2.3ms.

As far as I can tell, the cost of ts_rank(_cd) was never discussed
before. The original version 9f0a2a714b
didn’t sort at all and there’s no associated discussion. Later it was
sorted by date 1dd2c8163f but quickly
changed to sorting by id ff5e957476
(which isn’t to different with old sequential ids and current FlakeIDs).
This was carried forward until eventually being removed in
817c66bc3e prob because pagination sorts
anyway.

For now RUM results continue to be ranked solely by recencey
as it did since its introduction in
  01c45ddc9e and
  f1e67bdc31
It is possible to make it use an efficient relevancy-based ranking,
but this requires changes to its index which is beyond the scope of
this commit.

TODO: not sure how much the normalisation helps or if a non-log
  or non-unique word normalisation would be better.
2024-05-04 00:12:59 +02:00
.gitea/issue_template Update '.gitea/issue_template/feat.yml' 2022-12-12 04:26:43 +00:00
.woodpecker Add test suite for elixir1.16 2024-04-12 19:13:33 +01:00
benchmarks Merge branch 'benchmark-fixes' into 'develop' 2021-12-09 15:38:26 +00:00
ci CI: Use own package as base 2021-12-26 18:05:42 +01:00
config exiftool: make stripped tags configurable 2024-04-26 18:57:24 +02:00
docker-resources Update docker compose commands to Compose V2 2023-06-18 01:37:40 -04:00
docs Raise minimum PostgreSQL version to 11 2024-05-02 03:57:19 +02:00
installation Change nginx cache size to 1 GiB 2024-04-26 01:43:44 -04:00
lib [TESTING] dbsearch: actually rank search results 2024-05-04 00:12:59 +02:00
priv Update translation files 2024-04-26 17:49:40 +00:00
rel Disable busy waits in the default OTP vm.args configuration. 2024-02-17 13:21:56 +01:00
restarter fix_flaky_transfer_task_test.exs (#237) 2022-11-01 14:31:29 +00:00
scripts document prometheus 2022-12-16 10:24:36 +00:00
test Raise minimum PostgreSQL version to 11 2024-05-02 03:57:19 +02:00
uploads fix issues with the uploads directory 2019-04-28 06:43:00 +02:00
.buildpacks CI: Add auto-deployment via dokku. 2019-05-31 10:55:35 +02:00
.credo.exs Move Consistency.FileLocation to ./test 2020-10-13 19:57:45 +02:00
.dockerignore Docker builds (#231) 2022-10-16 19:25:54 +00:00
.formatter.exs Migrate to phoenix 1.7 (#626) 2023-08-15 10:22:18 +00:00
.gitattributes Don't treat js/css as binary in git anymore 2022-12-23 18:03:14 +00:00
.gitignore Add docker override file to docs and gitignore 2023-08-07 13:09:04 -04:00
.mailmap Add myself to .mailmap 2021-02-15 13:19:44 +03:00
AGPL-3 LICENSE → AGPL-3 2019-04-01 00:31:21 +02:00
CC-BY-4.0 Add a copy of CC-BY-4.0 to the repo 2020-09-06 11:38:38 +03:00
CC-BY-SA-4.0 CC-BY-SA-4.0: Add a copy of the CC-BY-SA-4.0 license 2019-04-01 00:30:21 +02:00
CHANGELOG.md [TESTING] dbsearch: actually rank search results 2024-05-04 00:12:59 +02:00
CODE_OF_CONDUCT.md add code of conduct (#129) 2022-08-03 10:55:11 +00:00
COPYING Remove reference to city.jpg in COPYING 2022-11-25 07:29:50 +00:00
docker-compose.yml Merge pull request 'Add docker override file to docs and gitignore' (#621) from norm/akkoma:docker-compose-override into develop 2024-04-12 18:50:25 +00:00
docker-entrypoint.sh Docker builds (#231) 2022-10-16 19:25:54 +00:00
Dockerfile Bump builds to OTP26 2023-08-09 14:39:28 +01:00
mix.exs version bump with translations 2024-04-27 15:10:52 +01:00
mix.lock Enable oban job uniqueness 2024-04-16 02:53:24 +01:00
README.md Add YunoHost to installation guides 2023-04-03 11:22:53 +02:00
SECURITY.md Update notes on security exploit handling 2024-03-04 17:50:19 +01:00
SIGNING_KEY.pub 2022.09 stable release chores (#206) 2022-09-10 14:44:17 +00:00

README.md

akkoma

a smallish microblogging platform, aka the cooler pleroma

English OK 日本語OK

About

This is a fork of Pleroma, which is a microblogging server software that can federate (= exchange messages with) other servers that support ActivityPub. What that means is that you can host a server for yourself or your friends and stay in control of your online identity, but still exchange messages with people on larger servers. Akkoma will federate with all servers that implement ActivityPub, like Friendica, GNU Social, Hubzilla, Mastodon, Misskey, Peertube, and Pixelfed.

Akkoma is written in Elixir and uses PostgreSQL for data storage.

For clients it supports the Mastodon client API with Pleroma extensions (see the API section on https://docs.akkoma.dev/stable/).

Differences with Pleroma

Akkoma is a faster-paced fork, it has a varied and potentially experimental feature set tailored specifically to the corner of the fediverse inhabited by the project creator and contributors.

This should not be considered a one-for-one match with pleroma; it is more opinionated in many ways, and has a smaller community (which is good or bad depending on your view)

For example, Akkoma has:

  • Custom Emoji reactions (compatible with misskey)
  • Misskey-flavoured markdown support
  • Elasticsearch and Meilisearch support for search
  • Mastodon frontend (Glitch-Soc and Fedibird flavours) support
  • Automatic post translation via DeepL or LibreTranslate
  • A multitude of heavy modifications to the Pleroma Frontend (Pleroma-FE)
  • The "bubble" concept, in which instance administrators can choose closely-related instances to make a "community of communities", so to say

And takes a more opinionated stance on issues like Domain blocks, which are enforced far more on Akkoma.

Take a look at the Changelog if you want a full list of recent changes, everything since 3.0 has been Akkoma.

Installation

OTP releases (Recommended)

If you are running Linux (glibc or musl) on x86, the recommended way to install Akkoma is by using OTP releases. OTP releases are as close as you can get to binary releases with Erlang/Elixir. The release is self-contained, and provides everything needed to boot it. The installation instructions are available here.

From Source

If your platform is not supported, or you just want to be able to edit the source code easily, you may install Akkoma from source.

Docker

Docker installation is supported via this setup

Packages

Akkoma is packaged for YunoHost and can be found and installed from the YunoHost app catalogue.

Compilation Troubleshooting

If you ever encounter compilation issues during the updating of Akkoma, you can try these commands and see if they fix things:

  • mix deps.clean --all
  • mix local.rebar
  • mix local.hex
  • rm -r _build

Documentation