sharkey.team — Sharkey Team!
An instance for the official sharkey account.
Details
up since 2025-01-13 05:48 (41.6 days ago)
- Uptime: 100.00%
- Users: 1
- Posts: 1
- Posts per user: 1.00
- Peers: 1331
- Version: sharkey 2024.11.2
- Source code: https://activitypub.software/TransFem-org/Sharkey/
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 09:44 — 2025-02-23 17:37
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯peers: 1331 (11.30/day)
min/max/avg/stddev: 1316 / 1331 / 1325.40 / 5.16
response_time: 1.511 (-1.16/day)
min/max/avg/stddev: 0 / 5 / 2.48 / 1.54
Crawling Info
First contact: 2025-01-13 (41.6 days ago)
Last successful contact: 2025-02-23 (105.4 minutes ago)
Contact: 10 successful, 1 failed.
Average fetch time: 2.48s
Next attempt scheduled for 85.8 minutes ago.
Found through fedi.wlabs.de (up)
IP address: 5.161.73.220 (and eepy.moe.)
Staff
sharkey@sharkey.team
Sharkey is an Misskey fork following upstream changes when possible, with added features! It has features such as: * Federated note editing * Scheduled notes * Mastodon API * UI Improvements * Federated Profile Backgrounds * Federated Music Status via Listenbrainz It is possible to migrate to Sharkey from: * IceShrimp.js * Misskey
Sharkey is an Misskey fork following upstream changes when possible, with added features! It has features such as: * Federated note editing * Scheduled notes * Mastodon API * UI Improvements * Federated Profile Backgrounds * Federated Music Status via Listenbrainz It is possible to migrate to Sharkey from: * IceShrimp.js * Misskey
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-02-23 12:23:40 in 0.00s]: IP: 5.161.73.220 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-02-23 17:37:04 in 0.42s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-23 14:57:27 in 0.65s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-23 09:44:51 in 0.48s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-23 04:40:36 in 0.77s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-22 09:44:55 in 0.77s]: IP: 5.161.73.220 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2025-02-23 17:37:04 in 0.35s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-23 14:57:27 in 0.44s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-23 09:44:51 in 0.43s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-23 04:40:36 in 2.24s]: IP: 5.161.73.220 / OK / HTTP status: 200
- [2025-02-22 09:44:55 in 1.84s]: IP: 5.161.73.220 / OK / HTTP status: 200