bilkow

I agree, and sincerely, I'm a Rust programmer and "memory safety" is definitely not why I use Rust. There are lots of memory safe languages but I feel more productive and get more satisfaction writing Rust than, say, Python, Lua or C++.

In Rust I feel like almost every time the program works on the first time it compiles successfully, even without writing tests. Probably a combination of very well designed API, builtin RAII, very explicit syntax, compiler strictness and clear docs. I also cannot forget to handle errors (even if I just decide to propagate or crash).

This is what "correctness" means to me, but it isn't exactly enforced by the compiler itself.

Well, sometimes what you're used to matter too. For me DDG is better (expect for local searches, in which case I've got to include my city's name).

Every time I search anything in someone else's computer (with google) I find it much harder to find what I'm looking for, sometimes I can't find and just go to DDG.

The only times I use !g is when I find some pretty obscure programming errors and no (useful) results on DDG, and only once in a while google is able to find anything better, usually the results are the same.

I believe that its actually possible to run python in WASM, see https://wapm.io/package/python#shell

This doesn't match my experience... When you install it, they show a page and the account icon. I believe that only on some major updates I've seen the account page again, which is a nice reminder to sync bookmarks (even though I don't use it). I always customize the toolbar upon installing and it (the icon) never came back or bothered me again.

> Everyone cares about speed first, or they would be using a more convenient slow language.

I use Rust and I actually care about readability first.

Sincerely I find Rust more readable than most popular languages (Python, Javascript, C++, Java, even Swift...), unless I'm looking into some code that abuses generics and lifetimes (which is actually rare for me).

I think that's because it enforces some pretty clear patterns with its lack of struct inheritance, sum types with pattern matching, the way things are imported ("use" statements), lack of parenthesis around conditionals, and being expression oriented.

Just use English / US (International), it will make "é" become ' + e and allow lots of other combinations.

Actually, F-Droid supports using the upstream developer signature for quite some time now if the build is actually reproducible.

https://staging.f-droid.org/en/docs/Reproducible_Builds/

https://gitlab.com/fdroid/fdroidserver/commit/8568805866dadb...

I think that's a terrible thing to do... There are real people which might have to find workarounds just to know what your initiative is about.

I'm also curious about the type of your initiatives, are they really local? Programming stuff isn't limited to the US[1].

[1] https://insights.stackoverflow.com/survey/2018/#methodology (only 25% of the stack overflow 2018 survey responses were from North America in general)

I'm not really sure, but the thematic break element (<hr>) after the last paragraph mentioning ruby makes me believe its not.

Just found it!

https://html.spec.whatwg.org/multipage/rendering.html#phrasi...

"The initial value for the 'color' property is expected to be black. The initial value for the 'background-color' property is expected to be 'transparent'. The canvas's background is expected to be white."

It seems that chrome and chromium may also ignore the spec, as https://news.ycombinator.com/item?id=19056637 says. Hopefully prefers-color-scheme[0] will take over soon.

[0] https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref...

Only admins can post to telegram channels, they're like facebook pages. On supergroups any user can post but admins can remove content, although I don't believe it counts as public content, so they shouldn't (according to the FAQ entry I listed above) take them down anyway.

I agree that this is bad, considering that the country will answer with violence anyway, but this seems to be aligned with telegram's position. From the FAQ about takedown requests on public content:

"Please note that this does not apply to local restrictions on freedom of speech. For example, if criticizing the government is illegal in some country, Telegram won‘t be a part of such politically motivated censorship. This goes against our founders’ principles. While we do block terrorist (e.g. ISIS-related) bots and channels, we will not block anybody who peacefully expresses alternative opinions."[0]

I believe that, if there were actually violence calls, they're being unbiased by strictly following their own public rules.

[0] https://telegram.org/faq#q-wait-0-o-do-you-process-take-down...

It may be an option if using (super)capacitors and only transmitting / receiving for a short fraction of time.

https://hackaday.io/project/28527-solved-esp8266-powered-by-...

I'm not sure, maybe it is worth checking the source code.

An update checker is nice though! I wish firefox had one, but at least there's FFUpdater.

It may now support working on devices without Play Services, but being the same apk, Google's libraries are still inside the app. This way it's not entirely free and doesn't fit F-Droid's inclusion policy. (https://f-droid.org/en/docs/Inclusion_Policy/)

That's not entirely true. While Telegram's "cloud chats" are not end-to-end encrypted by default, they're encrypted at rest. They claim that "all data is stored heavily encrypted and the encryption keys in each case are stored in several other DCs in different jurisdictions."[0] It's not even close to perfect, but it's also not everything that the government wants.

For me, the problem with Signal is based mainly moxie's position on the LibreSignal fork, which aimed to be a Google-Free version of signal, but moxie said he was not OK with LibreSignal using the Open Whisper Systems servers and the name "Signal".[1] I kind of understand his position, but that's not what I'd expect of the free software community and definitely not what I expect from someone who's in the middle of my communications.

In the end, the hope's in matrix.org. It supports end-to-end encryption, works without a number and is fully federated. Maybe someday Telegram and Signal can even federate with matrix.

[0] https://telegram.org/privacy#2-storing-data [1] https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

The OnePlus 3T seems to be officially supported by LineageOS[1].

I'd actually trust my phone more (using the official LineageOS build) as basic system components are FOSS (although there are some firmware blobs).

[1] https://wiki.lineageos.org/devices/oneplus3

As the github user mimi89999 pointed, moxie wouldn't have to support LibreSignal directly, it behaves like a normal Signal client and there would probably be no impact in his servers at all because there was a very limited number of LibreSignal users.

I kind of lost my trust for Signal when moxie said it was not OK[1] that a fully free and open source fork of their client (built to remove the Google Play Services depency back then) was using their servers.

I've read the discussion and I find moxie's arguments pretty weak in this matter.

[1] https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

EDIT: spacing

You can read the article normally by using reader view on both Safari and Firefox, which make almost any article better to read anyway, at the expense that code blocks won't be properly formatted (in this case, on some sites code blocks just disappear).

Does it work by checking the referrer? Maybe you can workaround by configuring a browser add-on (like RefControl) to just send facebook.com as a referrer while on WSJ.

s! works too

Aren't the adresses hashes of the _public_ key? Hashes of the private key doesn't make much sense to me, as clients never come to know them.

Edit: Grammar

This actually makes me sad. A 1/10 chance should happen sometimes (as a 1 in a D20) and the randomness is part of the fun of the game. If a 80% chance is actually a 92%, I think should just show a 92% chance, it would be more fair.