> Signal is hiring developers to build Rust libraries that help make private communication simple. If you care about code quality as much as you care about user privacy, you should fit right in.

Today in inscrutable error messages:

> (bad magic)

(I _do_ actually know what it meant, in context, but I still thought it was amusingly cryptic)

@nicofee You forgot
(3) fix it yourself
(4) pay someone (maybe the developers named in (1) ) to fix it

All I can do is kindly ask that if you are inviting people to Mastodon on other social media, Telegram groups or whatever else, please please use the page instead of linking to specifically. Thank you

Show thread


> You [inserted] something in my quote that I don't really agree to

Sorry about that! I guess I misunderstood you – would you like me to delete the toot?


> Both [spoofing a caller ID number and misdirecting a call] are subject to various MITM and spoofing attacks, to my knowledge not asymmetrically so.

I agree that they're both subject to attack, but disagree that there's no asymmetry.

My understanding is that it is much harder for an attacker to receive incoming calls for a bank's phone number than it is for an attacker to have their calls show the bank's number in caller ID.

The rest of this thread does a good job explaining why

Are there more FOSS-y alternatives to Twitch?


> so the router can just pass return data back to the previous hop,

Oh, I see.

So with this setup:

Router D gets data from Router C purporting the be *from* A and *to* Z.

D has to have a valid address for C (to route the return data) and Z (to route the connection) but doesn't need a valid address for A.

Thus, if C is malicious, the "from" spoofing works but the "to" spoofing wouldn't.

Is that about right?


> Because routers direct traffic towards its destination, but they don't care where it came from.

Yeah, that makes 100% sense for email. When a router gets a message from A and needs to send it on to C, it only needs to have an accurate address for C—A could be anywhere.

But for a call (or other bidirectional communication) I don't understand how that works. Once the call starts, data has to go both ways. Doesn't the router need both to know A's location to send data from C?

I have some ideas about ^^^^.

I know that caller ID was grafted on to the system much later, and there are obvious analogies to email headers – and I understand at least a bit about how spoofing there works.

But I'd be interested in hearing from anyone who has a bit more knowledge about telephony – which I know is more-or-less its own beast

Show thread

Security question:

If I call a phone number (say, the one on my debit card), I can be pretty sure that the person who answers actually owns that number.

On the other hand, if I _receive_ a phone call that purports to be from that phone number, I *can't* trust that the person on the other end actually controls the number (which is why it can often be a good idea to hang up and call back).

So here's the question: Why is the "to" information so much more reliable than the "from" info?


> Hi folks, as a newbie to I was wondering: is there any chance to reduce incoming toots to English and German.

Yep! If you go to Preferences > Other, you can select languages to filter on. This only applies to public timelines (local and federated; not your home timeline) but, as @jiminycricket mentioned, your home timeline is only people you've followed.

It's not perfect in detecting the language, but it's pretty good!

It's really frustrating to me! I'm trying to switch over Rhapsode's UI to C so I can have access to some necessary libraries, & I'm just getting segfaults!

They appear to happen upon returning from Haskell to C, but I'm not entirely clear what's triggering them. I'm not sure what else to do for debugging.

Can Haskellers please help?

Boosts please.

I'm rsyncing a large file to a remote server. It starts off fast, and then after about 5 seconds it drops to 500kB/s. I've tried with an without compression. Any ideas on how I can speed this up?


> I'm rsyncing a large file to a remote server. It starts off fast, and then after about 5 seconds it drops to 500kB/s. I've tried with an without compression. Any ideas on how I can speed this up?

Totally a shot in the dark, but it sounds almost like your Internet connection is being throttled

Maybe others will have different ideas, though


> Hold on, my boss is demanding on a meeting

Hope you have a productive one-on-one

All eyes on Zoom:

1⃣ Zoom will “probably” strip all tracking and cookies from its website
2⃣ All meetings will require password protection
3⃣ They'll consider open-sourcing Zoom’s code

Promising words. Now hope to see some action.


> github down lol

Hmm, still works where I am. Guess it's a partial outage

Hey, #German speakers, someone just told me that German doesn't really do euphemisms for taboo language, like damn -> darn or fuck -> fudge/frick in English.

Surely this can't be true? Can you think of any euphemisms?

Show more

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.