On Sun, 06 Oct 2024 19:33:59 +0200,
Kirill A. Korinsky wrote:
>
> On Sun, 06 Oct 2024 19:04:13 +0200,
> Omar Polo wrote:
> >
> > On 2024/10/06 16:52:39 +, Klemens Nanni wrote:
> > > 06.10.2024 19:40, Omar Polo пишет:
> > > > Thank you! I'm generally ok with these patches, provided that we
On Sun, 06 Oct 2024 19:04:13 +0200,
Omar Polo wrote:
>
> On 2024/10/06 16:52:39 +, Klemens Nanni wrote:
> > 06.10.2024 19:40, Omar Polo пишет:
> > > Thank you! I'm generally ok with these patches, provided that we remove
> > > net/utox while here. any oks to do so?
> >
> > If it is indeed
On 2024/10/06 16:52:39 +, Klemens Nanni wrote:
> 06.10.2024 19:40, Omar Polo пишет:
> > Thank you! I'm generally ok with these patches, provided that we remove
> > net/utox while here. any oks to do so?
>
> If it is indeed broken, by the update and/or deprecated upstream: OK kn.
it is bro
06.10.2024 19:40, Omar Polo пишет:
> Thank you! I'm generally ok with these patches, provided that we remove
> net/utox while here. any oks to do so?
If it is indeed broken, by the update and/or deprecated upstream: OK kn.
>
> one nit:
>
>> --- net/toxic/Makefile 6 May 2024 12:23:55 -0
On 2024/10/05 15:44:45 +0200, Kirill A. Korinsky wrote:
> On Sat, 05 Oct 2024 14:09:51 +0200,
> Klemens Nanni wrote:
> >
> > 05.10.2024 00:24, Kirill A. Korinsky пишет:
> > > ping.
> > >
> > > I'm using it for more than a month to chat with two contacts who insist to
> > > switch to this IM.
>
On Sat, 05 Oct 2024 14:09:51 +0200,
Klemens Nanni wrote:
>
> 05.10.2024 00:24, Kirill A. Korinsky пишет:
> > ping.
> >
> > I'm using it for more than a month to chat with two contacts who insist to
> > switch to this IM.
> >
> > It works well on -current.
> >
> > To make things easy I've re-in
05.10.2024 00:24, Kirill A. Korinsky пишет:
> ping.
>
> I'm using it for more than a month to chat with two contacts who insist to
> switch to this IM.
>
> It works well on -current.
>
> To make things easy I've re-inlinded both diffs.
Thanks, looks almost good port-wise, see inline.
>
> On S
ping.
I'm using it for more than a month to chat with two contacts who insist to
switch to this IM.
It works well on -current.
To make things easy I've re-inlinded both diffs.
On Sun, 22 Sep 2024 18:28:42 +0200,
Kirill A. Korinsky wrote:
>
> On Thu, 30 May 2024 20:18:22 +0200,
> Omar Polo wr
On Sun, 22 Sep 2024 23:56:28 +0200,
Kirill A. Korinsky wrote:
>
> But I not sure that it worth to make it because the project is archived,
> and both forks with some stars on github is on the same state.
>
I'd like to add that seems that Tox Handshake is Vulnerable to KCI
https://github.com/Tok
On Sun, 22 Sep 2024 19:39:32 +0200,
Omar Polo wrote:
>
> On 2024/09/22 18:28:42 +0200, Kirill A. Korinsky wrote:
> > On Thu, 30 May 2024 20:18:22 +0200,
> > Omar Polo wrote:
> > >
> > > sending both together since toxic 0.15.1 needs the latest toxcore as far
> > > as i can see. briefly tried,
On 2024/09/22 18:28:42 +0200, Kirill A. Korinsky wrote:
> On Thu, 30 May 2024 20:18:22 +0200,
> Omar Polo wrote:
> >
> > sending both together since toxic 0.15.1 needs the latest toxcore as far
> > as i can see. briefly tried, toxic seems to work but hangs on /quit
> > (still have to debug it),
On Thu, 30 May 2024 20:18:22 +0200,
Omar Polo wrote:
>
> sending both together since toxic 0.15.1 needs the latest toxcore as far
> as i can see. briefly tried, toxic seems to work but hangs on /quit
> (still have to debug it), utox (the other toxcore dep) doesn't seem to
> even connect.
>
> co
sending both together since toxic 0.15.1 needs the latest toxcore as far
as i can see. briefly tried, toxic seems to work but hangs on /quit
(still have to debug it), utox (the other toxcore dep) doesn't seem to
even connect.
could anyone test these more throughfully than me? my only contact
mov
13 matches
Mail list logo
