social.nathandyer.me — Nathan Dyer's Personal Mastodon Instance
Details
up since 2024-09-14 10:53 (57.2 hours ago)
- Uptime: 99.81%
- Users: 2 (1 active this month, 2 active last six months)
- Posts: 338
- Posts per user: 169.00
- Peers: 11247
- Version: mastodon 4.2.12
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-09-02 21:37 — 2024-09-16 19:54
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 338 (0.72/day)
min/max/avg/stddev: 328 / 338 / 333.10 / 2.13
peers: 11247 (4.11/day)
min/max/avg/stddev: 11190 / 11247 / 11218.91 / 17.67
response_time: 2.277 (-0.04/day)
min/max/avg/stddev: 0 / 7 / 2.16 / 1.36
Crawling Info
First contact: 2023-07-10 (14.3 months ago)
Last successful contact: 2024-09-16 (11.1 minutes ago)
Contact: 27074 successful, 2148 failed.
Average fetch time: 2.16s
Next attempt scheduled for 3.9 minutes from now.
Found through social.jlamothe.net (up)
IP address: 54.38.247.97 (and 934 others, including: tl.timeattack.zone (down), mastodon.heiperlan.de (down), social.meawchill.xyz (down), social.kistler.dev (down), social.cereza.de (down), social.postninja.net (down), freunde.nettesheim.eu (down), social.eiden.ch (down), sir.dhslammer.com (down), m.mossou.com (down))
Staff
Developer, engineer, blogger, and hopeless enjoyer of the little things.
You might know me as:
• Newsroom Support Engineer for the Freedom of the Press Foundation (including work on SecureDrop)
• The developer of Hypatia (quick-look tool) for Linux
All my toots are CC BY-NC-SA 4.0 | #TransRightsAreHumanRights
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-09-16 19:19:54 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 16:41:58 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 16:26:13 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 16:10:55 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 15:39:50 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 15:24:17 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 13:05:20 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 12:35:02 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 12:19:51 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-09-16 11:34:30 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-09-16 19:54:10 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 19:37:48 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 19:03:37 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 18:48:03 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 18:16:24 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 18:00:31 in 0.21s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 17:44:49 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 17:29:06 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 17:13:18 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 16:57:31 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-09-16 16:57:31 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 07:42:24 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-15 23:27:53 in 0.16s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-15 15:26:43 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-15 03:39:26 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-14 17:18:44 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-14 07:09:30 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-09-16 19:54:10 in 0.99s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 19:37:48 in 1.06s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 19:03:37 in 1.09s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 18:48:03 in 1.10s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 18:32:16 in 0.49s]: IP: 54.38.247.97 / Error: unparseable / HTTP status: 200
- [2024-09-16 18:16:24 in 0.97s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 18:00:31 in 1.01s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 17:44:49 in 1.05s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 17:29:06 in 1.01s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-09-16 17:13:18 in 1.06s]: IP: 54.38.247.97 / OK / HTTP status: 200