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

It does. Open your train ticket from the app, then the "i" next to "On time"/"+X MIN" text, and it shows the list of all train stops and where the train is. Next to the train stop you find a number which is the platform


> It is not even possible to see local data on the phone.

I can still see and navigate through everything


Bullies don't care about diplomacy.

If you expect Russia to be willing to find an agreement that does not restrict Ukraine's freedom or take its territories, you are wrong, or such a war would have never begun in the first place.


If you are connecting from an Italian ISP to https://mil04s43-in-f1.1e100.net you're going to be greeted by a message from AGCOM telling you the website has been used to spread copyrighted content.

This already happened with a Cloudflare CDN before. https://community.cloudflare.com/t/blocking-of-my-website-vi...

https://imgur.com/a/EKFHROX


How can they do that with HTTPS though?

HTTP sure they can happily MITM and redirect, but with HTTPS you need a valid cert.


Your browser shows a TLS warning saying that the certificate doesn't match. If you override it, it brings you to that page.

This is not a DNS block, the IPs are owned by Google, Italian ISPs are forced to forward the traffic of a blocked IP to AGCOM's servers.


DNS.


Connecting with https prevents any DNS poisoning, unless the ISP managed to get a fraudulently issued certificate or a MITM root CA installed on the end users' devices. Neither seem likely.


It's not poisoning, it's blocking.


I don't get that, and I'm connecting from the biggest italian provider TIM. I first get a warning from the browser because of the certificate. If I go forward I just get a 404. But maybe it changed in the last hours?


TIM and WindTre have overridden the block, don't know about the other ISPs.


Because it didn't. There's videos where people ask and the "robot" replies with "I can't disclose how much AI there is in me"


That's not a lie either?



TLDR a reporter asked a robot and believed what it said even when very vague


> Scoble made a follow-up tweet saying he talked with a Tesla engineer to get clarity.


This is my experience with frame.work's customer support, and how things should be improved.

One of the things I think is dangerous about the current state of their official communications channel (Discord, Reddit, etc) is that the moderators (which are volunteers but still overseen by framework employees) close conversations when people complain (as seen at the bottom of the linked post).

The other, even more dangerous thing, is that they've created and push an attitude of "don't care about the issue even if it's bad, I'll just buy a replacement instead of making a warranty claim" that makes users question their choice to contact Support. An example here: https://imgur.com/OLFJITP or straight up defending some the company's shady behaviour [1]

[1] https://www.reddit.com/r/framework/comments/1drjp5w/comment/...


Only 1-1 calls are encrypted, voice chats (group calls) are not


> "I can easily guess that assholes in secret service would probably like very much to use that to blackmail him to add backdoors to telegram. So sad."

Telegram is a backdoor by design. The server has complete access to all your messages, they can do whatever they want with those.

And they even had a backdoor in E2EE chats, see: https://habr.com/ru/articles/206900/


Do you have a link in english?


Goole Translate works good enough for this article, there is also one from "FiloSottile" but I haven't read it and iirc it still references this one, it's called "The most backdoor-looking bug I have ever seen"


This was a bug that was fixed right after it was reported. The author of the article praised Telegram for the speed of reaction.


Note that America has been caught spying on EU countries politicians and manufacturers so many times and nobody got ever punished for this. While the backdoor talks are purely hypothetical, and Telegram's client and protocol are open source: you can just study the code.


Which is what the author of the article I linked did. The backdoor wasn't hypothetical, Telegram had to patch the protocol.


It's important to say that data cannot be decrypted by the relay


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

Search: