IRC channel logs

<ocdtrekkie>I saw a timezone aware competitor to Framadate I really want to package for Sandstorm, because time zones are awful.

<isd>Jacob Weisz: do it!

<isd>Anyway, the time shift doesn't affect my availability

<isd>Jacob Weisz: also, link to the app?

<ocdtrekkie> https://github.com/lukevella/rallly

<ocdtrekkie>And yeah, the time of these is never super ideal for me, an hour in either direction doesn't change that much. ;)

<tsyesika>I'm also able to do an hour in either direction, I just wanted to bring it up since it wasn't discussed in the meeting :)

<tsyesika>also a timezone aware date polling tool would be great

<Zarutian_iPad>h’lo there

<Zarutian_iPad>so, I was not in yesterdays meeting (scheduling conflict)

<tsyesika>hey Zarutian_iPad

<Zarutian_iPad>ocapn uris were discussed and Alan did fill us friam folks in

<tsyesika>the draft minutes are up if you want to catch up on the discussions

<tsyesika> https://github.com/ocapn/ocapn/pull/35

<Zarutian_iPad>we discussed sturdyrefs, eq, equaliance and migrating objects keepiing their object identities

<tsyesika>the next meeting should be on the 24th of march but I'm not too sure what the time is due to DST

<Zarutian_iPad>“Daylights Savings Fund - why not save some sunshine for a rainy day? literally”

<tsyesika>I heard the eu was planning to scrap it but I've not heard anything about that for a few years

<tsyesika>anyway it was an interesting meeting, lots of good discussion about URIs

<Zarutian_iPad>ACTION lives in the only country that observes UTC consistenly

<Zarutian_iPad>so one thing brought up this friam was that sturdyrefs and their uri form are used for two purposes

<Zarutian_iPad>intro and re-enliven

<ocdtrekkie>The US also has various levels of government trying to toss DST

<ocdtrekkie>But apparently we make it hard to implement good ideas in our legal system.

<isd>The US senate passed a bill this past fall to get rid of it... and then the house just didn't take up the bill.

<Zarutian_iPad>the former is about out if band introduction while the latter is abot re-establishing prior liverefs

<ocdtrekkie>The Senate passing it was a weird fluke thing

<ocdtrekkie>It didn't actually have the support to pass but did anyways

<Zarutian_iPad>tsyesika: we must “pay” Jonathan Rees in Rees Cups for his chairmanship of ocapn

<tsyesika>sounds like an idea :)

<tsyesika>maybe some US folks can arrange that xD

<Zarutian_iPad> https://github.com/ocapn/ocapn/pull/35/files#diff-b306706da7e840156398aa89b6d5ffd43d0fe559f43b34da33787a530c78132dR135-L135 line 135

<Zarutian_iPad>re URIs, they are not only meant for browsers but to tag kinds of textual data

<tsyesika>anyway I'd be interested in having more discussions about ocapn sturdyref like things in another meeting, I think I agree with the sentiment last meeting that we need to figure out how they'll used and what they need to contain before discussing syntax

<Zarutian_iPad>for instance see tel: , geo: , data: and isbn:

<Zarutian_iPad>another is sms: which is nifty as I have used an QR code with such for smartphone equiped folks to use when the local hackerspace doorbell broke

<Zarutian_iPad>line 143: markm makes a good point, re the intro usage vs the re-enliven usage

<Zarutian_iPad>uri used for the former whilist sturdyref for the latter

<Zarutian_iPad>ACTION wonders how http://soft.vub.ac.be/amop/start might fit into it with their AmbientRefs to services, more Una like perhaps

<Zarutian_iPad>ACTION cought up on the meeting notes

<Zarutian_iPad>cwebber: https://github.com/ocapn/ocapn/issues/29#issuecomment-1433214633 the // was never part of the uri spec iirc, only the http uri spec

<Zarutian_iPad>one thing I want to continue to be able to is to write an ocapn uri/text-rep on a post it note or namecard and hand it to someone

<Zarutian_iPad>ACTION detests uri QR codes that do not follow the usual convention of having the url printed underneath

<cwebber>Zarutian_iPad: I thought when tsyesika and I looked at it that the URI spec did have those slashes in it

<cwebber>they could be removed but then technically it wouldn't be part of the address component or something

<Zarutian_iPad>uri ≠ url !

<Zarutian_iPad>universal resource identifier vs universal resource locator

<Zarutian_iPad>tel:+15554242 is perfectly valid uri

<isd>It seems like we do want these to be locators though.

<isd>(but I'm still kindof against them being URIs)

<Zarutian_iPad>ocapn:<base32 of syrup’ed structure> can work

<isd>Yeah, we'd talked about that but base64

<Zarutian_iPad>base32 as Douglas Crockford defined because of the above postit/namecard case

<cwebber>all urls are uris but not all uris are urls I thought

<Zarutian_iPad>indeed!

<Zarutian_iPad>isbn:978-9935-490-79-7 is an uri for example

<tsyesika>I am still wondering about the idea of the locator/uri/whatever being able to contain multiple different netlayer routing information

<Zarutian_iPad>though it is not a url

<Zarutian_iPad>tsyesika: in E those were called connection hints

<tsyesika>ACTION is thinking about for example a user having a chat application and wanting to share a sturdyref to this but it being able to be accessed over for example tor and websockets but the person sharing just wanting to give out this information without having to ask what type of client the other person is using

<Zarutian_iPad>nothing against having different netlayer routing info in there

<tsyesika>I can imagine when goblins gets web support through wasm, this could be a thing goblins would need

<Zarutian_iPad>not only one such endpoint per netlayer but multiple

<Zarutian_iPad>for instance, a websocket relay might be included

<isd>Yeah, I want to be have a list of possible connection options; made a comment to this effect in the github issue

<tsyesika>yep, your comment is what made me think about this :)

<Zarutian_iPad>markm pointed out the issue of using swissNum based object identifier re unveiled execution environs such as blockchains

<tsyesika>there could be other types, one type we've thought about in goblins is certificates too

<tsyesika>I think christine showed them briefly in the meeting

<Zarutian_iPad>in ActiveCapCerts the naming/designating an object is done via the handoff mechanism I lifted wholesale from Captp of E

<Zarutian_iPad>but the you need to name the principla public key you are giving the access of the object to

<Zarutian_iPad>christines cert plus privkey bearer ocapn uri iirc

<Zarutian_iPad>basically

<Zarutian_iPad>which incidentially can support a rather nifty thing indirectly: an Clueless Software Agent can carry the privkey as part of its encrypted payload, meaning that you can have a riddle for folks to solve, so to speak, to gain access to say a chatroom like tsyeskia said above

<Zarutian_iPad>bbl

IRC channel logs

2023-02-24.log