I’m really sorry to hear that, Kat… Sending positive thoughts your way

That sounds like a fantastic day

Am I the crazy one for primarily using Discord for VoIP?

Got it. I like this a lot, although I’ll admit I have a vested interest in minimizing the stock pots on our counter and keeping milk jugs filled with ice out of our sink

Good to know! And it’s not too difficult to remove the frozen milk from the container?

If you come up with a technique that works well, I can pass it along to Morgan!

Good catch! I nabbed it. I'll move this project to that domain, lop off the `avatar` path segment, and reserve "silhouette" for more complicated profile management

Thanks! I’ll keep cooking on the profiles thought—let me know if you have any better ideas for a project name or domain 😅

Aight, here it is: silhouette.town

Returns a 303 redirect to your avatar's blob URL, see silhouette.town/avatar/graha...

Super simple, without any caching atm. Source available on Tangled tangled.org/graham.syste...

Aight, here it is: silhouette.town

Returns a 303 redirect to your avatar's blob URL, see silhouette.town/avatar/graha...

Super simple, without any caching atm. Source available on Tangled tangled.org/graham.syste...

I made an attempt but Nushell integration wasn't working out of the box. I ended up switching to Asahi NixOS

Yeah, that seems fair. I'm gonna keep thinking about this, but in the meantime I'll spend the day writing a service that redirects to your Bluesky profile pic blob URL from an identifier path segment

You might be able to solve that problem with an attestation record that says "my service ____ uses profile ___", then you can visualize the impact that say, changing your professional profile picture will have. But supporting that across services seems like a lot of overhead?

I wonder if it might make things more confusing to folks though. When you edit your Bluesky profile, you have some idea of the services where your identity will change. If you have multiple profiles that are not service-specific, knowing what services will be affected becomes more complicated

Seems simple enough to just rip the app.bsky.actor.profile schema and create some other collection that can have multiple. I can see utility in being able to grab a profile picture from my PDS with a human-writable URL.