bitforged.social — BitForged Social
Details
up since 2024-12-04 00:04 (82.2 days ago)
- Uptime: 99.20%
- Users: 3 (1 active this month, 2 active last six months)
- Posts: 303
- Posts per user: 101.00
- Peers: 10923
- Version: mastodon 4.2.10
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 20:58 — 2025-02-24 03:45
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 303 (0.00/day)
min/max/avg/stddev: 303 / 303 / 303.00 / 0.00
⋯ ⋯peers: 10923 (9.35/day)
min/max/avg/stddev: 10911 / 10923 / 10918.43 / 3.85
response_time: 1.032 (-1.76/day)
min/max/avg/stddev: 1 / 5 / 3.24 / 1.53
Crawling Info
First contact: 2023-12-09 (14.5 months ago)
Last successful contact: 2025-02-24 (80.9 minutes ago)
Contact: 38098 successful, 3904 failed.
Average fetch time: 3.24s
Next attempt scheduled for 55.8 minutes ago.
Found through planet.chrisbeckstrom.com (down)
IP address: 172.93.110.65 (and 2 others: bitforged.stream (up), bitforged.space (up))
Staff
I am a software developer who converts caffeine to code!
I also happen to play games - you're most likely to find me on Destiny 2 however!
I'm a big fan of Linux, but use whatever works best for you!
Additionally, I work on BitForged alongside with @myth!
#Linux #Programming #OpenSource #VideoGames #Destiny2 #Crohns
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-02-24 00:43:00 in 0.00s]: IP: 172.93.110.65 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-02-24 03:45:19 in 0.07s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 22:24:58 in 0.59s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 20:00:37 in 0.41s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 17:20:59 in 0.07s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 14:33:37 in 0.07s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 11:45:10 in 0.39s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 09:03:41 in 0.33s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-22 20:58:09 in 0.33s]: IP: 172.93.110.65 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-23 22:24:58 in 0.51s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 11:45:10 in 0.56s]: IP: 172.93.110.65 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-02-24 03:45:19 in 0.31s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 22:24:58 in 1.99s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 20:00:37 in 2.35s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 17:20:59 in 0.31s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 14:33:37 in 0.31s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 11:45:10 in 1.98s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-23 09:03:41 in 1.97s]: IP: 172.93.110.65 / OK / HTTP status: 200
- [2025-02-22 20:58:09 in 1.93s]: IP: 172.93.110.65 / OK / HTTP status: 200