git clone https://schlomp.space/FediPotato/FediPotato.git
|
10 months ago | |
---|---|---|
cmake | 1 year ago | |
gui | 11 months ago | |
lib | 10 months ago | |
tests | 1 year ago | |
.clang-tidy | 1 year ago | |
.editorconfig | 1 year ago | |
.gitignore | 1 year ago | |
AUTHORS | 1 year ago | |
CMakeLists.txt | 10 months ago | |
CODE_OF_CONDUCT.adoc | 1 year ago | |
CONTRIBUTING.adoc | 10 months ago | |
CREDITS | 1 year ago | |
LICENSE | 1 year ago | |
README.adoc | 10 months ago |
FediPotato is a client for Fediverse servers.
❏ Get posts from:
❏ Mastodon & Pleroma
❏ Parastat
❏ Maybe others
❏ Show posts in a threaded view.
❏ Subscribing to hashtags.
❏ Separate filtered views (timelines filtered with regular expressions).
❏ Post posts.
Tested OS: Linux
C++ compiler with C++17 support (tested: GCC 7/8/9, clang 6/7)
CMake (at least: 3.9)
mastodonpp (at least: 0.5.4)
nlohmann-json (tested: 3.6)
Boost (at least: 1.62)
Qt (tested: 5.13)
Optional
git clone https://schlomp.space/FediPotato/FediPotato.git
mkdir -p build && cd build
cmake ..
cmake --build . -- -j$(nproc --ignore=1)
-DCMAKE_BUILD_TYPE=Debug
for a debug build.
-DWITH_TESTS=YES
if you want to compile the tests.
-DWITH_GUI=NO
to only compile and install the library.
-DWITH_CLANG-TIDY=YES
to check the sourcecode with
clang-tidy while compiling.
-WITH_DOC=YES
to generate the API documentation.
One of:
-DWITH_DEB=YES
if you want to be able to generate a deb-package.
-DWITH_RPM=YES
if you want to be able to generate an rpm-package.
To create a deb or rpm package, run make package
after compiling.
Read the Code of Conduct.
Before reporting a bug, please perform a search to see if the problem has already been reported. If it has, add a comment to the existing issue instead of opening a new one. Same for enhancements.
Please use similar coding conventions as the rest of the project. The basic rule to remember is to write code in the same style as the existing/surrounding code.
Add a copyright line with the year, your name and your email address to the files you edited. Add your name and email to AUTHORS. Unless you don’t want to.
You can also send me your patches via E-Mail, ideally using git format-patch or git send-email.