Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

I think we have vastly enough material to criticize Russia, we don't need more.

Our societies are already convinced those are dictatorships.

But it took Snowden and Assange to show us how deeply messed up our societies are.

It's very possible they are both Russian assets, but what they reported have been verified, and we needed to know it.

The way you are reacting is close to a religious interpretation of the world. It's not us VS them. It's not a football match.

We have a society to build, and it's been taken from us, one piece at a time. If we don't want to end up like Russia, we need all info we can get.

And given the huge price they paid for it, yes, I consider them heroes. And I think history will remember them as such.


Chat apps are hard, this doesn't strike me as a proof of bad quality as many competitors had such bugs.

And Telegram has been so far the most reliable, feature full and easy to use chat app I have had to use.


Which other chat app has displayed messages to the wrong users? That seems like one of the worst things a chat app could possibly ever do.



Wow, I'm truly baffled! Is this a rite of passage for instant messenger developers!?


Or OS developers. Video codec developers. Network stack developer. Driver developers. Web browser developers. Web service developers. Office suite developers.

And if you are a developer and your software is used in any decent scale, you are unlikely to be the exception.



Wow, touche

And in an Apples-to-Apples comparison, WhatsApp fared far worse than Telegram on privacy, and not to mention its parent company.

The only benefit I can think of WhatsApp has is claiming to be encrypted by default. So I dont need to press an extra button. I just have to take their word for it.


> And in an Apples-to-Apples comparison, WhatsApp fared far worse than Telegram on privacy, and not to mention its parent company.

I'd like to see that comparison. Considering that WhatsApp is end-to-end encrypted, and Telegram persistently stores almost all of their users' messages on their backend in a way that lets them read them, I find that very hard to believe.

> So I dont need to press an extra button.

Nobody presses an extra button, especially not one that opts you out of multi-device support.


Whatsapp is not open source and facebook was part of the PRISM program.

I don't think it's reasonable to expect them to actually be e2e encrypted.

Espacially since Zuckerberg has many years of poor track record for privacy, and made the famous quote "they trust me the dumb fucks"


So we have one app that claims to be end-to-end encrypted and is under intense scrutiny of security researchers across the world, and another one that's provably not encrypted and stores everything server side. Which one should I use?


I don't care that the russian spy on my messages, I care that my gov does.

Russian can't affect my life as much as my gov.


Exactly! Good points. Facebook’s been caught spying on you with audio, video, contacts, cameras you name it. What makes the true believers so sure their WhatsApp chats are really E2E encrypted and FB cant decrypt them and isnt scanning at the edge? LMAO


> Facebook’s been caught spying on you with audio, video, contacts, cameras you name it.

For contacts: I have no expectations of any contact privacy on WhatsApp. It's known and documented [1] that they upload your entire phone book for contact matching. Private set intersection would be better, but I don't see anything sneaky going on.

Audio, video, cameras: What are you referring to?

> What makes the true believers so sure their WhatsApp chats are really E2E encrypted and FB cant decrypt them and isnt scanning at the edge?

The amount of scrutiny they're under from security researchers worldwide, and the fact that many governments are currently throwing a fit about not being able to gain access to the data either.

[1] https://faq.whatsapp.com/1191526044909364


See, FB gets away with it because everyone mostly forgets.

2016 Audio: they listened to what you did through your microphone until they got caught

https://www.nbc4i.com/news/spying-secrets-is-facebook-eavesd...

2019: Facebook caught activating camera without permission, to spy on you

https://www.pcmag.com/news/facebook-app-caught-activating-ph...

2020: Facebook a year later still secretly using your camera to spy on you, this time through Instagram

https://news.ycombinator.com/item?id=24514433

This is the company you are now trusting with the mere claim that WhatsApp is end-to-end secured.

2018: Facebook, not satisfied with getting its own users’ data only, bought and hijacked a VPN app in order to — wait for it — bypass encryption that millions of people trusted for ALL SITES ON THE INTERNET in order to analyze traffic and be able to get the dirt on its competitors!

https://arstechnica.com/tech-policy/2018/08/facebook-violate...

Now about WhatsApp…

