I'm just watching a music video on YT with a live chat box beside it. Is this something we could do with #PeerTube, or a #LiveStream clone forked from it?
@xj9 remember that the whole idea of Git-based web forges is that nobody *has* to use them. If you are confident doing everything with the Git CLI, you can. AFAIK that's already true in GitLab, everything (not just code repos but issues trackers, wikis, etc) can be used directly through Git, with the appropriate permissions on the instance. As Drew quite rightly says, Git is already federated. What ForgeFed does is federate the web UI https://github.com/forgefed/forgefed/wiki/User-stories @BartG95@Wolf480pl@alcinnz
@jcbrand > having a healthy XMPP ecosystem is still important even without mass adoption.
Replace "XMPP" with "federated" and we are in total agreement. I'm just not convinced that the particular set of tech standardized by XMPP is the best tech for the job, and the growth of other federation standards seems to suggest it isn't, at least for some use cases. I've seen it described as a "heavy stack".
@Wolf480pl@alcinnz ... and if I don't own my own computer? If I'm a working class person in a developing country, trying to learn to code to lift myself out of poverty? Having it all work in a browser, under a single set of login credentials, could be the difference between whether that learning is available to me or not.
@Wolf480pl@alcinnz But ok, let's look at another situation. You're considering giving commit access to someone, or even handing over maintainership to them. Having a quick way to review someone's history of contributions is one way to reduce the likelihood of handing over commit access to someone who then uses it to insert malware, as discussed here: https://librelounge.org/episodes/episode-2-thanksgiving-npm-and-malware-in-free-software.html
@Wolf480pl doesn't that depend how complicated it is to review? What if you spends hours poring through the code, only to realize you're being trolled? This is much more likely in a federated environment than a silo, and one of the reasons some people mutter darkly about the wisdom of federating code forges at all. @alcinnz
@Zuph if not, I guess that UX is still a work in progress ;-P Moving on to the publishing side of things, when you say video embedding, for example, do you mean uploading video on Tumblr, then embedding it, or embedding it from a third-party host like YT?
@Zuph hmm. OK. The micro-blog apps seem to have a bias towards giving control over appearance to the user doing the viewing, as in the original vision of the web (separating display from content). For example, there are a few themes I can use to determine how #Pinafore looks while I'm browsing posts. Maybe the more bloggy apps (Hubzilla, Plume etc) might be interested in supporting this kind of theming? Have you looked at Doke.li?
I thought #GTalk was already dead, and that #Hangouts never supported #XMPP, because it's not compatible with what they wanted to do with #WebRTC. Was I wrong? In either case, yes, you can definitely carry on using XMPP withou gOgle. There's a list of suggested servers discussed here: https://ecodigital.social/@adfeno/101232941345420566
@z428 AP vs. Diaspora is more an accident of history. Diaspora forked the OStatus standard to add things like private messages, which AP supports. All the apps that support Diaspora federation are also implementing AP. Once that happens, and Diaspora s the only app that can't communicate with the #fediverse, I suspect they'll come around ;-) Or they'll be the tech equivalent of a Marxist party agitating inside a liberal democracy where all the other parties use the election protocol ;-)
@z428 the Matrix folks started off trying to implement XMPP, and they also experimented with IRC, and came to the conclusion that it was worth defining a new standard, so they could use modern, web native tools (eg JSON instead of XML?): https://matrix.org/docs/guides/faq.html#comparisons
@z428 I love #XKCD 927, but it vastly over-simplifies that protocols are intensely *political*. You could say that parliaments and elections are protocols for interoperability between political parties. In both cases, the ways the protocols are written can be heavily biases towards one party or another, and this is one reason why standards processes are so fraught, and standards proliferation happens.
Pre-election: we will establish a commuter rail service between Tamaki Makaurau and Waikato. Post-election: local bodies are establishing a commuter rail service between Tamaki Makaurau and Waikato. #HollowPromises#SortYourShitOut#NZLabour
Pre-election: will you legalize medical cannabis? "Absolutely, yes" Post-election: we won't prosecute you for using cannabis for medical purposes, if you're dying, but we will prosecute anyone who grows it for you if you're too ill to do it yourself #HollowPromises#SortYourShitOut#NZLabour
Pre-election: we will wipe all debt that beneficiaries are being forced to pay from times they needed emergency housing, and were put up in motels by WINZ at market rates Post-election: we will wipe any debt if a Review of Decision finds that its the result of a #WINZ mistake (ie exactly what would have happened under the previous government) #HollowPromises#SortYourShitOutLabour
@mlg > High population of people dependent on the outputs of the existing system for their day to day survival.
... and as we've already agreed a system that cannot continue as it is, for a whole range of reasons. But ok, let's try to stay out of the political wheel ruts that crisscross this area of discourse, and zero in on a particular resource that needs allocating, and how that is and could be done in practice. Dealer's choice.