We started a new privacy podcast.
Hey, everyone. If you're looking for a fresh privacy podcast, we recently started a new one called Signal Jam.
Here's a bit about why we made Signal Jam and what we're hoping to do differently.
We even have preliminary ways for you to participate in the project, which you can read about here.
Feel free to connect with us on Proton, Tuta, Signal, or here on Lemmy. Looking forward to your feedback and thoughts!
Questa voce è stata modificata (1 mese fa)
like this
crozilla
in reply to signaljam • • •Welcome to Signal Jam!
Jay & Michaelsignaljam
in reply to crozilla • • •hddsx
in reply to crozilla • • •signaljam
in reply to hddsx • • •𝔽𝕩𝕠𝕞𝕥
in reply to signaljam • • •signaljam
in reply to 𝔽𝕩𝕠𝕞𝕥 • • •artyom
in reply to signaljam • • •signaljam
in reply to artyom • • •Thanks for the feedback and suggestion! I'll look into Auphonic a bit and maybe do some experimenting.
-M
crank0271
in reply to signaljam • • •signaljam
in reply to crank0271 • • •crank0271
in reply to signaljam • • •Well I just went down the rabbit hole to verify that my podcast app is simply that, and not tracking tons of data to send back to who knows where. I had been using Overcast but a few months ago changed to RSS Radio after reading a recommendation - perhaps on Reddit? RSS Radio now seems to be all but disavowed by both Dorada Software, who links from the site for it, and Maple Media Apps, LLC, who is the publisher on the app store. The app privacy cards on the iOS App Store do not instill a ton of confidence, showing: Data Used to Track You (Identifiers, Usage Data) and Data Linked to You (Usage Data)
Perhaps it's time to switch... Podverse is at least open source, although they track Usage Data and link Contact Info to you. But good ol' Overcast only has a card for Data Not Linked to You, which seems like a big improvement.
signaljam
in reply to crank0271 • • •Good on you for the thorough research, and I like your logic. Things change fast, and it's good to have backups in place. Overcast would probably be my choice if using iOS. I wish there were more open source and privacy-friendly versions available.
-M
artyom
in reply to crank0271 • • •crank0271
in reply to artyom • • •artyom
in reply to crank0271 • • •signaljam
in reply to crank0271 • • •No stress! I was on iOS for a really long time, mostly out of entrenched habits, and trepidation into jumping into something like GrapheneOS. However, I did end up making the switch to Graphene, and arguably with the most restrictive settings (no Google Play Services, no Aurora Store, etc.). There was a small learning curve, maybe about a week or so, but in hind sight, it's one of the best privacy decisions I've made to date. Feel free to reach out to me on Signal or one of emails if you have questions or want to talk more in depth about it!
-M
jinx
in reply to crank0271 • • •Anytime Podcast Player
anytimeplayer.appsignaljam
in reply to jinx • • •TimLovesTech
in reply to signaljam • • •Cool idea and will check it out later. I also found a small grammatical error.
I assume you would want to strike "try", but I suppose you could strike "strive" instead.
Edit - I made a word salad on a post about a grammatical error, go me!
signaljam
in reply to TimLovesTech • • •rutrum
in reply to signaljam • • •signaljam
in reply to rutrum • • •Appreciate the feedback! We care about producing quality rather than quantity. As I mentioned in our Welcome post, we don't view ourselves as content creators in the contemporary sense, and we don't want that associated pressure to constantly pump out new stuff. We hope the project gains enough international relevancy and appeal that we can bring in other contributors (which might result in more frequent episodes/posts), but for now, slow and steady is the goal.
-M
Blaze (he/him)
in reply to signaljam • • •Hello,
Thank you for sharing this, feel free to crosspost to !privacy@programming.dev for additional reach
signaljam
in reply to Blaze (he/him) • • •brownmustardminion
in reply to signaljam • • •signaljam
in reply to brownmustardminion • • •Hey, there— we're still open to it, but when we launch it depends on how much demand there is from the community. Realistically, we'll probably wait a few more episodes down the line before we start one. Out of curiosity, do you use Signal, Matrix, or other platforms you think we should consider?
-M
brownmustardminion
in reply to signaljam • • •signaljam
in reply to brownmustardminion • • •Totally respect the compartmentalization strategy. I'll chat with Jay about this... maybe we'll bump up the SimpleX timeline a bit.
We're trying to prioritize which platforms to start with since the project is so new. As we publish more content and resources, we're hoping they bring real value to the community, and in turn widen our audience. Once that happens, it would make more sense to open up more channels to accommodate more folks. One thing at a time 🙂
Arthur Besse
in reply to signaljam • • •stupid_asshole69 [none/use name]
in reply to Arthur Besse • • •I only read the signal link you posted, but the first link inside it complains that the signal server needs to know a users ip and that could be used to connect people and users. Ip addresses are required to send data. Ip obfuscation is insanely out of scope for a messenger.
The second link complains about sealed sender not failing closed which is true (or was true at the time) but also a reasonable compromise to prevent abuse and avoid it constantly failing and requiring new expirable tokens.
These are not reasons to not use or even not recommend signal. A person who is taking recommendations to increase their privacy should not be worried about those concerns.
Removing oneself from public records (or taking greater control over what surfaces in public records about oneself) is infinitely more important than expecting ip obfuscation or sealed sender from signal.
I am not making this reply to start an argument and will not engage in one. The point is to help readers understand that your concerns about signal are esoteric.
Arthur Besse
in reply to stupid_asshole69 [none/use name] • • •People are only expecting metadata protection (which is what "sealed sender", a term Signal themselves created, purports to do) because Signal dishonestly says they are providing it. The fact that they implemented this feature in their protocol is one of the reasons they should be distrusted.
stupid_asshole69 [none/use name]
in reply to Arthur Besse • • •For anyone reading along, that means people you send signal messages to can see your user account name maybe even if you click the button that’s supposed to make it not possible to do that.
Change your behavior accordingly.
Arthur Besse
in reply to stupid_asshole69 [none/use name] • • •No, it isn't about hiding your identity from the people you send messages to - it's about the server (and anyone with access to it) knowing who communicates with who, and when.
Michael Hayden (former director of both the NSA and CIA) famously acknowledged that they literally "kill people based on metadata"; from Snowden disclosures we know that they share this type of data with even 3rd-tier partner countries when it is politically beneficial.
Signal has long claimed that they don't record such metadata, but, since they outsource the keeping of their promises to Amazon, they decided they needed to make a stronger claim so they now claim that they can't record it because the sender is encrypted (so only the recipient knows who sent it). But, since they must know your IP anyway, from which you need to authenticate to receive messages, this is clearly security theater: Amazon (and any intelligence agency who can compel them, or compel an employee of theirs) can still trivially infer this metadata.
This would be less damaging if it was easy to have multiple Signal identities, but due to their insistence on requiring a phone number (which you no longer need to share with your contacts but must still share with the Amazon-hosted Signal server) most people have only one account which is strongly linked to many other facets of their online life.
Though few things make any attempt to protect metadata, anything without the phone number requirement is better than Signal. And Signal's dishonest incoherent-threat-model-having "sealed sender" is a gigantic red flag.
Video Clip of Former Director of NSA and CIA: “We Kill People Based on Metadata”
Ryan Goodman (Just Security)stupid_asshole69 [none/use name]
in reply to Arthur Besse • • •There’s a big difference between the metadata that the Snowden leaks are talking about and how they’re used and the metadata the signal server (or its subcontracted provider) has and how and under what conditions it’s able to be used.
The metadata that is the subject of the statement “we kill people based off metadata” is unencrypted cell phone signals and other broadly plaintext requests sent over a system that by design also includes location telemetry. That information could be easily obtained en masse through a man in the middle attack or through the lawful intercept backdoors built into the equipment that carries the information itself (which is less of a man in the middle attack and more of a man in the middle design).
This is different from the signal metadata both in form and content. The signal metadata is not vulnerable to a mitm attack and the agencies implicated in the Snowden leaks would have to actually go through the legal hoopla required in order to get just the metadata itself. Same as they would have to if they wanted the actual content.
Amazon does comply with law enforcement requests often without requiring a warrant, but the difference between requiring a request be made as opposed to simply being able to collect that metadata freely and package it as actionable intelligence is significant.
All messaging systems are vulnerable to this attack. If you send or receive a message then you, the other party and any intermediary like a server are subject to the laws of the places they’re physically located.
Again, I’m not arguing, I’m trying to make this very convoluted system clearer.
signaljam
in reply to Arthur Besse • • •Hey, Arthur— thanks for dropping these links. Jay and I will look at these and consider your thought process, and might reach out to follow up, if that's okay! If I may ask, what do you prefer for email and RTC?
-M
Arthur Besse
in reply to signaljam • • •For chat, something with e2ee and without phone numbers or centralized metadata. SimpleX, Matrix, XMPP, etc - each have their own problems, but at least they aren't centralizing everyone's metadata with a CIA contractor like Jeff Bezos like Signal is.
For email, I'd recommend finding small-to-medium-sized operators who seem both honest and competent. Anyone offering snakeoil privacy features such as browser-based e2ee is failing in at least one of those two categories.
signaljam
in reply to Arthur Besse • • •We're considering moving up our timeline on a SimpleX and Matrix chat as we've received interest from others about that, too. Keep an eye on our website or show notes as we'll update those when new chat channels open up.
As for email, are there specific providers you recommend we look at?
-M
geneva_convenience
in reply to Arthur Besse • • •twikz
in reply to geneva_convenience • • •Matrix is open source, should give that a try,
it could be a bit more user friendly tho
geneva_convenience
in reply to twikz • • •twikz
in reply to geneva_convenience • • •Matrix | Germany | Open source | Origins
element.iogeneva_convenience
in reply to twikz • • •No Matrix was developed by Amdocs, an Israeli company. It has moved to Europe afterwards (I recall UK but might be wrong about that part)
Element is a Matrix client.
ReversalHatchery
in reply to geneva_convenience • • •