@deadsuperhero
General Discussion
4
Posts
1
Posters
15
Views
-
I am heart to heart with you on this, friend.
-
I am heart to heart with you on this, friend.
@deadsuperhero so, here's my best bet. I can be wrong!
1. Get some servers to implement the API well.
2. Get some must-have clients that run on those servers. This shows the value of the API.
3. Our leading servers shift to supporting it.That may work; I don't know. It's my best bet right now!
I want to note that WordPress is working on the API!
-
System moved this topic from Uncategorized on
-
@julian @deadsuperhero We actually have a meeting tomorrow if either of you wants to come.
https://www.w3.org/events/meetings/3432cf4c-a9fe-4f72-8de5-fa6809b57767/20260219T110000/
-
@evan@cosocial.ca Yeah, I mostly agree with this. It's just that the buy-in is a little bit of a chicken and egg problem. You need servers to adopt it, but you need a compelling first mover. Bonfire, maybe?
The spec definitely needs love, too. I think one of the harder things is building a timeline out of inbox activities. I feel like maybe a future version of the API could specify timelines somehow, whether it's an endpoint or some kind of basic query? Maybe there's even a way to implement alternative timelines at that level?
These are all just guesses on my part, but I feel like this could be a gateway to universal custom feeds.
@deadsuperhero so, it's a two-sided market -- clients and servers. The traditional mechanism is a "ratchet" -- build up one side, then build up the other, and then build up the first.
So, yes, servers first, then clients, then more servers, more clients, and so on back and forth.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@deadsuperhero so, it's a two-sided market -- clients and servers. The traditional mechanism is a "ratchet" -- build up one side, then build up the other, and then build up the first.
So, yes, servers first, then clients, then more servers, more clients, and so on back and forth.
-
A working group might be able to come up with other, non-software strategies for dealing with this shit. Perhaps relying on new features in the software that don't actually ID anyone but could attach the status of having BEEN IDed or just let in and I'll take responsibility.
But it takes actually thinking about and studying a problem to come up with answers like that. You can't just shove your head up your ass and then yell at it.
-
@nitrml @fbinin @ret @mellifluousbox Should be noted that if we all actually did manage to get sentenced to prison we'd either break the system or end up in warehouses in the desert surrounded by overheated assholes in cammo.
Either way, problem solved.
-
@mellifluousbox It has to be thought about. Sometime soon people may have to decide if they're going to implement age verification or shut down their servers. If they're to be provided any answers, be they implemented options or a documented reason why this is just done, then the effort to come up with them needs to start before they're needed.
-
Also, you should give yourself a break and use the miscellany context.
-
@nitrml how do you think they’ll implement age verification on mastodon dot social? Special fork? No. It’ll be baked into the software, which will create a precedent for this to be implemented everywhere.
-
@gbargoud they’re free to make their own decisions about whether they comply or not. The instance I’m using right now is in violation of UK law. Probably Saudi law, Iranian law, Chinese law, etc etc… there’s no winning this.
-
@raphael @liaizon @smallcircles @django ha! There are a lot of Djangos involved in the social API.
