In the current situation, and in the short term, I believe, it is no little possible to allow Bluetooth, yes I use mouse (with a dongle, in the Tails), keyboard, and headphones with Bluetooth. I hope that the security with the Bluetooth improved in the next few months, yes at some point will be propitious and auspicious use Bluetooth at the Tails.
> -------- Original Message --------
> Subject: Tails-ux Digest, Vol 39, Issue 10
> Local Time: September 14, 2017 10:00 AM
> UTC Time: September 14, 2017 10:00 AM
> From: tails-ux-request@???
> To: tails-ux@???
>
> Send Tails-ux mailing list submissions to
> tails-ux@???
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mailman.boum.org/listinfo/tails-ux
> or, via email, send a message with subject or body "help" to
> tails-ux-request@???
>
> You can reach the person managing the list at
> tails-ux-owner@???
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tails-ux digest..."
>
> Today"s Topics:
>
> 1. Re: Wireframes for DAVE 2 (sajolida)
> 2. Re: Wireframes for DAVE 2 (sajolida)
> 3. Re: Wireframes for DAVE 2 (anonym)
> 4. Improving our Bluetooth trade-off (intrigeri)
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 13 Sep 2017 15:54:00 +0000
> From: sajolida <sajolida@???>
> To: Tails user experience & user interface design <tails-ux@???>
> Subject: Re: [Tails-ux] Wireframes for DAVE 2
> Message-ID: <4307e774-f2ca-6379-3765-6a6af359ce74@???>
> Content-Type: text/plain; charset=utf-8
>
> sajolida:
>> I would like you to review the initial wireframes that I created for
>> DAVE 2. See https://tails.boum.org/blueprint/DAVE_2.
>
> Ah, and the deadline is by the end of the week (Sunday) because I want
> to be looking for people to test them starting on Monday.
>
> ------------------------------
>
> Message: 2
> Date: Wed, 13 Sep 2017 17:01:00 +0000
> From: sajolida <sajolida@???>
> To: Tails user experience & user interface design <tails-ux@???>,
> Uzair Farooq <uzairfarooq11@???>, anonym <anonym@???>
> Subject: Re: [Tails-ux] Wireframes for DAVE 2
> Message-ID: <fe9a0e82-44db-6ec1-1c87-7bf4e2acd8a5@???>
> Content-Type: text/plain; charset=utf-8
>
> Now putting anonym and Uzair in copy since they are not subscribed to
> this list.
>
> anonym, Uzair: I just sent some wireframe for the now download page.
> Feel free to have a look:
>
> https://mailman.boum.org/pipermail/tails-ux/2017-September/003450.html
>
> But I have some more technical questions:
>
> - I want to change some content on the page after the download has
> started but before the verification is done. See "Skip verification"
> in moving_parts_1.pdf.
>
> At this point the user might not have the add-on installed so that
> requires some additional JavaScript on the page (we can add it to
> /install/inc/js/dave.js).
>
> My question is what kind of trigger we can use to change this
> content: is there a way from inside the page to know when the
> download of the ISO image started or when it has finished?
>
> Otherwise do you think that piggybacking on detecting a click on the
> download button is the best we can do?
>
> - Until now the name of the add-on and its description was "Tails
> Download and Verify" but now the extension won"t do the download
> anymore. So I should at least propose some rewording to improve that.
> But I wanted to ask you how hard it would be to change:
>
> - The display name of the add-on, maybe from
> "Tails Download and Verify" to "Verify Tails Download" or something
> like that.
>
> - The URL in AMO, currently
> https://addons.mozilla.org/en-US/firefox/addon/tails-download-and-verify/.
> But if that"s not trivial we shouldn"t bother :)
>
> - For people without JavaScript I wanted you to confirm that even with
> Web Extension and in Chrome they would still be able to use the
> add-on. To keep the same mechanism that we"re using now: if there is
> no JS, then we show people a button to directly download the XPI and
> they can still use it.
>
> And now in terms of process:
>
> - I created Redmine tickets for the big steps of the migration.
>
> See the subtasks on https://labs.riseup.net/code/issues/12328.
>
> Uzair: It would be super helpful if you could create yourself an
> account on Redmine so we can assign some tickets to you.
>
> We have some doc about how we use Redmine on our website but ask me
> if in doubt:
>
> https://tails.boum.org/contribute/working_together/Redmine/
>
> - In terms of budget, adding little bits of work here and there, we
> might ask Uzair to do more work than planned initially so I just
> wanted to make it clear that we"re open to extending the budget that
> you gave us to cover more work as we go asking for more. We"d rather
> pay a bit more and get more work done than stick with what we agreed
> upon and feel limited.
>
> ------------------------------
>
> Message: 3
> Date: Wed, 13 Sep 2017 18:15:00 +0000
> From: anonym <anonym@???>
> To: sajolida <sajolida@???>, Tails user experience & user
> interface design <tails-ux@???>, Uzair Farooq
> <uzairfarooq11@???>
> Subject: Re: [Tails-ux] Wireframes for DAVE 2
> Message-ID: <a9b79a6c-c17d-9bd8-2cba-7796e2e10eb2@???>
> Content-Type: text/plain; charset=utf-8
>
> sajolida:
>> Now putting anonym and Uzair in copy since they are not subscribed to
>> this list.
>>
>> anonym, Uzair: I just sent some wireframe for the now download page.
>> Feel free to have a look:
>>
>> https://mailman.boum.org/pipermail/tails-ux/2017-September/003450.html
>
> I like it!
>
>> But I have some more technical questions:
>
> I"ll defer completely to Uzair here -- he"s the expert!
>
>> - Until now the name of the add-on and its description was "Tails
>> Download and Verify" but now the extension won"t do the download
>> anymore. So I should at least propose some rewording to improve that.
>> But I wanted to ask you how hard it would be to change:
> [...]> - The URL in AMO, currently
>> https://addons.mozilla.org/en-US/firefox/addon/tails-download-and-verify/.
>> But if that"s not trivial we shouldn"t bother :)
>
> If you don"t know this, Uzair, I"ll look this up.
>
>> And now in terms of process:
>
> And here I don"t really have anything to say, except...
>
>> Uzair: It would be super helpful if you could create yourself an
>> account on Redmine so we can assign some tickets to you.
>
> ... that this indeed would be helpful, but no pressure! We do most of our communication there, and it seems to work quite a lot better than email. :)
>
> Cheers!
>
> ------------------------------
>
> Message: 4
> Date: Thu, 14 Sep 2017 11:33:08 +0200
> From: intrigeri <intrigeri@???>
> To: tails-ux@???
> Subject: [Tails-ux] Improving our Bluetooth trade-off
> Message-ID: <858thhhbfv.fsf@???>
> Content-Type: text/plain
>
> Hi,
>
> [deadline: September 23]
>
> Currently one can"t use Bluetooth in Tails without going through
> manual operations that 1. are not documented; 2. can only be performed
> in the GNOME session (which implies that e.g. one can"t use
> a Bluetooth keyboard in the Greeter anyway). So in short, we support
> Bluetooth usage neither officially, nor effectively (except for
> technical users who want to use things like Bluetooth speakers and
> will manage to make it work).
>
> But Bluetooth is not fully disabled at the lower level, so our users
> are exposed to security vulnerabilities in the Linux Bluetooth stack
> such as BlueBorne (https://www.armis.com/blueborne/), which forced me
> to think about this topic urgently today.
>
> I think this current trade-off is pretty bad for most Tails users: it
> makes them vulnerable, without providing them anything useful
> in exchange.
>
> I propose we:
>
> 1. Short-term: fully disable Bluetooth (#14655, I"ll probably get my
> branch merged today so 3.2~rc1 is safe vs. BlueBorne, but we can
> revert this change in 3.2 final if it"s not OK). As explained
> above, this should not impact UX much.
>
> 2. Mid-term: document how to re-enable Bluetooth in the GNOME session
> and with Additional Software Packages (see commits 4fa1c46,
> 613b14c, 3d53d2c and 9320ca7 for inspiration).
>
> 3. Long-term: better support Bluetooth (e.g. #10801 + persistence of
> Greeter settings).
>
> Don"t get me wrong! I"m convinced that at some point, we do need to
> support Bluetooth properly: our current userbase might be dedicated
> and motivated enough to deal with limitations like "I can"t use my
> Bluetooth speakers and there"s no wired speakers around so well I"ll
> watch this video with my crappy laptop integrated speakers", but if we
> want Tails to have a greater impact we should probably make it work
> nicely for people who won"t want to use a tool that breaks such common
> use cases.
>
> Cheers,
> --
> intrigeri
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Tails-ux mailing list
> Tails-ux@???
> https://mailman.boum.org/listinfo/tails-ux
>
> ------------------------------
>
> End of Tails-ux Digest, Vol 39, Issue 10
> ****************************************