Oh yeah… it’s already sending a lot of telemetry to Facebook:

https://www.wired.com/story/whatsapp-instagram-facebook-data...

And has been since 2016:

https://www.wired.com/story/whatsapp-facebook-data-share-not...

Oh, but at least the content of your messages is not analyzed by FB? Well, as far as we know that might be true, but if the other user flags your convo, it is in fact sent to Facebook:

https://www.propublica.org/article/how-facebook-undermines-p...

But wait, there’s more. Sometimes the mask slips due to People You May Know, which is the carefully guarded mix of “secret” algorithms that has helped Facebook aggressively grow beyond 100 million people:

https://medium.com/hackernoon/facebook-is-reading-my-encrypt...

https://gizmodo.com/people-you-may-know-a-controversial-face...

Mark Z knows what’s up:

https://www.theguardian.com/technology/2016/jun/22/mark-zuck...

https://amp.theguardian.com/technology/2018/apr/17/facebook-...

Telegram has NEVER tried to do any of these types of things.

So, given a choice, would I trust Zuck and co, or a guy who literally had to flee Russia because at great personal cost he had refused disclose the identities of the Maidan protestors, and losing his company to their Mail.ru conglomerate?

https://www.forbes.com/profile/pavel-durov/

https://www.quora.com/Why-was-Pavel-Durov-so-careless-in-his...

https://www.cnn.com/2016/02/23/europe/pavel-durov-telegram-e...

The answer is: neither (although Pavel Durov is like 1000x more trustworthy in my opinion).

https://itc.ua/en/news/durov-boasts-that-telegram-employs-ab...

I prefer open source software

https://community.intercoin.app/t/web3-moxie-signal-telegram...

And here’s why:

https://community.qbix.com/t/the-global-war-on-end-to-end-en...


There should be a site to remember all those:

- list the problems

- link to sources

- backup the source instead they happen

We forget too easily, and PR works wonders. I used to have such a list for Microsoft, but:

- I have to pull it of every time we talk about the new MS, because people think they are good guys now. They already forgot.

- People don't think it could have been that bad.

- I have to rewrite the list, I can't link to it. Or expand it. And I have to justify its existence and credibility because MS PR is so strong now.

- The links are disappearing from the web, so my previous proofs are fading away, slowly being replaced by references everywhere singing MS praises and stating how a saint Gates is.

The powerful are rewriting history, literally.

karmicarchive.com is available, just saying.



That's a single point of anecdata from Reddit, as far as I can tell at least for the WhatsApp one.

The Signal one somebody has posted in the adjacent thread was definitely real and horrible though: https://news.ycombinator.com/item?id=27950763

The fact that at least two heavily-used messengers got one of the most essential things in instant messaging wrong is nightmare fuel I didn't need to have in my life :(


We just had the xz crisis and that surprises you?

IT is just a series of security breaches.


Don't shift goal posts, please. A supply chain attack and a service sending private messages to the wrong recipient are very different issues.


I don't shift goal post, I'm answering to:

> is nightmare fuel I didn't need to have in my life :(

It's a weird reaction. All software have always been like that as far as I remember.


These two things are as different as you can get in terms of software bugs.

xz: A sophisticated supply chain attack. These are known, scary, and we don't have great ways to prevent them yet.

Apparently half of all popular instant messengers at some point making the same kind of trivial but catastrophic off-by-one error: Not rocket science to prevent. I was hoping at least high-stakes apps would have better QA.


I don't shift goal post, I'm answering to:

> is nightmare fuel I didn't need to have in my life :(


Funny enough, I experienced this in Android in the 2010s. Several times I would text one of my buddies using vulgar language and the texts would go to random people. My grandparents, my pastor, etc. It was horrible. lol


Delivering messages to the intended recipients (and no one else) is the single fundamental purpose of chat. If many chat apps have failed at this, then many chat apps have sucked.


Yes, but in that case, no single chat app ever conceived match your criteria. They all had some kind of similar major bug at some point. Even the big names.


Yes but how do you go about defining an ORM model without an app init class?


