@mig5 I thought #OnionShare was maintaibed by @micahflee ?

There are also some treats for advanced users who want to run #OnionShare in headless mode: we documented how to run the CLI as a systemd unit file:

https://docs.onionshare.org/2.6.3/en/advanced.html#running-the-cli-as-a-systemd-unit-file

and we documented all the configuration settings, including for persistent onions:

https://docs.onionshare.org/2.6.3/en/advanced.html#configuration-file-parameters

https://docs.onionshare.org/2.6.3/en/advanced.html#configuration-file-parameters-for-persistent-onions

I gave some tips here on how to pre-generate an onion address, so you can do it all without ever needing the UI: https://github.com/onionshare/onionshare/issues/816#issuecomment-2664631149

@lispi314 @dalias @lauren

Not only that, but @signalapp being.located in #Trumpist #USA means they gotta have to follow said laws and that means if flexed upon using #FOSTA & #SESTA or god forbid made-up claims to commit #TransGenocide and prosecute #Trans minors and/or their parents and/or medical professionals, THIS WILL BLOW UP IN THEIR FACES like a grenade used as ball gag and fuse pulled!

• It's absolutely trivial to abuse #Govware #Backdoors and thus track people down. #Signal by design and architecture WILL BE COMPLICIT IN IT!

For comparison: @monocles doesn't demand #PII like a #PhoneNumber or anything at all and if you don't trust them either (which is fair - never trust anyone, neither Signal nor #monocles nor me!) you can not only choose from various providers but literally #SelfHost your own (even as an #OnionService on @torproject / #Tor) and thus have full control of all the comms.

• And I'd rather recommend @micahflee 's #OnionShare over Signal just because that's even simpler and basically "fully decentralized" and "#serverless" that it's even more flexible.https://onionshare.org

@cwebber yes, and we already have options for that:

• #IRC & #XMPP+#OMEMO, #Zulip, etc. for #Chat.

• #JitsiMeet, #WebCall and other #WebRTC-based comms.

• #Mumbke, #SIP and other #VoIP solutions.

• #OnionShare, #Wormhole, #oshi, #BitTorrent & #IPFS for #Filesharing.

• #Nextcloud et. al. for collaboration.

...

@wmd @miqokin also the same Issues are by my own experience are better solved via @torproject / #Tor, @guardianproject 's #Orbot & @micahflee 's #OnionShare just to name a few.

• Not to mention most #MobileNetworks illegally use #RFC1918 space like 10.0.0.0/8 for #CGNAT, intentionally bricking #VPN|s in order to force #progessionals and #businesses in way more expensive contracts as they need a "real" VPN for work...

@delta @leaf @n0iroh the closest "#serverless / #P2P" I've seen is #OnionShare [made by @micahflee]...

Tho I think the true #future will be #decentralized, #federated and similar to eMail...

• Personally #XMPP+#OMEMO is a good fit. I do think that #deltaChat's approach to using #PGP/MIME is good and can work even in more restrictive scenarios (i.e. corporations when #E2EE & #Messaging require indexed archives for compliance reasons!)...

@xoron I don't want to discourage you at all - in fact I think your goal is not just noble but also worth aspiring to.

• My recommendation is always to scout out existing solutions, protocols and standards and see if those can be salvaged / used and if not, reason why. #PGP/MIME may seem crusty but a good UI can make it easy. Same.goes for #OMEMO & #OTR...

But whatever you do, please "DO NOT DIY ENCRYPTION!"

• Instead delegate it to drop-in libraries (i.e. crypto++ for C++) that are well, maintained and getting audited.

Prioritize features early on and make a decision what you want and if/how these can be accomplished. If necessary, have different modes / functions one has to context-switch (i.e. videocalling can't work in an airgapped network unless your callers are in the same (W)LAN).

• If possible choose to stay platform-independent in terms of tech, so like #WebCall, #JitsiMeet, etc. you can simply package that up with nw.js... (Except if you need like a minimalist, (n)curses-style TUI tool like #enc)

User-test early on. Espechally with "#TechIlliterates", if you can.

• Focus on a #MVP (minimum viable product) early on.

Write #documentation early on since that'll remove headaches. And I don't just mean #CommentYourCode but go deep and explain in detail why you chose something. This will help not just you.

• In terms of "scouting existing solutions" I'd recommend to take a look not just at #JitsiMeet & #WebCall, but also #Briar, #ServalMesh, @monocles / #monoclesChat, @gajim / #gajim and @micahflee's #OnionShare.

Make yourself a list what you like and dislike from those.

• Same with #Linphone, @zulip / #Zulip, #WhatsApp, #Signal, #Threema and even #WeChat, #FacebookMessenger, #iMessage, #FaceTime and god forbid #Skype, #MicrosoftTeams as well as #Slack.

Don't be afraid if your #App can't tick all the boxes at first release. Rather feel free to slowly ibtegrate them.

Needless to say I do sincerely wish you good luck and only the best in terms of success.

@halva @lynn @signalapp @deilann

The problem is one needs to literally acquire a phone number and have access to it, and the demand of a phone number itself is bad. This makes it unnecessarily complex and expensive compared to using @monocles / #monoclesChat.
(Cuz if I've to pay to communicate, I might just choose a provider that isn't a #VC #MoneyBurningParty but a long-term sustainable solution based off #OpenStandards!)

• I'm sorry for your location. My sincere condolences!

Still, #Signal doesn't allow #SelfCustody of all the keys & #SelfHosting, which makes it vulnerable as a #proprietary #centralized, #SingleVendor & #SingleProvider solution.

• Just because @Mer__edith isn't having #Roskonmadnozr pointing a gun at her head doesn't mean she'd risk jail for a user when push comes to shove.

And with #CloudAct on one hand and #Trump wanting to "Speedrun Hitler", I'd not rely on Signal.

• The "Metadata" #FUD is just a marketing bs because Signal will comply with warrants, whereas nothing prevents me from buying a Thin client, setting up an #OnionService to tunnel everything over @torproject / #Tor and rig it to disconnect power if tampered with or upon command.

I have setup comms for critical operations (incl. helping people flee Russia!) and I'd rather choose #OnionShare over #Signal if #Metadata is a real concern.

• Internet Access, even in "P.R." #China, is something feasible to workout given the massive prevalence of public #WiFi. Also it's easier to spoof/anonymize a MAC than an #IMEI or even #IMSI, so making one dependent on #PhoneNumbers to even sign up is inherently bad!

You use @micahflee 's OnionShare to circumvent firewalls.

I use OnionShare because it's the easiest way to transmit large files without uploading them to a filehoster like oshi.

• We are not the same!

@mattblaze Remember:

• #Wiretapping IS the illicit activity!

The only winning move is to commit "#AssetDenial" and commit to untappable communications with proper #E2EE via @torproject / #Tor.

• @micahflee made #OnionShare which is basically the most idiot-proof way to communicate over Tor to this day!

https://onionshare.org

@BestGirlGrace I mean it's easy to get started with the former by opening up @micahflee 's nifty tool called #OnionShare...

https://onionshare.org
It's pretty awesome and easy to use...

@lmorchard @vkc nodds in agreement I'm flabberghasted by rising #MediaIlliteracy & #TechIlliteraxy despite things being easier to do than ever before.

• This ain't like 1999 where one had to buy a book to learn #HTML and be rich enough to afford #ADSL!

Nowadays even a cheap smartphie can host an #OnionService and stuff like #OnionShare even makes way easier...

• Not to mention how cheap simple #Webhosting and #VPSes and #ReburbishedHardware is these days...

@Skivling @jpaskaruk @james

Please understand as a maintainer of a project intended for many legitimately legal uses, I cannot help you with things like violating copyright.

Otherwise I'd be thrilled to get early feedback on #distrans but it's still quite early stage. I have sent a few large files around with it though. A 4G Kali ISO made it through intact.

It's currently only single-file and point-to-point, but resuming interrupted downloads and trackers are coming soon if I can find some happy fun #rust #hacking time.

I'm also considering a simple GUI that lets you send a file, #onionshare style...