https://mastodon
General Discussion
9
Posts
4
Posters
28
Views
-
@channyeintun the name might be a little confusing for people that are not aware of what the "next" stands for. Without that knowledge it implies your project is affiliated with Mastodon proper and that it's the direction in which it's heading. If I were a mastodon dev, I'd be slightly upset.
-
@channyeintun the name might be a little confusing for people that are not aware of what the "next" stands for. Without that knowledge it implies your project is affiliated with Mastodon proper and that it's the direction in which it's heading. If I were a mastodon dev, I'd be slightly upset.
@mariusor I am a Mastodon dev and I don't mind though. 😀
-
@mariusor I am a Mastodon dev and I don't mind though. 😀
@channyeintun OK, nevermind, I'll see myself out... 🚶♂️➡️
-
@channyeintun hey, I've noticed a pretty major security issue in your new app, relating to how you're interacting with OAuth. What's the best way to contact you.
-
@channyeintun hey, I've noticed a pretty major security issue in your new app, relating to how you're interacting with OAuth. What's the best way to contact you.
@thisismissem Could you create an issue on GitHub?
-
@thisismissem Could you create an issue on GitHub?
@channyeintun not for a security issue.
-
@channyeintun OK, nevermind, I'll see myself out... 🚶♂️➡️
@channyeintun@mastodon.social you're part of the Mastodon core team?
-
@julian No. I'm not. Just contributed like fixing typos. 😂
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@julian and the collection is always a flat-topped tree!
-
@julian "ordered collection" yes, but the question is how to fill the collection. currently i have a thread where i came to my deep 50 limit ,-) i will see what happens today, i hope.
And the other site is how the UI is interpreting the collection
and a collection is by a lsit of iri's or resolved iri's. there are a lot of possibilities ;-)
-
@naturzukunft2026@mastodon.social what's the problem? The context endpoint just resolves to a paginated ordered collection.
-
@smallcircles@social.coop Okay, we'll look into the list, and send pull requests!
-
@fedify @hongminhee I would be delighted if #fedify contributors would take a peek at the fediverse development curated list and propose a PR on how best to incorporate the changes to the project, now that the various #TypeScript packages have been modularized. That would be very helpful. And create an issue if the current list format is no good fit.
https://delightful.coding.social/delightful-fediverse-development/
-
Btw, just found the v2 release announcement of @fedify and that is a prime example on how, on the grassroots environment end of the spectrum we can maneuvre into better territory.
Kudos to the #fedify developers. Handing people tools they need to focus on solutions, and build without getting thrown into deep on-the-wire impl detail reeds to worry about.
That is the positive side of the equation. There's not only a big uptick in interest for the #SocialAPI i.e. #ActivityPub client-to-server, which offers new opportunity to correct course. But also are there more #FOSS projects focused on robust tool and library support for the 'Solution developer' stakeholder.
In the revamp of the delightful commons initiative, made possible with support of @nlnet I emphasized all these projects, while I de-emphasized the apps that are already doing good for themself, but contribute to further divergence from open standards.
https://delightful.coding.social
https://hollo.social/@fedify/019c8521-92ef-7d5f-be4d-c50eae575742
-
Though with regards to progress, there's a difference in both approaches.
At the #SolidProject side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.
While at #ActivityPub side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix #interoperability breakages.
The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.
-
Yes, I agree. Though the diagram is too simple to capture it well, it is important to identify the forces that are at play, and the mechanics that drive them, and to subsequently monitor where you are and where you want to be in the future. So timely action can be taken to make corrective actions.
For the #SolidProject ecosystem for instance they might have identified a minimum set of standards to adopt, with which reasonably powerful "MVP's of the Semantic web" could be approximated with. And focus on strong library and tool support for that in multiple programming environments. Instead you enter a jungle of open stardards in various stages of completion, and good luck go figure it out. Also they might've focused on actual movement building. Far-reaching innovative standards - a new paradigm for the web - aren't adopted by the boardroom of a company, but are introduced by devs who get excited by what see and how they are empowered. And persuade management.
