Re: [Tails-dev] Tor on Tails issue
check if this is really a Tor connection issue, or if this is caused by mac randomization. On 3/24/22 01:31, gunsales--- via Tails-dev wrote: I've been having technical issues with using Tor on Tails. When I try to connect to Tor on Tails with obsf4 bridges on my university's wifi Tor gets blocked. This isn't an issue when I use Tor on windows with the university's wifi so I'm not sure why this occurs. I'm not sure if I need a specific bridge that can by pass the firewall or if its a problem with the OS itself or the usb I am using. If you could tell me what might being going on and what I could do about it I'd be very glad to know. -- Sent with Tutanota, the secure & ad-free mailbox. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Install Signal in tails
> It installs ok and works but won't save when Tails is restarted What do you mean by that? It does not store your signal settings persistently, or that the installation itself is not persistently, meaning that on restart signal won't be installed. Do you get any error message? How did you install it? On 8/11/21 6:06 AM, Tropic wrote: Hi Tails Love your O/S. Im trying to install Signal but I cant get it to save in persistence. I have trawled the net looking for an answer but cant find anything It installs ok and works but wont save when Tails is restarted Thanks for your time Tropic ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] I'm planning to do user interviews for chat platforms
Because of frustration with the UX of jabber, I intend to conduct some user interviews with Tails users as a means to communicate the needs of given user group better to xmpp developers. I'm very busy, and I won't spend much time doing this. So it will take some time until done. If you have something that you wish me to include in the analysis that I'll communicate to xmpp developers, feel free to send me whatever you want. If you believe I'd better use that time to conduct user interviews about another communication platform, I will welcome this feedback. I'm considering Matrix as an alternative option. kind regards syster ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] considering XFCE over Gnome
(just to not cause any confusion to those reading: I'm not a Tails dev, only an advanced user) I always use old laptops, and Tails runs quite slow on them, and it's annoying. On my travel laptop it's close to impossible to use it actually. On the same laptop XFCE runs very smooth. I'm using such old laptops for those reasons: - I consider electronic waste a huge problem for the environment, so I use devices others would through away - I'm poor - when being on a protest camp or similar, laptops are often very old so that the economical damage police can cause by taking them away remains small. health considerations: - those old laptops heat up much moore while using Tails, resulting in evaporation of toxic gas, I think If you're about to build XFCE Tails version, I'd be keen to become a tester. I would highly appreciate the existence of such a version. (as long as my assumption is correct, that an XFCE version would run smoothly on old laptops) kind regards syster On 7/19/21 7:24 AM, Hans wrote: Hi folks, ok, I have understood, that it is not easy to install a windowmanager looking like MacOS or Windows. Also, you told me, you are using Gnome. Well, thinking about this, please allow me a very personal feedback: 1. The choice of using Gnome is IMO not very lucky. Gnome is big, Gnome is eating much ressources. 2. I would use LXDE or better XFCE, because they are very small and tiny. XFCE also has the advantage, to use the very fine package "kali-undercover", which let XFCE look like Windows10. 3. The lack of TAILS in 32-bit is a great disadvantage, because it can not be used on netbooks, like EEEPC or others. I believe, many people are using these still. However, I agree, that journalists today might use all 64-Bit notebooks. 4. Tails should be for everyone, so it should be small and tiny, so it can be run smoothly also on older hardware. I am sure, especially in poorer countries, people are not able, to buy the newest hardware. Last but not least: Thank you for the documentation, how to build tails. This will allow me, to build a tails version according to my own needs. Of course, there is also much to learn. Generally: Thank you all for the hard work - it is really needed and appreceated in this corrupt world! Best regards Hans ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] chat software for Tails
On 7/19/21 6:15 AM, intrigeri wrote: >I don't believe the XMPP ecosystem is good enough for our users > that we should spend time encouraging them to use it more. > Quite the opposite, actually. Personally I have lots of disappointment for the approaches xmpp development takes. On the other side, I'm even more disappointed by the other options available. What options do you consider preferable over xmpp? (if that is already documented I missed it) kind regards, syster. On 7/19/21 6:15 AM, intrigeri wrote: Hi, syster via Tails-dev (2021-07-17): The server that Tails is using for its official chat room, might become an entrance to xmpp for Tails user. Choosing a server that gives new user a pleasant experience should be preferred over a server that does not. Personally, I would prefer not to dedicate any effort into this sort of XMPP outreach, because: - I see the move we're going to make later this month as a temporary stop-gap measure, rather than as a long term endorsement of XMPP. There are chances we migrate away from XMPP entirely in the not-too-distant future. - I don't believe the XMPP ecosystem is good enough for our users that we should spend time encouraging them to use it more. Quite the opposite, actually. - We're talking about very, very few people here (Tails users who try, and manage to connect to our users mutual support chat room) ⇒ whatever we choose here, the impact is almost negligible. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: migrate our public chat rooms to another friendly XMPP server (#17956)
Ok, sounds good with me then. On 7/19/21 6:15 AM, intrigeri wrote: Hi, syster via Tails-dev (2021-07-17): The server that Tails is using for its official chat room, might become an entrance to xmpp for Tails user. Choosing a server that gives new user a pleasant experience should be preferred over a server that does not. Personally, I would prefer not to dedicate any effort into this sort of XMPP outreach, because: - I see the move we're going to make later this month as a temporary stop-gap measure, rather than as a long term endorsement of XMPP. There are chances we migrate away from XMPP entirely in the not-too-distant future. - I don't believe the XMPP ecosystem is good enough for our users that we should spend time encouraging them to use it more. Quite the opposite, actually. - We're talking about very, very few people here (Tails users who try, and manage to connect to our users mutual support chat room) ⇒ whatever we choose here, the impact is almost negligible. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: migrate our public chat rooms to another friendly XMPP server (#17956)
Hi, here some consideration that might gone unnoticed: The server that Tails is using for its official chat room, might become an entrance to xmpp for Tails user. Choosing a server that gives new user a pleasant experience should be preferred over a server that does not. The compliance tester says some XEP's that are recommended are missing. Some of them might not bring a feature to a Tails user, while others might. This is the test: https://compliance.conversations.im/server/esiliati.org/ A server that offers a landing page in multiple languages would be great too. I suggest to ask for feedback in c...@joinjabber.org (xmpp room), as the xmpp community should have more experience on matter regarding xmpp and should be happy to help out. If it is assumed that the server that hosts Tails official chat room will not be an entrance to xmpp for (new) Tails user, then the mentioned considerations can be ignored. kind regards, syster. July 12, 2021 12:34 PM, "intrigeri" wrote: > Hi, > > I've created public XMPP chatrooms at esiliati.org. This hosting > option came warmly recommended by boyska and its admins are happy to > host us. > > Please join this channel for a 1-week testing period: > > - Channel: tails-dev > - server: conference.esiliati.org > > If no obvious blocker has been identified by the end of the week, > next week I plan to: > > - make these chat rooms the official ones > > - set up authorization (affiliate & roles) so that a bunch of us can > do moderation work as needed > > - deprecate the chat rooms currently hosted at Riseup > > Cheers! > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Documentation about BIOS and firmware attacks
Hello :-) > Being a nice market, it is costly, hard to setup, and hard to find, > especially 100% blob free hardware. I am not sure more than a few > percents of the Tails audience would do the switch. If a user has this information, they might consider switching to libre/coreboot once their current labtop breaks, or for similar reason. > Therefore I don't think it would qualify as an actionable input/advice, > and so how relevant it would be to add it. Giving unactionable security > advises is a bad practice Personally speaking, I would feel more comfortable if I read that I can have the power if I need to mitigate that issue, rather then hoping all will go well. Obviously it makes sense to explain that this is extremely unlikely to be needed. It would also create more comfort to myself, if I read that the developers of the OS I need to trust in, also thought about how to mitigate such a rare attack. (btw: beside that I really like the new warning docs) On 6/27/21 10:05 PM, geb wrote: Hello, syster via Tails-dev: I've just been reading through the new /doc/about/warnings/. It includes "No operating system can protect against BIOS and firmware attacks" and explains why that is, followed by a suggestion how to reduce that issue. What I'm missing is a hint to use Libre/Coreboot as an option to prevent some of such attacks. (at least that is my assumption) https://tails.boum.org/doc/about/warnings/ I am not sure how relevant it would be here : libreboot/coreboot computers is mostly a niche market, in general and especially if you consider the few models that can run 100% without firmware. Being a nice market, it is costly, hard to setup, and hard to find, especially 100% blob free hardware. I am not sure more than a few percents of the Tails audience would do the switch. Therefore I don't think it would qualify as an actionable input/advice, and so how relevant it would be to add it. Giving unactionable security advises is a bad practice: If users an unable to do anything based on it, except noting there are solutions which are not available to them, it make just them feel less safe, powerless, and thus sad... :/ (I found the page being great regarding this last problem btw: it warns the users, but immediately after, slow down and either mentions solutions if actionable ones exist, either remind them there are unlikely to encounter those attacks in real life, and should not worry to much (which is nicer, but also true) :-) ) ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Documentation about BIOS and firmware attacks
I've just been reading through the new /doc/about/warnings/. It includes "No operating system can protect against BIOS and firmware attacks" and explains why that is, followed by a suggestion how to reduce that issue. What I'm missing is a hint to use Libre/Coreboot as an option to prevent some of such attacks. (at least that is my assumption) https://tails.boum.org/doc/about/warnings/ ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] NSA tails and closed code
What I always thought what would be nice: Having 2 versions of Tails. One pure and free, and one with proprietary code that is needed to run some hardware. If one has a wifi adapter that runs on free software, most if not all of the proprietary code that is included in Tails is of no use for that person, at least that's how I understand it. Such an wifi adapter can be be bought for the cost of an USB stick. On 6/14/21 10:01 AM, boyska wrote: Georg Koppen: anonym: Romper Stomper via Tails-dev: and why are there closed codes in “tails”? I guess you are referring to the firmwares required for hardware support? If we didn't ship these firmwares Tails would not run on most hardware. It's a necessary trade-off. Is there a list of those firmwares somewhere (I couldn't find anything on the Tails website about that topic after searching a bit) or is it "just" a Debian package taken 1:1 from upstream? https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-packageslists/tails-common.list#L247 this is the list of debian packages Tails installs to have firmwares ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] proposal/offer for hosting and bridging XMPP, IRC, Matrix - to deal with xmpp.riseup.net going away
Risesup is about to discontinue their XMPP service and with that, Tails MUCs. For the new set up my proposal is: Using XMPP, Matrix, IRC (and maybe Mattermost) at the same time and bridging the rooms. The hosting will be outsourced to a friendly collective by using one of the offers/suggestions we get through community feedback as seen here: https://fosstodon.org/@tails/105684244090696525 Currently there are IRC, Matrix and XMPP rooms, but they are not bridged. Advantage of bridging: - Those that offer support in a Matrix/IRC/XMPP room, will be able to offer it to all rooms that are bridged to the one they offer support. - everyone can use their favorite thing My offer: Once the requirements are clear, I can find a solution that will met it, present it and after arrange the hosting with a friendly collective. Process and workflow can change anytime on your request. If you believe something other then my offer is helpful, tell me. (this is also documented in this gitlab ticket: https://gitlab.tails.boum.org/tails/tails/-/issues/17956#note_164816) kind regards, syster. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] decentralized ethereum wallet
Your best chance to get it into Tails, is to have it available in the Debian stable repository first. If it is not in Debian stable, you're out of luck. Once it is in Debian stable, it's probably still unlikely. However interest in crypto currencies are increasing. The Monero community is currently working to get their wallet into Debian stable as a means to get a chance to land into Tails as a software installed by default. btw: once a package is in Debian stable, you can install it into Tails persistence with: sudo apt-get install package-name Take in mind that installing additional software can reduce the security of Tails and could even deanonymize you. February 12, 2021 8:02 AM, "Fanta" mailto:fa...@onionmail.org?to=%22Fanta%22%20)> wrote: hi guys is there any chance to see ethereum wallet with erc tokens available in tails like electrum bitcoin wallet? that would be great best regards ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] The future of monthly reports, 2021 edition [Was: Preparing the next monthly report]
Some inspiration for monthly reports can be the XMPP newsletter. I've done more contribution (even not much) to Tails then to XMPP, but I never contributed to Tails monthly reports but to the one of XMPP. some information about the XMPP report: How to contribute is easy accessible: https://xmpp.org/newsletter.html To contribute has an very easy entry point: - there's a MUC specific for that, where you can just drop a line. - there's a pad where you can add your contribution. - there's git for final report I don't know if there's something of value for Tails, since development and community in the XMPP ecosystem varies a lot from Tails (many independent projects using the same standard). February 4, 2021 8:56 AM, "intrigeri" wrote: > Hi, > > Thanks for expressing your feelings and sharing your plans! > > Historical context > == > > FWIW, here's what I remember from the last project-wide discussion on > this topic: > > - Our starting point was that in the past, very few people were > writing these reports. It was done from scratch, looking at Git > history, changelog, Redmine, etc. This work was very tedious. > At some point, the very few people who were doing this work wanted > to stop. > > - We decided to make everybody responsible for writing their bits of > report if they wanted, while the person assigned to a report "only" > has to coordinate & curate it, so that: > > - Curating takes much less time, and is now feasible by many more > community members (it does not require following All The Things > anymore) ⇒ the curating workload can be spread more evenly. > > - The writing workload can be spread more evenly. > > Analysis > > > Here's my analysis of how it went in practice wrt. our initial goals: > > - In terms of spreading the curating workload > > Apart of the aforementioned "very few people", a few community > members took responsibility for curating reports: > > - 2020: 2 people (5 reports) > - 2019: 3 people (5 reports) > - 2018: 4 people (5 reports) > - 2017: 3 people (6 reports) > > Thanks! > > I would say that on the "spreading the workload" aspect, this > attempt has only been partly successful: on the one hand there's > been more community involvement than in the past, which is great; > but on the other hand more than half of our reports are still > curated by the same 2-3 people, which is not sustainable at all, > so we're back to square one. > > - In terms of writing bits of reports > > As far as I can tell, very few people have been writing bits of > reports. There's a huge overlap between the set of people writing > their bits of reports and the set of curators. > > Also, since these very few people, put together, are members of > almost every Tails team, the contents has kept covering the vast > majority of our work. On the one hand, it's good because it means > our reports are not as incomplete as one may have feared. On the > other hand, it means the attempt to spread the writing workload > more evenly has totally failed. > > My conclusion is that overall, this new setup did not reach its goals: > the work is less tedious for sure, but most of the work is still done > by the same few people. In order to make this problem visible, I've > also de-assigned myself from 2021 curator roles. > > And now? > > > I still think these reports are very important in terms of "connecting > with the rest of the world"¹, which matters in terms of relationships > with our upstream & sibling projects, communication with our users, > and in terms of fundraising. So I would be sad to see these reports > stop for too long. > > I'm not up to trying yet another iteration of "everybody will do their > bits and the workload will be shared", aka. the community magic dust. > I need a more formal setup, that is sustainable without sajolida and > myself, and with clear roles that reflect the importance of these > reports to us. > > The first setup idea that I came up with: > > - technical writers act as writers and editors, i.e.: > > - use our internal team monthly reports to write good quality > contents, with a communication style that's consistent with the > rest of our communication (for example, shorter than this > email :]]] ) > > - define a strategy, e.g. in terms of frequency (it could be that > monthly is not the best, I dunno, I'm not trained at this kind > of communication) > > - welcome contributions from volunteers and decide what to do with > them > > - other teams share info, needs, expectations, and feedback with > technical writers about the intended audience they have in mind for > these reports (e.g. FT about Debian & Tor people, fundraising about > potential donors, etc.) > > At this point this is meant to be half a proposal, half a conversation > trigger. Perhaps you disagree with my assumptions and goals? > Perhaps you have other ideas? > > Also, this proposal is clearly not perfect. For example, in an >
Re: [Tails-dev] Preparing the next monthly report
I just want to tell you, that I enjoyed reading these reports. While I was new to Tails, it also was part of building trust by seeing it's active and transparent development and its regular and professional documentation. It played also a role in motivating me to do a bit of support. February 3, 2021 9:11 PM, "sajolida" wrote: > Tails: > >> The person who volunteered to curate the report will >> help coordinate, patch, and rephrase things but will not be able to go >> through every possible source of information (including what's in your >> head). > > I volunteered to curate the January report some weeks ago but I withdraw > myself today. I'm seriously overworked with the UX sprint until February > 15 and in Tails in general. > > I've curated ⅔ of reports since 2017 but I won't curate them anymore. > > This monthly report dynamics has been recurrently frustrating for me. > What I envisioned as a way of communicating within the project, > connecting with the rest of the world, and celebrating our achievements, > has felt broken for me for years. I've put a lot of energy in the past > to try to change this but I don't have this energy anymore. I'll find > elsewhere the information that I need from them. > > -- > sajolida > Tails — https://tails.boum.org > UX · Fundraising · Technical Writing > > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] selling merch as Tails while outsourcing the effort - some concrete ideas
I'm in a position, where I have at one point time to be committed to offer support to Tails, and then from one moment to the other it can change being offline for months. Being the contact person will fail sooner or later. where help by core is needed: contact Person: Being the contact person the collectives/company can reach out if they need to. This should happen rarely. An email list for this would be good. I can respond when I have time, and others when I don't. Agreements: I can be the person to collect/document potential agreements. Final say needs to have core. tax: Uniformed opinion: Maybe you need to send the collective(s) some paper. temporal final decision on process: At one point there needs to be made a decision about the exact process that I'm going to propose. So it will require some time by core to think through the proposal, have a discussion and form a decision. core help not really needed: research: I'll do that. If one has ideas, I'm happy to listen. Design: We have this already, aren't we? New Designs: Outsourcing by asking community. If this will bring nice results, we have more designs otherwise not. Money: You have a bank one can send cash to. You have crypto coins. Job done? Webpage implementation: I suck at doing things with code. Thought I should be able to create a MVP. After all it's not more then presenting Products and linking them to the pages people can get it and doing some documentation. If I fail doing MVP, I'll try to go the route of outsourcing this task to the community. Maybe I'll do this anyway, even if it's just for trying how it will work out. Merge request and fixing small errors should be the only task for core team here. Can't tell if I forgot something. Did I? January 20, 2021 9:03 AM, "intrigeri" wrote: > Hi, > > syster via Tails-dev (2021-01-19): > >> Question: >> You want me to dick deeper into this topic, reaching out to more collectives >> and document my >> findings? I can help to make the idea of selling merch more concrete, >> thought I only continue >> furthering my investigation if there is general interest in the approach I'm >> taking and if it seems >> likely that Tails will offer merch, if the result of the research is >> positive (whatever that >> means). > > I like your approach. > > I greatly appreciate that you're aiming for a setup that minimizes the > amount of work required by core Tails workers. Thanks for this! > > Before I can form an opinion, I need to better understand what work > this would require, that can't be outsourced and that you are not in > a position to commit to yourself. Is this something you could clarify? > > Cheers! > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] selling merch as Tails while outsourcing the effort - some concrete ideas
A while ago someone asked in the email list weather it was ever considered to do some of the fundraising through selling merch. That brought me to think about how this could be done for Tails. With the following I'll share my thoughts: While Tails needs a solution that won't take resources that could actually used to make Tails better, outsourcing should be part of the solution. While Tails aims to protect its personas, it should take those values also in consideration while selling merch. (example: Tails aims to help people to escape domestic violence. Selling t-shirts produced by forced labor is against this value) While capitalism makes it difficult to produce under fair and environmental friendly conditions, we should at least work towards that goal. In short what needs to be taken into account: - only very little effort for Tails - respectful to values Tails tries to protect and represent There are collectives/companies that offer "selling merch as a service". Some more respectful to values Tails tries to protect and represent, others less. How could this look like? That's what I asked somewhere else and someone pointed me to the artist behind Pepper (a comic series that is purely created with free software). They start their merch selling page with a short intro how everything works, and then listening their products and a link where one can get it. That link guides you then to the webpage of the company/collective that offers "selling merch as a service". To better understand what I'm speaking about, take a look here: https://www.davidrevoy.com/static9/shop Just to get this discussion more concrete I reached out to few collectives (wait did I actually sent out all the emails, or just to one, cause I only got reply by one...I'll find that out) so that shipping can be closer to the spot something is ordered to. The one that replied back (unfortunate their focus is german market, but not limited to that) did so with positive feedback. They state to be happy to list Tails among their "soli projects", meaning they can do printing and distribution of merch and donate parts of that back to Tails. Just to know a bit about their political affiliation, here some other soli projects that they support: - systemli (tech collective to provide activists and anyone that needs it with online tools to help them organize) - Heyva Sor a Kurdistanê (similiar to what you might know as red cross, to support people and communities living around a country known as Kurdistan. Heyva Sor operates also where every other similar organization drops out for fear of their safety) - Internationalist Commune (an umbrella for "internationalists" from all over the world to organize together in support of countering terrorism and to struggle for environmental protection, feminism, democratic confederalism... ...and more. Just to give an impression. Their webpage is this: https://black-mosquito.org/ Their clothes are from different manufactures, coming with different "eco-lables". Some are in closer relation and support with the workers others not. Thought some have complete transparent production chain. I haven't looked much into it, thought there are anyway not really any better option offered anywhere else. It's either the same/similar or much worse. Question: You want me to dick deeper into this topic, reaching out to more collectives and document my findings? I can help to make the idea of selling merch more concrete, thought I only continue furthering my investigation if there is general interest in the approach I'm taking and if it seems likely that Tails will offer merch, if the result of the research is positive (whatever that means). ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] bridging XMPP and IRC
This can be solved by bridging IRC and XMPP. No need to choose one over the other. >> I would've greatly preferred an IRC option, since I more generally use >> that. I only set up XMPP to chat with tails developers when I needed >> it, but it was useful when I did use it. >> >> If possible, I'd love to see a public chat option preserved for >> precisely the reasons intrigeri mentioned. >> >> In any event, keep up the great work! Hopefully I'll find some time to >> contribute again this year :). >> -- >> -Austin >> GPG: 267B CC1F 053F 0749 (expires 2021/02/18) > > really shortly, > > I find also usefull xmpp chat for contact quick of tails devs, and > because I like more than others 1000 newer instant messaging solutions. hugs > > ignifugo > >> ___ >> Tails-dev mailing list >> Tails-dev@boum.org >> https://www.autistici.org/mailman/listinfo/tails-dev >> To unsubscribe from this list, send an empty email to >> tails-dev-unsubscr...@boum.org. > > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://www.autistici.org/mailman/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
