@freemo @tetrislife @QOTO
And here we stumble upon the question of revolutionary change and legacy compatibility again ![]()
@freemo thanks. I was only asking about services on the same domain, for an instance like qoto.org.
sharing log-ins across domains/service providers is quite a leap, I only recently felt that I understood how Hubzilla's "nomadic" identity/OpenWebAuth works and it wasn't how I thought it works earlier.
That does suggest that free/open software developers could collaborate more. Hubzilla (and Friendica, and Diaspora) still have, say, their own events and calendars and photo album support, and Mastodon (and Mobilizon, and Pixelfed) have their own auth.
@QOTO I appreciate the variety of services qoto.org opens up (I appreciate nixnet, snopyta, ouvaton, disroot, frama* too). Becaise I also appreciate all-in-one solutions like Hubzilla and public hubs, I was wondering if the one log-in can be used for all of qoto.org's services.
What bothers you more -- the suggestion that programming=#javascript or the mis-alignment of the answers?
Getting Started on Nyxt Hacking https://nyxt.atlas.engineer/article/getting-started-on-nyxt-hacking-1-bookmarklet.org | https://lobste.rs/s/dlpe2s #browsers #emacs #lisp
@shapr @clacke reminds me of claims that caffeine.js.org (live-coding Squeak on JS) had support for broadcasting changes https://thiscontext.com/2019/12/02/naiad-progress-2019-12-02-online-team-services/
@beli3ver I guess having a fallback option of outsourcing it again might be useful. So, something self-hostable like the ODOO project that has support providers?
@deshipu@mastodon.technology @kensanata what percentage of maintainers read the developers' code comments, deliberately and placing trust in it? it is a small percentage in my experience. whereas code with useful symbol names would read a bit better and not need the crutches of likely stale comments.
Executable specs a.k.a tests are a more useful way to communicate intent. and you could go to town commenting the test code because there is no implementation detail to distract from them being read.