I hanen't touched Django in some time, but something like this should work:

    from django.db import models
    from django.db import connection

    class MyModel(models.Model):
        name = models.CharField(max_length=255)

        class Meta:
            app_label = 'myapp'


    with connection.schema_editor() as schema_editor:
        schema_editor.create_model(MyModel)

    # from django.core.management import call_command
    # call_command('makemigrations', 'myapp')
    # call_command('migrate', 'myapp')


A lot could be said about it, but the first thing that comes to mind is that not every application uses a db.

And not every application that uses a db needs an ORM.

You probably can build an ORM into the single file. But I'm not saying every application should be developed as a single file forever. I just like that you can start with one and expand later.


Then you don't need django, flask and fast API already does all that withing a single file.

What makes django useful is the admin, auth, session and so on that are all built around the ORM.


You never know into what a project will develop. So it is nice to know you can expand it into anything, even when you start simple.


I love this trend, every time they fail, it costs them a lot of money, and then I make bank after a few years of destruction because they look for a safe bet.

Then the cycle restarts.


It's embedded in the browser now.


I can't see big technical limitations resulting in slow QRCode scanning. We manage to detect fast cars going 120mph to fine them, we can read fingerprints instantly through a screen. We can take pictures of galaxies light years away.

30 years ago you could kill ducks with the NES guns instantly and it worked by detecting pixels.

I'm sure we can figure out how to analyze black squares and turn them into a number under 50ms.


Lol, that's the joke.

QR Codes were invented by Denso (automaker own) / Toyota. For high speed assembly line processes. Lul.


In 1994, no less.

I don't think people realize how limited the hardware was at the time.

They think because their phone is slow at scanning QR codes, that's how it must be. But the phone is not a dedicated device for QRCode scanning.

It's like someone saying they get blurry pics of cars on the highway so clearly speed limits are not possible to check automatically.


Touch x against y versus line this weird printed shape up at just the right angle in good lighting conditions. I feel like NFC is much easier to tell older folks how to use as well.

I'm all for the "we have technology why tf don't we use it, why aren't we better at it" argument, but the truth is that a lot of tech/systems in transport & other areas are retro af and new stuff gets shoe-horned in with all the caveats of a shoe-horning in.

Stuff doesn't get upgraded often, because it's expensive, because all of us vote for politicians that grant expensive/overpriced gov contracts putting money into them and their mates' back pockets. We'd be able to refresh public use tech all the time if it was non or low profit, never gonna happen tho.

Look at how much it cost Wales to change 30mph signs to 20mph: 34m£! And that's just for a few small areas, not everywhere they wanted to do. How in the f u c k, do you spend 34m taking down and putting up some signs? Those are ludicrous prices & all of us just completely ignore it bc we're too busy arguing about skin colour, which sex the person I sleep with is, or trans people being in the bathroom they want to be in, etc. Honestly.


> weird printed shape up at just the right angle in good lighting conditions

None of that matter. QR code can be read on any angle because of the 3 position detection patterns it comes with, by design.

Lighting conditions are not a problem on tickets (which is what the article is about) because you can illuminate the paper from the camera.

QRCode were fast on assembly lines two decades ago. They were invented in the nineties, at a time where we had slow processors and shitty cameras.


Actually, they do matter.

Assembly lines give you GREAT control over where the code is located, how it's lit (consistently), and what you do on read error (can't shunt off the passenger to a read error bin, so they don't hold up the line). Rotational angle doesn't matter, perspective skew does. And then - it's a leaf of paper, so you get folds and obscured parts (yes, correctable...up to a point).


Assembly lines are dirty, full of parasites and with broken lights all the time.

We can create live deep fakes or detect complex objects in live feeds of random webcams.

We certainly can correct a few shadows and distortions on a flat piece of paper we formatted, showing a basic symbol we designed and printed, pushed against a sensor we control, on a device we can light and shape the way we want.

NFC fails as well, you can fold the ticket just and it will break the antena.

Of course if it's a reusable ticket on a rigid medium, it won't happen. But neither for QRCode.


You speak about reader sourced illumination but there's a reason that phone screens go to full brightness when trying to scan a digital barcode.


