bob1122

I love this!

I don’t think I’ve ever quite fully appreciated N++‘a array of features.

What features do you find really help your workflow and how do you find it compares to Sublime Text in that regard?

Tried it, works.

Also seems to not deliver SMSs that contain other combinations with 'secure communication' within it.

E.g.

'Hahahaha juice secure communication james'

or

'Not secure communication'

Agreed.

I respect if it's not what you're looking for but you may be able leverage yourself into a good position (with the community and with PG) as a result of the publicity + traction combo.

Great work getting that ball rolling so quickly!

Not sure I follow you, can you explain?

Same, however this similarly is also a Chromium / JS mishmash

Absolutely, maybe I'm not with the trends but it seems unprofessional and doesn't add much value (for myself)

Unfortunately, I think this model is still the older model without the new exclusive ESC key and the 9th gen CPUs

Which awkward book are you referring to?

Thank you for pointing that out doom

This is incredible, thanks for sharing!

Oh my this is majestic!

Country: Belarus

Probed ISPs: Beltelecom (AS 6697)

Censorship method: TCP injections

We have recently heard of network anomalies in Belarus. Tor has been finally blocked in December 2016, although it had been explicitly declared that Tor should be blocked since February 2015.

Directly connected users from Belarus

An anonymous cypherpunk has helped to gather some evidence regarding Tor being blocked in Belarus. It’s neither a complete study nor an in-depth research and it’s unclear if any other further evidence will be gathered, so we decided to share current knowledge as-is:

Tor directory authorities are not blocked Public onion routers have their ORPort blocked by TCP RST injection The onion routers’ DirPort is not blocked Plain-old non-obfuscated Tor Bridges from BridgeDB circumvent the interference Beltelecom (or its upstream) has strange configuration of the networking gear injecting reset packets The strangeness in equipment is the following. The first injected RST packet does not have have proper SEQ/ACK numbers. These packet fields are just filled with zeroes. So this packet is dropped by the client’s TCP/IP stack per RFC5961 and does not actually terminate the client’s connection:

$ tshark -Tfields -eframe.time_relative -eip.src -etcp.srcport -eip.dst -etcp.dstport \ -eip.ttl -etcp.flags.str -etcp.seq -etcp.ack -r urandom.pcap | sed | awk | perl 0.000000 192.168.1.2 42555 87.118.94.227 443 64 S* 899897236 0 0.029459 87.118.94.227 443 192.168.1.2 42555 125 R* 0 0 (sic!) 0.096914 87.118.94.227 443 192.168.1.2 42555 52 AS 1984028404 899897237 0.096958 192.168.1.2 42555 87.118.94.227 443 64 A* 899897237 1984028405 0.136874 87.118.94.227 443 192.168.1.2 42555 125 R* 1984028405 0

That’s all for today. Remember, fried potato is better with onion!

Did you intentionally obfuscate your code?

This is very handy