Community-supported infrastructure ready for production.
relay.fire.hose.cam
constellation.microcosm.blue
slingshot.microcosm.blue
more:
https://microcosm.blue
https://tangled.org/@microcosm.blue
Unavailable:
🟠 spacedust.microcosm.blue
🟠 ufos-api.microcosm.blue
Available with stale data
🟡 constellation.microcosm.blue
NOT affected
🟢 slingshot.microcosm.blue
🟢 plc.wtf
🟢 both relays
🟢 all three jetstream
Unavailable:
🟠 spacedust.microcosm.blue
🟠 ufos-api.microcosm.blue
Available with stale data
🟡 constellation.microcosm.blue
NOT affected
🟢 slingshot.microcosm.blue
🟢 plc.wtf
🟢 both relays
🟢 all three jetstream
you can browse it: qoomon.github.io/aws-s3-bucke...
need to actually test, someone want to try to restore from it?
you can browse it: qoomon.github.io/aws-s3-bucke...
need to actually test, someone want to try to restore from it?
once it's done, you should be able to mount the bucket locally, start constellation with `--restore-from-backup`, and have an instance with the full constellation.microcosm.blue backlink history up in an hour or two
once it's done, you should be able to mount the bucket locally, start constellation with `--restore-from-backup`, and have an instance with the full constellation.microcosm.blue backlink history up in an hour or two
Plz gib money so I can do more things that benefit people.
Plz gib money so I can do more things that benefit people.
indexed by constellation
across every lexicon
that you can query
at constellation.microcosm.blue
indexed by constellation
across every lexicon
that you can query
at constellation.microcosm.blue
Previously just showed quotes of the Leaflet post; now *also* shows all Bluesky mentions, including the one linked on initial publish if it exists
Eventually we can expand this to include mentions in other Leaflet posts…and other atproto apps!
by 8:30am EDT, auto-recovery worked for all services, which fully recovered on their own.
by 8:30am EDT, auto-recovery worked for all services, which fully recovered on their own.
- relay PDS connections dropped around 3am EST
- autoreconnect brought them back up around 8am EST
firehose event delivery was *delayed* during those five hours (no events were lost)
the server did not reboot, the relay container stayed up. dmesg on the host has nothing since oct 25
pds hosts connected dropped abruptly and there are some gaps in metrics
- relay PDS connections dropped around 3am EST
- autoreconnect brought them back up around 8am EST
firehose event delivery was *delayed* during those five hours (no events were lost)
⭐️ 41
⭐️ 41
⭐️ 36
⭐️ 36
Fix: parameter passing when proxying
New mode: "wrap". Reverse-proxy to a PLC server. Eg: Allegedly can replace Caddy in front of Parakeet, and accept writes via PLC op forwarding. Auto TLS included.
New example code: poll PLC to detect unexpected changes to your DID:
Fix: parameter passing when proxying
New mode: "wrap". Reverse-proxy to a PLC server. Eg: Allegedly can replace Caddy in front of Parakeet, and accept writes via PLC op forwarding. Auto TLS included.
New example code: poll PLC to detect unexpected changes to your DID:
aka, posts can act as a many-to-many join between mentioned users
want to see who you’re mentioned together most often with?
motivating example was bluemoji, but it's already usable for some general traversal. you can ask,
> what issues on @tangled.org have a "good-first-issue" label?
check it:
aka, posts can act as a many-to-many join between mentioned users
want to see who you’re mentioned together most often with?
For now it is limited "read only". Soon enough you'll be able to interact with Link on blacksky.community
Try it out: anisota.net
Try it out: anisota.net
🥝 relay.fire.hose.cam and jetstream.fire.hose.cam (montreal)
🥝 relay3.fr.hose.cam and jetstream2.fr.hose.cam (EU)
🍊https://jetstream1.us-east.fire.hose.cam *is* affected because it subscribes to bsky.network
🥝 relay.fire.hose.cam and jetstream.fire.hose.cam (montreal)
🥝 relay3.fr.hose.cam and jetstream2.fr.hose.cam (EU)
🍊https://jetstream1.us-east.fire.hose.cam *is* affected because it subscribes to bsky.network