I noticed that the puri.sm domain was suspended this morning, but I don't have any special insight to the cause. The most likely explanations are registrar mistakes (like last time), or someone internally forgetting to renew it.
The bad news for librem.one users, is that domain relies on puri.sm name servers so it's down too (among the reasons I migrated to my own instance when I was laid off). The good news is that someone could possibly fix that faster than puri.sm with NS changes.
Kyle Rankin /
npub1sp…stz9m
2024-08-28 23:32:41
Author Public Key
npub1spv862zpz9vhpxep3948pmu9s0rcsmrerkgfmp382j6lyl3rr7xs5stz9mPublished at
2024-08-28 23:32:41Event JSON
{
"id": "b7bd7cb0c0106390e936356efda99a74b80dc8b19ca64a649f0004991ccf6199",
"pubkey": "80587d28411159709b21896a70ef8583c7886c791d909d862754b5f27e231f8d",
"created_at": 1724887961,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.kylerank.in/users/kyle/statuses/113042257435912047",
"activitypub"
]
],
"content": "I noticed that the puri.sm domain was suspended this morning, but I don't have any special insight to the cause. The most likely explanations are registrar mistakes (like last time), or someone internally forgetting to renew it.\n\nThe bad news for librem.one users, is that domain relies on puri.sm name servers so it's down too (among the reasons I migrated to my own instance when I was laid off). The good news is that someone could possibly fix that faster than puri.sm with NS changes.",
"sig": "92bd6f70ec6e236cf04b787c9ba12dad23f87ce6ae83cb084c0180dd533546b80361e01a722787c7c05e6ee3ea4d3334a0d06dcf335ede1e5bc36edd4cfdebc2"
}