Activity for seqre.dev

LOOK MA, I'M FAMOUS (1:20s 👀)

That was a good read, thanks for sharing!

Okay, that's pretty neat stargraph.link/user/seqre.dev

Where is that from?

Yesterday @mackow.ski and I released @cot.rs v0.6 🎉 While it's great, I want to emphasize that we're going to start doing monthly town halls to bring community more into development cycle! If you're interested in Rust web development and/or @cot.rs progress, please come and join us 🙌

Who doesn't want their margins ✨ jiggly ✨

Yo @margin.at, is it intended? I just scrolled down a tiny bit and it started jumping lol

I meant more subscription: is this some usual way or some fancy AT Proto way? But tbh, hearing about analytics sounds good too!

Will you share how did you implement this? 👀

Reviewed a movie

2001: A Space Odyssey

Stanley Kubrick

Reviewed a movie

KPop Demon Hunters

Maggie Kang

@baileytownsend.dev @mackuba.eu @patak.cat Want to roast me or sumthing? :p

I think it got lost in the middle of @tangled.org funding and @npmx.dev news, but I really want feedback from AT Proto folks about this idea 👉👈

Check out this: github.com/plankanban/p...

Oh yeah, something like that! There is @cred.blue which does similar thing

Calling out to ATProto builders I know of (and interacted with 😅): @baileytownsend.dev @mackuba.eu @patak.cat Am I cooking or not? I want to know if this is sane idea lol

The biggest selling point for this is that it'd have to be done once per application and anything on the Internet could use it to learn how to sponsor the app (not only components of my idea!).

Basically GitHub's FUNDING.yml but instead an ATProto record. It would be stored in the application repository and would specify how folks can donate to it. It could have some pre-defined ways (OpenCollective, Ko-fi, etc.) that would be standardized as well as URLs or text to explain custom methods.

This theoretically could be enough, it would just require some up-front work for each app to setup itself within the platform and specify how to pay it. But what if we could sort of automate this? Let me introduce custom lexicon A - sponsorship records.