Évidemment c'est marrant de voir ceux sur-utilisés, mais je trouve ça super mystérieux les quelques points noirs surtout. C'est la liste des nombres à 4 chiffre auquel le cerveau humain refuse de penser ?

Oh I didn't heard of hotwire native, is it what was once called Strada ? I did some react native in the past and I kind of miss mobile development now that I follow the "canonical" RoR stack

So, as long as it is clear that any data requested by a user should be in its pds, we could easily implement pds resolution from user handle/did, the didkit gem does it right now github.com/mackuba/didkit

At first I was a bit confused about where the private data/routes were, and though maybe some private resources were living in specific pds (like bsky threads endpoint), that's why I wanted the user to be able to request any pds.

Now I realize it should simply live with the rest of your data.

Thank you !
No currently the gem can't find the pds itself. The boletus pds is one of the bluesky pds (probably where my data is stored), I wrote it in the example to make it clear it was expecting a full pds url (and not an entryway like bsky.social)

I hope it will serve you well. Don't hesitate to give feedbacks or open issues/PRs, the thing is still quite young, and could be improved in many ways.

Oh and there is also a "client" to make authenticated requests once you've got your precious tokens : github.com/lasercatspro...

Oh you're right, I totally forgot this file (I'm quite new in the repo maintenance game). It should be fixed !

Yes the link, of course : github.com/lasercatspro...

There is also a lot of things to discuss and do about atproto_client. I think it tries to do too much things right now, I am tempted to just make it a dpop handler (you give it a request, it dpopize it).
This way other gems could use it, like @mackuba.eu's minisky, which has a far better api

(I would love to add a generator for the peculiar configuration setup, the keys + the metadata.json endpoint)

Here is the omniauth strategy I promised : github.com/lasercatspro...

I checked yours but as it was a full rails app and I allready had a lot of code on my side I prefered opening a new repo.
But it has a lot of room to improve so if you want we can work on it together

You're also catching some urls. I think #! is too widely used.

But the fun part is that some people are allready using #important for their own purposes.

Nice feature !
2 comments though :
- I think currently you're seeing posts from anybody (not just people you follow), it might be a feature but I think some people will overuse it and make it unusable.
- you're catching expressions like %#! (used for insulting or stuff like that)

Yes I was quite lost myself until Claude came to help, I realized these things were actually pretty good at clarifying specs. And that video too m.youtube.com/watch?v=Bkig... (amazing speakers)
Did you try to use the gem for your strategy ?
I have one working in a draft project that I should extract

damn.

(c'est cool d'écrire en anglais aussi non ?)

Hey how did you get these gandi credentials 😱

Cool :)

I'm working on a ruby implementation for the oauth/dpop thing currently, and have something "working" here : github.com/lasercatspro....
Probably not ready to be in that list, but I wanted the world to know it existed.
(an omniauth strategy based on it should come too)