PieFed - Explore Anything, Discuss Everything.

if working is not None:
    print('the thing works')
else:
    print('the thing does not work')

Single line of code: [4 spaces and an escaped newline]
return [4 spaces and an escaped newline]
New paragraph [2 escaped newlines]

Code Block (no lang): [4 spaces and an escaped newline]

if this [4 spaces and an escaped newline]    
then [4 spaces and an escaped newline]    
that
else
the_other_thing [4 spaces and an escaped newline]    
endif

(no spaces before newlines for next block)

Code Block (python):

if this is not None:
    that
else:
    other_thing

am i even subscribed

if image is not None:
   pass

This is probably just me, but I found INSTALL.md to be a bit confusing.

So, for a fresh install of Ubuntu in a Windows Hyper-V VM, this is the list of steps I took to get something that at least looks like it might be the right thing:

remove unattended-upgrades, and clean up after OS install

sudo systemctl stop unattended-upgrades
sudo apt-get purge unattended-upgrades
sudo apt autoremove

install postgresql 16

sudo apt install ca-certificates pkg-config
wget --quiet -O - [https://www.postgresql.org/media/keys/ACCC4CF8.asc](https://www.postgresql.org/media/keys/ACCC4CF8.asc) | sudo apt-key add -
sudo sh -c 'echo "deb [http://apt.postgresql.org/pub/repos/apt/](http://apt.postgresql.org/pub/repos/apt/) $(lsb_release -cs)-pgdg main" >> /etc/apt/sources.list.d/pgdg.list'
sudo apt update
sudo apt install libpq-dev postgresql

install python libs

sudo apt install python3-pip python3-venv python3-dev python3-psycopg2

install redis server

sudo apt install redis-server

install git

sudo apt install git

set up database

sudo -iu postgres psql -c "CREATE USER pyfedi WITH PASSWORD 'pyfedi';"
sudo -iu postgres psql -c "CREATE DATABASE pyfedi WITH OWNER pyfedi;"

clone PieFed

git clone [https://codeberg.org/rimu/pyfedi.git](https://codeberg.org/rimu/pyfedi.git)

cd into pyfedi, set up and enter virtual environment

cd pyfedi
python3 -m venv ./venv
source venv/bin/activate

use pip to install requirements

pip install wheel
pip install -r requirements.txt

edit .env file

cp env.sample .env
nano .env
(change SECRET_KEY to some random sequence of numbers and letters)

initialise database, and set up admin account

flask init-db

run the app

flask run
(open web browser at http://127.0.0.1:5000))
(log in with username and password from admin account)

Maybe this will help someone else (or maybe someone has spotted something that I missed - like I say: it looks right when loaded in a browser, but I'm not 100% sure)

From my nginx access log

your.ip.address - - [21/Feb/2024:06:53:19 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.2; +https://feddit.de"
your.ip.address - - [21/Feb/2024:06:53:21 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.2; +https://feddit.de"

This was "https://feddit.de/activities/like/19ab3a68-e9ae-4218-8ca2-d8cc885e96f9" being sent twice.

I've reported this problem to other affected servers that I've seen:
the lemmy.ca post suggests the problem was something to do with running multiple containers with the same index number;
the endlesstalk.org post suggests that re-starting the backend containers is a fix
(their answers will likely more sense to you than to me, as I don't run lemmy).

Thanks! (and apologies for this being in English)

From my nginx access log:

your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"
your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"
your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"
your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"

2 of the entries are "https://lemmy.sdf.org/activities/like/88bc5b6d-f11f-4245-90aa-908e43befe97" being sent twice,
the other two are "https://lemmy.sdf.org/activities/like/437327e5-a262-46bc-8ce7-1c2c5bd440b3" being sent twice

I've reported this problem to other affected servers that I've seen:
the lemmy.ca post suggests the problem was something to do with running multiple containers with the same index number;
the endlesstalk.org post suggests that re-starting the backend containers is a fix
(their answers will likely more sense to you than to me, as I don't run lemmy).

Thanks!

Hi. Just looking at what lemmy.ca sends my server:

From nginx log:

your.ip.address - - [20/Feb/2024:03:48:47 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.ca/"               
your.ip.address - - [20/Feb/2024:03:48:49 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.ca/"         
your.ip.address - - [20/Feb/2024:03:48:57 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.ca/"              

Dumping the JSONs reveals 3 duplicate files, all containing:

"id": "https://lemmy.ca/activities/create/0968bf93-ac05-4178-bf3f-28cdc65fc338"
"actor": "https://lemmy.ca/u/HairyOldCoot"
"object": {
  "id": "https://lemmy.ca/comment/7454502"            
  "content": "That was an episode of Sliders."
  "published": "2024-02-20T03:48:45.810068Z"

These are 3 Creates, not 1 Create and 2 Updates or anything. I've chosen a comment 'cos that's public info, but it's the same for all other activity too (Votes, Deletes, etc).

lemmy.ca isn't alone in this. endlesstalk.org sends everything twice (info posted here), as does lemmy.sdf.org and mander.xyz, but lemmy.ca is the only one I've seen send stuff 3 times. Other instances (e.g. aussie.zone, feddit.nl, lemm.ee, lemmings.world, lemmy.world, programming.dev, reddthat.com, sh.itjust.works, slrpnk.net) don't, but there's nothing obvious like lemmy version numbers to indicate the difference.

Whilst I'd prefer you didn't send me stuff 3 times, I'm mostly mentioning it because I doubt it's good for your own resources to send every activity by every lemmy.ca user out multiple times. Also, the OPs of my community are from Mastodon, so I imagine you're sending them the same message 3 times too ...