ππ»π There's a new beta for Surf available on TestFlight and Google Play.
General Discussion
1
Posts
1
Posters
1
Views
-
ππ»π There's a new beta for Surf available on TestFlight and Google Play. As well as the usual performance improvements and bug fixes, we've made some updates to the Surf Shop. Tap Discover Feeds in your sidebar to check out what's new and find inspiration for when you create your own feeds.
#SurfFeeds #Flipboard #ActivityPub #ATProto #OpenSocial #Apps #Technology #Tech
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@evan @julian @darius @dmitri IMHO what's best for fellow implementers and end-users, and most fair to those who took risk to implement the specification as agreed upon, is:
WE DO NOT BREAK USERSPACE[0]Linus' diction in that footnote is not great, but the principle is. It stands up for all implementers, not just rich/big ones. That's leadership in protocol development. Instead some of our leaders have not only been breaking userspace, but doing it for hire.
[0]: https://lore.kernel.org/all/CA+55aFy98A+LJK4+GWMcbzaa1zsPBRo76q+ioEjbx-uaMKH6Uw@mail.gmail.com/
-
@evan @julian @darius @dmitri This is not only about fairness and openness, but even moreso about backwards compatibility and not changing the conformance classes in a way that will effectively 'fork' ActivityPub. Which is why I emailed you Jan 16, 2024 with concerns about the changes to normative references in your draft (no reply). A WG is ONLY needed to make non normative changes affecting conformance classes like you've authored into your draft.
-
@darius @evan @julian I made the point in SWICG meeting years ago. W3C staff seemed to agree. https://github.com/w3c/strategy/issues/435#issuecomment-2065436813
There's no reason to keep repeating the half truth because it sounds true, but it's not, so it has clearly caused confusion. If that's the only reason we have a WG, we don't need one. There are other reasons.
There has not been CG consensus on a request to republish AP, and this is a way of venue shopping to a much smaller consensus group.
-
Darius, that's only partially true. Per policy, CG cannot publish normative specifications. It's NOT true that "only a WG can". S6.2.6 explicitly describes how AP can be updated without a WG. It requires W3C staff help, and requires backwards compatibility. Clarifying and improving the spec has always been possible without a WG, but not if W3C staff obstructs it, and not when insiders are determined to publish breaking changes despite lack of consensus in CG.
-
@julian @darius @dmitri I think @bengo has brought a lot of healthy skepticism to the CG and WG chartering efforts over the last few years. I'm glad he's worked so hard on this, and I hope he continues to make sure that processes stay open and fair.
-
@julian @darius That's not the case!
@dmitri do you have the link for the meeting notes from last Friday? They'd be really helpful for this conversation.
EDIT: Found em in my history! https://hedgedoc.socialweb.coop/MoKSsjLPRwyDoDpKodH_mQ?edit
-
@evan @julian @bengo As chair of the new working group: I want as much work as possible done in the (community oriented, open) CG. I want the CG to bring proposals to the WG and I want the WG to reach out to the CG when we have needs.
The WG exists because W3C policy states that a CG cannot publish normative W3C specifications, only a (Members-only) WG can. I'm going to do the best I can to make the WG run as openly as possible within the framework handed to me.
