kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 240 seconds]
frigginglorious1 is now known as frigginglorious
<abliss>
any hope of prefx (or regex) filter permissions?
<isd>
What do you mean specifically?
<isd>
(Just pushed another updated spk to the same URL. it doesn't pull in the default feeds anymore)
<JacobWeisz[m]>
Related to that: I was tempted to pop open an issue about an API to offer a user demo data/experience on their first run/grain of a given app.
<isd>
feel free to open an issue. Can discuss details on the tracker.
<isd>
...I should factor out some of the internals of docker-spk into a library; it would be nice to have library support for manipulating spks.
<isd>
(I'm mentally chewing on the design of a hypothetical nix-spk, because I want better reproducibility)
strugee has quit [Ping timeout: 240 seconds]
strugee has joined #sandstorm
<abliss>
what I mean is that it would be nice to give a grain access to anything under https://example.com/* , or to be able to give a grain access to http* just once
<isd>
The former is what the latest iteration does.
<isd>
I agree the latter would be nice for some circumstances.
<isd>
I am however nervous about making it anything but an admin-only option, as otherwise I fear app developers will abuse it just because it's the path of least resistence, even if there is a sensible design for their app that doesn't need it.
<isd>
abliss: what did you need to do (if anything) to get the API clients working?
<isd>
Got the mobile app working.
<isd>
spk at the above url is updated, if others want to play with it.
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
frigginglorious has quit [Ping timeout: 240 seconds]
<abliss>
yeah, the only thing i had to do was change the img onload tag to a different img url.
_whitelogger has joined #sandstorm
<JacobWeisz[m]>
I mean, fun fact to Kevin's comment on the feature idea, technically one could use the Powerbox to connect a Sandstorm app to a licensing server.
frigginglorious has joined #sandstorm
<isd>
ocdtrekkie: yeah, I mean there are always going to be clever things an app author can do to be annoying.
<isd>
But I think exposing to apps whether they are the only grain is an additional information leak that users should be able to plug if they so chose.
<isd>
choose
<JacobWeisz[m]>
That is fair. It just seems a particularly obscure setting.
<isd>
I've been thinking lately about the notion of settings that apply to all of a user's grains of a particular app. They would be useful in some circumstances
<isd>
e.g. it's kinda silly that with Sandcal the user's timezone is set per-grain. I guess ideally Sandstorm would just handle that, but I wonder if there are other cases where it might make sense for a user to be able to set "default settings" for grains of a particular type.
<JacobWeisz[m]>
That may just be a good profile setting for Sandstorm to have and then share.
<JacobWeisz[m]>
Similar to (love those HTTP APIs), display name and preferred pronoun.
<JacobWeisz[m]>
Many apps can use your time zone, I recall BabyBuddy had to patch a fix in for setting that in the UI for Sandstorm.
<isd>
Yeah, maybe we should just push that into core.
<JacobWeisz[m]>
I occasionally feel like there's a good body of common profile settings we don't support that apps would make good use of.
<JacobWeisz[m]>
Presumably the big thing is to ensure they are optional or provide a good default, such that choosing to not set something works, and setting it is deciding you are okay sharing it with apps.
<JacobWeisz[m]>
(Time zone probably should default to either the server's time zone or UTC)
<JacobWeisz[m]>
#3391 is my first take on an app review guide/market policy for thoughts and opinions.
<isd>
Reviewing now
<isd>
Re: time zone, probably looking at the client's utc offset in the browser might provide a reasonable default.
<isd>
Annoyingly you can't actually get a symoblic name, but we could e.g. default it to UTC-5, which would be close enough to not be horribly broken out of the box.
<isd>
Maybe we could also keep track of whether it's been set explicitly, so if the user doesn't have a setting it just feeds the app the UTC offset it detects at the time.
<JacobWeisz[m]>
If browsers already can pass it to websites we probably should try to use that, same as we do for i18n.
<JacobWeisz[m]>
Although, like i18n, I think we should have a setting in profile to set it explicitly too.
<isd>
They only do UTC offset, which isn't really sufficient for what SandCal is trying to do.
<isd>
You really need a symbolic name.
<isd>
But using the utc offset is maybe a good default value for us to use.
<JacobWeisz[m]>
Yeah, I know any different country might do different stupid time zone things.
<JacobWeisz[m]>
And "browser default" is a good "not set" setting for the Sandstorm profile probably.
<JacobWeisz[m]>
If you try to implement this, expect me to bug you to also do the i18n one. ;)
<isd>
Upgrading from the old TTRSS app seems to work.
<isd>
(if I change the app id to match)
<ill_logic>
We doing the meeting? I can set it up again.
<ill_logic>
Also Jacob Weisz do you want your server log still in the notes from last time?
<ill_logic>
There's no context to it so I don't know if it was a temporary thing.
<JacobWeisz[m]>
Probably toss it out
<JacobWeisz[m]>
Mostly was just there to show Kenton, but I don't think it captures anything super sensitive there?
<isd>
If others want to meet I will join in.
<JacobWeisz[m]>
I left the grain up so Ian and Kenton can revisit that log if they want, but there's no good reason for it to be in the public notes probably.
<JacobWeisz[m]>
I have not much to discuss other than saying I'd like more community opinions on #3391 since I am going to revise at some point here.
<ill_logic>
I still don't have anything to add.
<JacobWeisz[m]>
(Market behavior is arguably whatever Kenton says it should be, but it's a valuable discussion on people's expectations of the market at minimum?)
<ill_logic>
Okay. So Jacob Weisz worth doing now or skip to next week? I remember we were considering slowing meetings down to match the pace of reasons to have them.
<JacobWeisz[m]>
If it's just Ian and I and you, we should table it.
<JacobWeisz[m]>
Cuz everything we're working on is in plain text in this chat log.
<abliss>
i should be able to join.
<abliss>
would be good to discuss the future of ttrss
<isd>
I think that might make sense, yeah.
<JacobWeisz[m]>
Okay. I am excited about the future of TTRSS.
<isd>
Let's put that on the agenda.
<ill_logic>
okay so it's on then? I have the email ready to send.
<ill_logic>
(given abliss joining)
<ill_logic>
or do you still mean for next week?
<isd>
SGTM. Note that abliss had trouble joining via phone last week, so you may want to mention that's a potential issue.
<abliss>
i meant tonight.
<JacobWeisz[m]>
We can do tonight, sounds like there's four of us.