IRC channel logs
2025-12-07.log
back to list of logs
<acrow>Is there a spritely community solution for a dojo (community workout room) that already exists? Because a day in the library could save years of coding... <acrow>I may be under the influence of cwebber's reality distortion field but enabling instructors to keep class attendance and setup or cancel a class with notifications doesn't seem like a far reach for goblins especially if hoot is involved. I expect a steep learning curve to result. <cwebber>acrow: you could definitely build it! but it's definitely also currently something we don't have a "here's how to line up all the pieces" tutorial for all the web stuff. that's getting better, tsyesika is about to put out a blogpost that's a step towards how to use Goblins + web stuff <cwebber>for now, you'd probably want to look at the pumpkin-chat repo and how it works for some things, but even then it's not a production application, that's internal dogfood <acrow>cwebber: Thank you. Internal dogfood is golden to me! <cwebber>Dave's Brassica Chat may also be interesting, it uses propagators-based FRP <cwebber>but it also has a bunch of other curious things in it like CRDTs what might be a distraction <acrow>cwebber: Our community is small -- I hope that eases some of the 'production' quality concerns. We currently buy a product for this but have no visibility into security; we only appraise ease of use and reliability. <acrow>Small means we aspire to having 100 people. bbdb could be a backend. <acrow>ACTION dreams of federating all global dojo's <dthompson>I still want to do that goblins-based issue tracker that we discussed at SeaGL a couple years ago <acrow>ACTION waves at dthompson while reading his papers <dthompson>tsyesika's http bridge to goblins will be helpful for this <dthompson>as well as our upcoming "sleepy actors" feature <cwebber>yeah both of those will be huge, esp when combined <cwebber>basically it turns goblins into a web framework <cwebber>including a storage system with hot caching <acrow>dthompson: you remember that! Funny, I was looking at the code this morning. <cwebber>but you're on your own for the indexing (for now) ;) <acrow>dthompson: I improved on the version you saw but it's still a small thing. I recall stopping when I was not prepared to address the lack of remote-ip in (web request), I think. It was marked as <fixme> for apparently good reason. <acrow>There is a huge security issue there but ease of use is more important to this group than the privacy of our stocks of washclothes. I'm ok with cracker's attempting to hold this data for ransom. <dthompson>I don't recall what your issue was with remote ip addresses <acrow>I wanted to use the remote-ip's as a, very rough, proxy for user identity. <acrow>Avoiding the issue of authentication and authorization. <cwebber>it may be better to use goblins' ocap features for the authorization stuff! <cwebber>and may be that hopefully it feels fairly intuitive <dthompson>yeah I think the simplest thing to do that's reasonably safe is to give each user a capability URL to access the system <acrow>doesn't that tie users to having a google account? Key users have apple accounts. ;? <identity>like, not a, just a link that has credentials attached as a parameter <dthompson>leave all the account stuff aside. I just mean that google docs allows you to generate a URL that you can share with someone to give them read or write access to the document <dthompson>by sharing the URL with someone you have given them the capability to access the document <dthompson>the url contains an unguessable token that the server maps to some amount of privilege in the system <dthompson>if each person has a unique url to log in then you can have accountability and revocation <acrow>So, the peoples just bookmark a complex url that gives them access. Or, provides a ?key=<blah> query string. <dthompson>I'm not sure how you had planned to keep people out of your app before but the capability url approach would keep out anyone who doesn't have such a url <acrow>ACTION I love the idea. Implementation is technically within my reach -- Making it work with the masses (well, about 30 of them) is a try, try again exercise. I'll see what I can do. <acrow>Our group is small enough that the honor system is workable. <acrow>I think it could be enough to make it a group access situation where I create one obscure url path and then ask people to append their name in a query string. In production I know that's ridiculous but ... one step at a time. Again -- washcloth count is difficult to weaponize. <dthompson>you could but I'm gonna advise against it :) <acrow>dthompson -- as you can now see -- :) Anyone is welcome in my app. Anyone with malicious intent probably could bribe a politician with less effort and greater gain. <acrow>Not that I'm encouraging such chicanery.... <acrow>ACTION Returns to re-reading core of spritely. :) <acrow>Keep up the good work -- I'm always thrilled to read about what you are up to -- it's always good! On that topic I wondered if any of you are travelling this spring to Bellingham? <dthompson>the only conference we have plans to attend right now is FOSDEM <acrow>and FOSDEM will be awesome -- one of these years I'll make guix days, I hope. <acrow>Am I the only mere mortal person wondering when every.org allows me to use Zelle? <acrow>Zelle is an instant and entirely free (financially) money transfer system provided by many banks and credit unions (like mine). I used it last night to pay for silent auction items I had bought from a charity. Venmo is similar but instead of just transferring your money to others venmo holds onto it long enough to make short term market plays for internal gain. Check zelle out. <acrow>Yeah, not sure, but maybe that could be why guix and others also seem to present only their 'less desirable' options. I ultimately may have to consort with other, poorer, options. <acrow>dthompson: Regarding the issue tracker in goblins -- I think, the framework for that is good. What I think you are pointing out is that we need an onboarding/registration front end to establish an initial contact with users and provide them with capability urls. <acrow>Oh, I see! Much better... I'll work on this. Thanks.