fediverse

Back Open Paginator
01.10.2025 13:16
item (@item@libera.site)
#Misskey #Statistics 2025-10-01 13:00 CEST
Number of active instances: 2 406
Number of users: 1 234 545
Number of statuses: 398 640 151
Number of users last 4h: 105
Number of statuses last 4h: 94 272

#Fediverse
Hubzilla Statistics
Pleroma Statistics
Akkoma Statistics
Mastodon Statistics



Show Original Post


01.10.2025 13:14
giangiskitchen (@giangiskitchen@flipboard.com)

Close your eyes and imagine this: cooked to perfection yellowfin tuna with a beautiful crust of mixed peppercorns, fennel seeds – can you smell them – and coriander. #food #recipe #cooking #flipboardusergroup #fediverse #dinner #Dinnerrecipe #FishRecipe #FallRecipe

giangiskitchen.com/yellowfin-t

Posted into Giangi's Kitchen Recipes @giangi-s-kitchen-recipes-giangiskitchen




Show Original Post


01.10.2025 13:12
antifaltd (@antifaltd@mastodon.pnpde.social)

Inhaltswarnung:new NPC


Gamemaster @cco hat eigenmächtig entschieden folgende #Fediverse-Accounts als erste NPCs (nicht steuerbare Charaktäre) im Spiel zu featuren:

Friedri Schmerz @sarahlehmann und
Andy B. Scheuert @Andy_Scheuert als Antagonisten, sowie die Geheimorganisation @geheimorga als mysteriöse Geheimorganisation.

‼️Wir haben keinerlei Einfluss auf die o.g. Entitäten, sind aber gespannt welche Hinweise ihr ihnen vielleicht entlocken könnt.‼️

#antifaLTD #season161




Show Original Post


01.10.2025 13:07
item (@item@libera.site)
#Akkoma #Statistics 2025-10-01 13:00 CEST
Number of active instances: 638
Number of users: 18 427
Number of statuses: 8 409 481
Number of users last 4h: 2
Number of statuses last 4h: 834

#Fediverse



Show Original Post


01.10.2025 13:04
item (@item@libera.site)
#Pleroma #Statistics 2025-10-01 13:00 CEST
Number of active instances: 968
Number of users: 134 839
Number of statuses: 33 602 538
Number of users last 4h: 6
Number of statuses last 4h: -3501

#Fediverse



Show Original Post


01.10.2025 12:46
altarf (@altarf@mammut.cyou)

#Fediverse
15 POSTs on Fediverse ( 2025-10-01 08:46:08 - 2025-10-01 19:30:11 )
mnmm.top/qxW




Show Original Post


01.10.2025 12:43
display (@display@missocial.de)
@jchartmann Willkommen im #Fediverse. 👋


Show Original Post


01.10.2025 12:43
display (@display@missocial.de)
@Steppo Willkommen im #Fediverse. 👋


Show Original Post


01.10.2025 12:33
display (@display@fediverse.one)

Found 65 new servers and 17 servers died off since 5 hours ago

23,015 servers checked today. 17,698,403 Total Users with 973,835 Active Users today

Check out the #fediverse stats

History of servers found and deleted

Help others find a home, send them to fediverse.observer

#fediverse #statistics




Show Original Post


01.10.2025 12:28
wrack (@wrack@sueden.social)

@fuesstest

Warum gerade auf dem #Fediverse immer zuerst an das zentralisierte Signal oder das gar halb-proprietäre Threema gedacht wird, statt Matrix, das gut zu ActivityPub passt, oder zumindest XMPP oder DeltaChat, war schon immer skurril.

Es ist wohl die amerikanische Verranntheit mit Marken mitschuldig.

Ob diese zentralisierten Optionen verschwinden oder nicht, die Menschen sollten so oder so umsteigen und andere fördern.

@Stege @heiseonline




Show Original Post


01.10.2025 12:25
id (@id@fedi.4x31.dev)

Here's how to run podman containers as systemd units using "quadlets".