The Stockholm Metro and public transport uses QRs, but on phones, and it's awful. The huge variance in people's shitty broken, dim phones make it take 3-4 tries sometimes. Infuriating! The scanners themselves are brilliant though, but nobody wants to stand in line for some printer machine and need to carry a flimsy bit of paper around.


The article talks about tickets with chips in it, which means you could provide the same ticket with qr code, only cheaper and less polluting.

No variance.

People can then use nfc with their phone, which doesn't have the pollution problem.


When I was there they also had NFC readers you can tap your credit card or phone on.


I would use redbean, from the same author, and use HTML.


>> I would use redbean, from the same author, and use HTML.

Wait... Could we build Solvespace web version and bundle it into that and have a completely portable CAD program that runs locally but in the browser?


Impressive stuff. Unfortunately, Lua. From a user point of view (well, at least this user), TypeScript would be a better fit.


What are your misgivings about Lua?


Not OP, but having written some Lua, I can make some guesses:

- Relatively obscure language, so potential contributor base is limited from the start

- Lua shares PHP's "One datatype to rule them all" design, which works but feels ugly. In PHP it's "arrays", in Lua it's "tables", but either way you have all the attendant problems and weird edge cases to learn

- Expanding on above point, Lua's APIs for working with tables are, uh, idiosyncratic. Slicing a "list", last I looked, was an unintuitive monstrosity like `new_table = { table.unpack(old_table, start_index, length) }`

I could keep going, but I have other things to do during my brief time in this universe.

To any Lua aficionados out there, my apologies if I've misrepresented it. Corrections to my misunderstandings will be appreciated.


> Relatively obscure language

Lua is among the most used languages in existence.

It's probably the most used language by under-21-year-olds, and almost certainly so for under 16. Roblox is absolutely enormous.

It's the usual choice of embedded scripting language, so a great number of programmers who don't use it as a daily driver, nonetheless learn it to modify this or that program. Being a very simple, minimalist language, this is easy to do.

It's true that it's missing some affordances which you'll find in larger (and frequently less efficient) languages. You'll end up doing more iteration and setting of metatables. That bothers some people more than others. These are the tradeoffs one must accept, to get a 70KiB binary which fits in an L1 cache while being multiples faster than e.g. Python or Ruby.


Lua is too bare bones. It's a carefully considered tradeoff for the project goals of being a very small & easily embeddable language for C projects, but it means you need to implement too much load-bearing functionality yourself. Each lua project ends up being an ad hoc framework composed of C bindings and standard lib extensions, but it doesn't have an ecosystem that makes this straightforward or consistent.

A lot of people like lua from using it on very small projects, or like, spiritual reasons related to its implementation simplicity. But having used it quite a lot professionally, in practice it ends up being a slog to work with.

All that said, lua is closely tied to C, and embedded in a C project is both its intended use and the place where it fits best. So while I don't really like lua and would almost never choose it myself, this is one of the rare exceptions where I think it's a good choice.

A lot of people want redbean to use TS or python instead, and imo either would make it much bigger, more complex, for relatively little benefit. It would definitely benefit from a more full-featured language, but I think a weirder one that is still intended for embedding in C would be best. Something out there like janet or fuck it, tcl. But lua has a lot of allure for a lot of programmers and I think gives the project a feeling of "old school cool" while still being pretty accessible. So is probably the best choice in the end.


None in particular, except that all the code I am currently writing is in TypeScript. Especially if it comes together with HTML files.


You don't need the file to be named "hello.py". You can name it just "hello", with the right shebang it will work fine.


Even if you don't want to limit yourself to the stdlib, you can still use a zipapp : https://docs.python.org/3/library/zipapp.html


You need to introduce a build and release process then to do this then which still detracts from it being simple or the selling point being it's already installed.


With cpan it's the same, you need to install deps somehow.

You don't need it if it's just a python script with stdlib, just like with raw perl.


In fact, that's true for Python if you use a zipapp and no c extension: https://docs.python.org/3/library/zipapp.html

You can happily copy the zip of your scripts and all deps in the server.

You still do have to mind your versions, as always with python.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: