On Wed, Mar 19, 2025 at 11:18:12AM +0000, Stuart Henderson wrote: > On 2025/03/18 22:39, Christoph Liebender wrote: > > > > out whether it's useful for them, and 2) get an idea of what, other than > > > > mollysocket, they need to use in order to run it. > > > > > > Alright then. Revised and more detailed version is attached. > > > > > > > then, they need to know if their push server supports a VAPID key > > > > (whatever that is) and generate if necessary, authorize it to the push > > > > server somehow, work out what to put in allowed_endpoints for their > > > > choice of push server, does that sound about right? > > > > > > I'm pretty sure that the VAPID-key is an implementation detail - there > > > is no need for a user to know what it is. The only required thing is > > > that it stays secret as well as constant. When changed, every client's > > > Molly app needs to be reconfigured. > > > > > > In any case, every user might generate it when setting up their instance > > > of mollysocket. I don't think there is a problem with that. > > > > > Whoops! it is attached now! > > Thanks - that's just the sort of thing I had in mind. I have some small > nitpicky format tweaks for README but it would be simpler to do that by > sending a small diff after import. > > Any OKs, or would anyone like to import with ok sthen? >
Needs the usual NOT_FOR_ARCHS for ring consumers and HOMEPAGE can be dropped since it's the default provided by GH_*. Otherwise this looks good portswise - I haven't really looked at the README since you did. ok tb to import
