Re: NEW: net/mollysocket

2025-03-19 Thread Christoph Liebender
Am 19.03.25 um 13:25 schrieb Stuart Henderson: On 2025/03/19 11:18, Stuart Henderson wrote: 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

Re: NEW: net/mollysocket

2025-03-19 Thread Stuart Henderson
On 2025/03/19 11:18, Stuart Henderson wrote: > 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? Now impo

Re: NEW: net/mollysocket

2025-03-19 Thread Stuart Henderson
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 pu

Re: NEW: net/mollysocket

2025-03-19 Thread Theo Buehler
On Wed, Mar 19, 2025 at 11:18:12AM +, 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

Re: NEW: net/mollysocket

2025-03-18 Thread Christoph Liebender
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

Re: NEW: net/mollysocket

2025-03-18 Thread 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 20

Re: NEW: net/mollysocket

2025-03-18 Thread 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, Christop

Re: NEW: net/mollysocket

2025-03-17 Thread Christoph Liebender
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

Re: NEW: net/mollysocket

2025-03-17 Thread 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,

Re: NEW: net/mollysocket

2025-03-17 Thread Christoph Liebender
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

Re: NEW: net/mollysocket

2025-03-04 Thread 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

Re: NEW: net/mollysocket

2025-03-03 Thread 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

Re: NEW: net/mollysocket

2025-03-01 Thread Christoph Liebender
Am 25.02.25 um 16:55 schrieb Christoph Liebender: Thanks for your comments. I've integrated your suggestions in the attached tarball. - christoph diff --git a/net/mollysocket/Makefile b/net/mollysocket/Makefile index 8fcee423108..8c07fa3c296 100644 --- a/net/mollysocket/Makefile +++ b/net/moll

Re: NEW: net/mollysocket

2025-02-25 Thread Christoph Liebender
Thanks for your comments. I've integrated your suggestions in the attached tarball. - christoph diff --git a/net/mollysocket/Makefile b/net/mollysocket/Makefile index 8fcee423108..8c07fa3c296 100644 --- a/net/mollysocket/Makefile +++ b/net/mollysocket/Makefile @@ -1,6 +1,8 @@ COMMENT =

Re: NEW: net/mollysocket

2025-02-25 Thread Stuart Henderson
On 2025/02/25 12:18, Christoph Liebender wrote: > Hi ports@, > > I've come up with a port for: > >     https://github.com/mollyim/mollysocket . > > Essentially, it makes it possible to use Signal on your phone with > UnifiedPush > instead of Google FCM / Sockets. Portroach doesn't handle DIST_T

NEW: net/mollysocket

2025-02-25 Thread Christoph Liebender
Hi ports@, I've come up with a port for:     https://github.com/mollyim/mollysocket . Essentially, it makes it possible to use Signal on your phone with UnifiedPush instead of Google FCM / Sockets. infrastructure/db/user.list changes: --- a/infrastructure/db/user.list +++ b/infrastructure/d