That is uncalled for and just common. Toms comments were constructive and
topic specific. Sure, showing some frustration as we all have from time to
time, but your comment was just common thug personal attack and has no place
here. In fact I do not see where you have offered a single thing
On Tuesday, February 20, 2018 at 10:27:24 AM UTC-5, Tom Zander wrote:
> So, knowing that your API is actually based on 8-bit characters and not 7
> bits which you are limiting yourself to, my suggestion is to take something
> above 127 and below 256 as a special char.
> Most fun one would be
On Wednesday, February 21, 2018 at 5:41:41 PM UTC+1, qubenix wrote:
> > So let me be blunt as this is likely the last email from me to qubes
> anyway;
>
> Bye, I'm happy to see you go away finally. It was killing me inside that
> you were working on the new gui controller. Fuck off back to bcash.
On 02/21/2018 05:41 PM, qubenix wrote:
>> So let me be blunt as this is likely the last email from me to qubes
> anyway;
>
> Bye, I'm happy to see you go away finally. It was killing me inside that
> you were working on the new gui controller. Fuck off back to bcash.
>
I really hope that you
On Wed, February 21, 2018 4:41 pm, qubenix wrote:
>> So let me be blunt as this is likely the last email from me to qubes
>>
> anyway;
>
> Bye, I'm happy to see you go away finally. It was killing me inside that
> you were working on the new gui controller. Fuck off back to bcash.
Tom had some
> So let me be blunt as this is likely the last email from me to qubes
anyway;
Bye, I'm happy to see you go away finally. It was killing me inside that
you were working on the new gui controller. Fuck off back to bcash.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received
On Wednesday, 21 February 2018 12:12:06 CET Wojtek Porczyk wrote:
> This is bad UX.
This is frustrating, I spent too many emails making the point clear that
this is an API level escape token. Not a user-visible one, and then you
respond to the thread showing you still completely missed that.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Feb 20, 2018 at 04:27:16PM +0100, Tom Zander wrote:
> On Tuesday, 20 February 2018 14:04:03 CET Wojtek Porczyk wrote:
> > On Tue, Feb 20, 2018 at 01:21:30PM +0100, 'Tom Zander' via qubes-devel
> wrote:
> > > On Tuesday, 20 February 2018
On Tuesday, 20 February 2018 19:41:19 CET Marek Marczykowski-Górecki wrote:
> > On the 'other' side of qrexec (on dom0) you have perfect control over
> > the
> > situation and you also don't have any need for recoding or encodings or
> > anything like that. It still is just 8 bits data, not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Feb 20, 2018 at 06:57:34PM +0100, Tom Zander wrote:
> On Tuesday, 20 February 2018 16:54:36 CET Marek Marczykowski-Górecki wrote:
> > > The thing you have to rememeber is that the escape character never needs
> > > to be typed by the user.
>
On Tuesday, 20 February 2018 16:54:36 CET Marek Marczykowski-Górecki wrote:
> > The thing you have to rememeber is that the escape character never needs
> > to be typed by the user.
> > In QRexec you are defining an API, applications like qvm-run are using
> > that API. What the user passes into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Feb 20, 2018 at 04:27:16PM +0100, 'Tom Zander' via qubes-devel wrote:
> On Tuesday, 20 February 2018 14:04:03 CET Wojtek Porczyk wrote:
> > On Tue, Feb 20, 2018 at 01:21:30PM +0100, 'Tom Zander' via qubes-devel
> wrote:
> > > On Tuesday, 20
On Tuesday, 20 February 2018 14:04:03 CET Wojtek Porczyk wrote:
> On Tue, Feb 20, 2018 at 01:21:30PM +0100, 'Tom Zander' via qubes-devel
wrote:
> > On Tuesday, 20 February 2018 01:49:37 CET Marek Marczykowski-Górecki
wrote:
> > > We've decided to deprecate the '$' character from qrexec-related
>
13 matches
Mail list logo
