To that end, I released a new version of the #rustlang akv CLI using #AzureSDK that now requires a key version for crypto operations. This change should help mitigate data lock-out.
Latest Posts by Heath Stewart
Making the key version required for Key Vault cryptography APIs
Why we changed the key version to be a required parameters for Key Vault cryptography APIs in Azure SDK for Rust.
🪨👎
We need a dislike/reactions button here. 😢
We all saw what dinosaurs did to Samuel L. Jackson's arms in Jurassic Park. It's now April 3rd - you're not fooling me!
That's why www.fediscovery.org was a particular interesting concept. It would seem to help close that gap of discovery on small instances.
But whatever the case, it'd be nice if the tribalism stopped. We should build (more) bridges, not walls.
AP instances need more subs for discovery, which needs more people, which need more storage and bandwidth. I can appreciate the need to recoup costs, which is why I donated to my instance back then. But I also appreciate that creates competition, even within a particular vocabulary.
The fact I can (and likely will eventually; too much going on currently requiring my attention) just spin up my own PDS and migrate my stuff without sacrificing discoverability and visibility is certainly more attractive to me.
And @standard.site proved disparate lexicons can find enough common ground to aggregate the most important bits between similar services.
IMO, it's the data storage that's the big draw to ATProto for me when it comes to the developer ecosystem. I mean, someone has to pay for storage (PDS) and bandwidth (mainly? relay) and people like to get paid, but not necessarily having to cover storage for every sync'd post seems cheaper.
Then whose arms are those?!
Tribalism is hell of a thing. ☹️ I think it looks neat but can totally appreciate stepping back for mental health.
I've enjoyed this thread because I don't feel either of us being defensive. It's interesting discussing the pros and cons. And I'm sure we can all agree: at least it's not X.
Just activity notifications. Full documents and blobs aren't. An AppView wanting those can query the PDS, so it's a PULL model as opposed to APs PUSH model. And, yes, more relays are needed to truly decentralize and that's probably the biggest linchpin. Again, pros/cons of either.
That's neat! Why am I not surprised? @thisismissem.social has her feat in both worlds.
Tangled, Leaflet, and more AppViews also exist. ATProto isn't just the Bluesky lexicon or AppView, afterall. Just like AP also has other use cases beyond Mastodon.
Hosting your own PDS means you own your data, though everything does pass through relays making them less attractive to host without financial support. AP helps with that a little. Definitely tradeoffs in both directions.
It also shifts the burden of hosting. ATProto has all your data hosted in a PDS but shares freely via relay. AP duplicates data (even DDoS's sites for thumbnails, or did they fix that?) to every instance so storage costs and even bandwidth become a problem. There's no penalty for a small PDS.
> Then enshittify with VC money
Maybe. I'm cautiously optimistic, though I imagine charging any sort of subscription to pay for hardware, bandwidth, people, etc., is going to be met with severe scrutiny.
When I was active on fedi I did choose to pay a monthly sub to my instance.
Interesting read. So basically an opt-in, selective relay in the ATProto sense? Sure would fill a big gap I felt fedi had even on a fairly large instance.
Did you get an answer? If it’d help improve my commute time post-RTO, I could do a side hustle. 🤔
And what’s with the slowdowns at JBLM? I’ve never understood that. It’s not like a lot of people are entering or exiting there. Just more gawkers not focused on the road and hoping for cool explosions or something*?
*) They aren’t like in the movies, people.
Announcing initial 1.0 release of my include-file crate with #rustlang macros that effectively let you hide setup code in plain markdown files (md, adoc, etc.) like you can in doctests. We use these in some #AzureSDK docs to keep samples focused while still making sure they compile and work.
Wait…are you calling oatmeal raisin cookies the most disappointing kind of cookies?!
Blocked and reported.
Screenshot of my avatar using a Superman tuck on a virtual cycle in Zwift with a mountain in the background.
I’ve done a super tuck a few times descending mountain roads, but never been so crazy to try a Superman tuck. This #Zwift April Fools prank will suffice.
This is why I bought the same keyboard for work and home. And why I never got comfortable on Dvorak (too often on lab machines back in the day).
Now my only problem is flipping between Windows and Mac keyboards. Fortunately the Ctrl keys are in the same place, but Ctrl/Cmd still often trips me up.
Fluffy black dog sitting like a person on a cream-colored couch leaning on a pillow.
He thinks he’s people part 1,547
Um…I think one leaked out.
And a lot of building 18, at least, isn’t even in yet for reasons. Not sure about the other two attached.
I get your point about creators. I wasn’t thinking of it that way. I was thinking more about infra costs.
But I wanted to clarify that I was thinking about covering compute if an LLM were involved in filtering itself, not just feed creation.
Heck, all this requires compute - and bandwidth, storage, and I’m sure the team likes getting paid or for setting up grants, etc.