12:53 <mnutt> is there anything I need to do WRT reviewing the davros 0.27.1 sandstorm submission?

12:54 <mnutt> it's not a critical update so there's no pressure, just wanted to make sure someone saw it and address any issues if there are any

13:22 <JacobWeisz[m]> I saw it, I opened an issue on a UI quirk but I haven't sat down and tested the usual stuff yet.

13:23 <JacobWeisz[m]> App approval backlogging is always my fault.

13:27 <JacobWeisz[m]> mnutt, is there any reason the update might've turned web publishing off?

13:31 <JacobWeisz[m]> So, to clarify, upgrading doesn't make the web publishing stop, but web publishing is switched off after upgrading on the UI. So it's still published but the UI says it's not.

13:36 <JacobWeisz[m]> It just looks like maybe the UI always has web publishing disabled when you open a grain, even if it's enabled.

14:10 <mnutt> no worries, I'll take a look! I need to stay more on top of the github issues

15:19 <blowfist> abliss1: did you fix anon connect on your matrix app?

15:49 <abliss1> i have anon connect working, but not back-connecting (to check the public key), so it still can't receive federation messages

15:49 <abliss1> hoping to wire up ian's proxy today.

15:50 <JacobWeisz[m]> abliss, I meant to ask at the office hours, are you going to look at adding the published feeds to Ian's version of TTRSS?

15:57 <abliss1> i can do so if it's desired; the change is quite small.but i realized its usefulness is limited unless we also add an easier way for users to create short dns aliases to their static publishing urls.

16:03 <abliss1> so that's the next thing i want to look at after i get the matrix prototype federating. i think for all these social/federated apps, in order for it to work well, we need some kind of user-friendly dns solution

16:05 <abliss1> because in every case, you're going to want to expose a url (to your rss feed) or a handle (to your matrix server) in a way that is portable, so that if you want to switch your server impl to a different grain or a different app, you need to be able to repoint your domain to the new location.

16:08 <abliss1> i think the sandstorm architecture lends itself to a nice compromise within Zooko's triangle. if the admin can hand out subdomain ranges to individual users (e.g. *_abliss.sandstorm.rapidraven.com), then a simple meteor ui can let each user assign arbitrary tokens within their subdomain space to any grain's static publishing (or a particular webkey's api)

16:17 <abliss1> it means the user has to trust the admin not to reassign the range out from under them. but this feels reasonable; if the user really wants more security, they can go buy their own domain name for $10 and manage the txt record themselves.

17:36 <JacobWeisz[m]> I would use it with web publishing personally, FWIW.

17:37 <JacobWeisz[m]> If Matrix or ActivityPub or whathaveyou is implemented as a system grain, mind you, Sandstorm users wouldn't need their own DNS space for those.

17:37 <JacobWeisz[m]> Though it would still be nice for web publishing direct from a Sandstorm server.