You might be having a bad day, but at least you didnt spend like a decade developing a social media protocol that was structurally incapable of DMs so you needed to make a whole second E2EE protocol
@denis Ja, ohne diesen Typen ist es direkt wesentlich besser geworden. Ich experimentiere damit noch, da ich noch nicht den Nutzen/das Netzwerk für mich gefunden habe.
Demande d'ajout de mon PDS #bsky faite. On va voir combien de temps il faut.
L'étape d'après, ce serait un firehose communautaire, mais pouvoir réellement héberger ses données est un premier pas. J'avoue que j'étais pas confiant sur l'arrivée de cette étape. #federation#bluesky @aeris@fenarinarsa vous avez tenté déjà ?
@alucard c’est un bug qui traine depuis longtemps, je crois que c’est parce que tu as un nom avec ton propre DNS, il faut aller dans les paramètres de Bluesky et le revalider.
They have created their own (new) protocol "The AT Protocol" while there was a puuurefctly good protocol available, ActivityPub (the one Mastodon and other Fediverse software uses)
With their decision they have created another "island of social platforms" while ActivityPub is adopted more widely each day
@stux More import is that the reason they developed their own protocol is to maintain centralized control over the "federates" network. With ActivityPub, there is no central point it control---servers themselves are free to federate, or not federate, as they please. In AT protocol, BlueSky maintains control.
So OK I keep trying to like #atproto / #bsky, lexicons specifically but they make it so hard. like... let's see, OK we're going to reinvent RDF and JSON-Schema such that
there is some concept of a "namespace authority" rooted in DNS ownership of a domain name that is supposed to maintain a set of lexicons and do things like make sure there are no duplicates (eg. lexicon IDs are case sensitive but you are not allowed to have IDs that differ only in case, which a ns authority has to ensure)
but there is no means of using the domain to retrieve a schema, so eg. it is explicitly not spec'd to require com.example.myLexicon be at myLexicon.example.com - so the whole goofy Javabrained reverse-domain name thing as the ID is pointless
Accordingly, lexicons have to be sourced ad-hoc and by convention, and the convention is bonkers!!!! According to their reference implementations, the way you are supposed to use lexicons is to autogenerate their json schema definitions and version them locally everywhere they are used. I can't express how baffling this is to me - like the atproto monorepo has a top level lexicons directory, and then their Makefile then goes through several of the subpackages calling each of their (separate) code generation scripts, resulting in local, vendored copies of each of the lexicons - and by copies of the lexicons i mean both generated code AND typescript interfaces AND an entire copy of the whole schema.
This is presumably because there are REFERENCES between lexicons EVEN WITHOUT those lexicons having a meaningful notion of location or dereferenceability - how would you know what 'app.bsky.feed.defs' is referring to unless you packaged and built all lexicons together? the method for resolving references literally requires them to all be locally present at runtime as far as i can tell, idk the lexicon code is unreadable to me.
There is no means of versioning, so "Once a schema is published, it can never change its constraints" and the only means of changing is to change its freaking name, so com.example.myLexicon.FinalFinalv2 is explicitly encouraged. The reference implementations repeatedly violate this, though, so whatever.
Again, there is no actual mechanism of "publishing" a schema, though, so it's completely unclear what that's supposed to mean - how do people know the schema has changed names since they just have it hardcoded in their clients?
and the entire spec documentation is just a bunch of harebrained ideas that amount to, as far as i can tell, just literally being JSON-Schema just different? And they compare it to RDF but there's literally nothing to compare there except for the absence of an explanation as to why they didn't just use JSON-LD. I literally cannot tell how this is supposed to work as an interoperability/extensibility layer if there is no means of resolving terms or lexicons and all definitions have to be known in advance.
@aud there is and has always been this whole "big graph server" idea that defines the protocol and increasingly looks like the makings of a powerful wizard class locked in a high tower with all the power kind of situation
Strange that lots of #academics on #bsky are not really engaging with anyone, except perhaps with few other academics and they just reposting their original twitter material. Huge majority anglo-american. Probably some of them are on #threads too.
Not sure what the actual point of such activity is all about though
By the way I'm just doing a bit of looking into bsky, once I finish that I'll be off!
@afouxenidis@fifilamoura
I had scoring values for a like, voting in polls, a retweet/quote-tweet and a reply. I had around 1.5 thousand followers on both platforms at the time but adjusted for exact counts.
Over 4-5 months, for my accounts saying the various random things about all sorts of topics that I say, the results were off the scale different. Such a massive difference in favour of Fedi that it was in the hundreds of times ahead and it got steadily worse over those 4-5 months.
@afouxenidis@fifilamoura
My conclusion was you have to have either a very niche following or topic expertise, or a very large following on Twitter, or your time is essentially worthless.
A mere handful of followers here on the #Fedi will provide you more interaction than thousands of followers would there.
#bsky is really interesting
fundamentally a dead virtual space, for Europeans at least (and even more so for academics)
Americans (USA) seem a bit more engaged
..only English-speaking users..
looks and feels like (early) #Twitter
buckets of accounts with no posts, some just with the odd re-post, or posts that are days or months old
some people (like here) are just re-posting the same material they have on Twitter
I'll post some more on bsky if there's anything new /1/ #tech#socialmedia
on pense ce qu'on veut de #bsky niveau contenu, mais #mastodon est bien plus solide techniquement
je l'ai pas dit mais scroller sur bsky est execrable ; après on peut imaginer que ça va s'améliorer, ou pas d'ailleurs, le scrolling sur #tumblr ne s'est jamais amélioré
@kypeli I’ve 6 available. I stopped giving them around because I also stopped using it. You can’t even create a simple keywords based filter to hide certain stuff.
@dannotdaniel yeah but Jack is almost completely uninvolved as far as I can tell. On the board but doing nothing. And I gather he wasn't exactly getting his hands dirty while CEO of twitter either. I suspect he was too far removed to really be able to advise on the nitty gritty.
Yeah like I don't think it's better than here by any stretch, I very rarely use bluesky, and yes it seems many miles away from starting a federation. It's lost its way. But I still don't think it's a crypto Nazi hotbed.
what is bluesky / bsky's business model. I don't see ads, I don't see premium? What's the product? am i the product? how am I the product? #bsky#bluesky
Friends of Friends (n+1) graph from a "relatively small account" in #bsky. Yeah network exploration can be massive due to hub accounts. I guess I need to refine the native #gephi plugin proposal to add more tuning to smooth the exploration.
