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? I'd say the motivation is like this: established Molly users 
learn about the possibility of ditching Google notifications, are 
interested in implementing that with their server / VPS box, and 
discover the OpenBSD port. Then, the README supplies OpenBSD specific 
info for setup.

Sure, in the end you'd need some kind of relayd/nginx reverse proxy 
setup in front of mollysocket that terminates TLS, but isn't that out of 
scope? Especially because there is the possibility to run mollysocket in 
airgapped mode, without any reverse-proxy in front.

Adding a link to Molly in the README, sure, that can be done. For your 
reference, Molly is not available on the Playstore nor F-Droid, you need 
to resort to one of their distribution channels:
	https://molly.im/get.html

What is the scope on READMEs? Or: where does it say what the scope is?