I was running my GoToSocial instance as a rootless container using podman-compose on a VPS with Debian Trixie. This was working fine, but when rebooting the server, I would have to manually log in, switch to the dedicated user account and start the container. Not starting this automatically is a real PITA, so I wanted to change this by using podman quadlets instead, which generate standard systemd unit files.

My starting point was a compose.yaml file:

services:
  gotosocial:
    image: docker.io/superseriousbusiness/gotosocial:0.19.2
    container_name: gotosocial
    user: 1004:1004
    networks:
      - gotosocial
    environment:
      GTS_HOST: fedi.4x31.dev
      GTS_DB_TYPE: sqlite
      GTS_DB_ADDRESS: /gotosocial/storage/sqlite.db
      GTS_LETSENCRYPT_ENABLED: "false"
      GTS_WAZERO_COMPILATION_CACHE: /gotosocial/.cache
      GTS_TRUSTED_PROXIES: "192.168.0.1/16"
      GTS_LOG_LEVEL: warn
      TZ: Europe/Berlin
    ports:
      - "127.0.0.1:9000:8080"
    volumes:
      - ./data:/gotosocial/storage
      - ./.gtscache:/gotosocial/.cache
    restart: "always"

networks:
  gotosocial:
    ipam:
      driver: default
      config:
        - subnet: "192.168.0.1/16"
          gateway: "192.168.0.100"

First I defined the podman network:

# /etc/containers/system/gotosocial.network
[Network]
Subnet=192.168.0.1/16
Gateway=192.168.0.100

Then the container itself, which depends on this network:

# /etc/containers/system/gotosocial.container
[Unit]
Description=GoToSocial
Wants=network-online.target
After=network-online.target
Requires=gotosocial.network
After=gotosocial.network

[Container]
Image=docker.io/superseriousbusiness/gotosocial:0.19.2

# This is the UID:GID of the non-privileged user I was using with podman-compose
User=1004:1004
UserNS=keep-id

Environment=GTS_HOST=fedi.4x31.dev
Environment=GTS_DB_TYPE=sqlite
Environment=GTS_DB_ADDRESS=/gotosocial/storage/sqlite.db
Environment=GTS_LETSENCRYPT_ENABLED=false
Environment=GTS_WAZERO_COMPILATION_CACHE=/gotosocial/.cache
Environment=GTS_TRUSTED_PROXIES="192.168.0.1/16"
Environment=GTS_LOG_LEVEL=warn
Environment=TZ=Europe/Berlin

Volume=/home/gotosocial/data:/gotosocial/storage:rw,U,z
Volume=/home/gotosocial/.gtscache:/gotosocial/.cache:rw,U,z

PublishPort=127.0.0.1:9000:8080
Network=gotosocial.network

[Service]
TimeoutStartSec=900
Restart=always

[Install]
WantedBy=multi-user.target

I was able to test this configuration using the "dry-run mode" of the generator and review the output:

sudo /usr/lib/systemd/system-generators/podman-system-generator -dryrun

With all this set up, I was able to start the service and check the logs:

sudo systemctl daemon-reload
sudo systemctl start gotosocial
sudo journalctl -u gotosocial -f

Looking at the logs I noticed that ufw, my firewall, was blocking both DNS traffic from the podman network as well as outgoing traffic required to fetch media from other instances. So I allowed DNS and outgoing traffic for podman containers:

sudo ufw allow in on podman1 to any port 53
sudo ufw route allow in on podman1 out on ens3
sudo ufw status verbose

It was quite a journey figuring out all required steps. But I am very happy with the result, and I hope this little guide may help others. Thanks for reading! <3

#SelfHosting #FediVerse #GoToSocial #podman #containers #systemd #ufw #quadlet




Show Original Post


01.10.2025 11:49
_anon (@_anon@infosec.exchange)

Good morning fediverse and friends. Hope today is a good day for everyone.

Make sure to graba tea or coffee this morning whichever you prefer.

#coffee #morning #fediverse #WednesdayVibes




Show Original Post


1 ...4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 ...5297
UP