Am 18.03.25 um 22:37 schrieb Christoph Liebender:
> Am 18.03.25 um 12:59 schrieb Stuart Henderson:
>> On 2025/03/17 20:37, Christoph Liebender wrote:
>>> Am 17.03.25 um 19:08 schrieb Stuart Henderson:
>>>> On 2025/03/17 18:43, Christoph Liebender wrote:
>>>>> Am 04.03.25 um 17:12 schrieb Christoph Liebender:
>>>>>> Am 03.03.25 um 10:50 schrieb Stuart Henderson:
>>>>>>> On 2025/03/01 19:47, Christoph Liebender wrote:
>>>>>>>> Comments, ok?
>>>>>>>
>>>>>>> the readme should follow the template used in other ports, see
>>>>>>> /usr/ports/infrastructure/templates
>>>>>>>
>>>>>>> I don't have time to look further today
>>>>>>
>>>>>> I've made the readme follow the template. I've also shortened it a 
>>>>>> bit
>>>>>> for it to be more concise. It is attached.
>>>>>
>>>>> I added myself in the MAINTAINER tag as per suggestion in the net/ 
>>>>> wstunnel
>>>>> update to 10.1.10 . Attached as tarball.
>>>>
>>>> I took a look at the readme but it doesn't really have enough
>>>> information to get it working by itself. Then I looked through the
>>>> readme via https://github.com/mollyim/mollysocket and it's not very
>>>> well structured, has a lot of references to irrelevant Linux-only
>>>> things, and is lacking information too - it talks about "the Android
>>>> app" but doesn't say where to get it and my searches in play store
>>>> just return irrelevant things. A simple step by step would be quite
>>>> helpful.
>>>
>>> Well, what kind of person should the README be written for? Someone 
>>> who has
>>> never heard about Molly and just stumbled accross mollysocket in the 
>>> ports
>>> tree?
>>
>> That sounds about right to me. At least enough for people to 1) figure
>> 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!

• mollysocket.tar.gz (24K)