vonuebelgarten

The sad part is that this problem was solved decades ago with grid locators like Maidenhead[1]. It's a purely mathematical conversions with no lookup tables, cover the entire world and alternate pairs of letters with pairs of digits (so no confusing or language and culture dependent words).

Code becomes longer according to the required precision, so eight digits are enough for a typical city neighborhood, ten digits goes to a 30x20m block that is good for disambiguation even in the most dense urban areas. Adding more digits will work too, but that just more work.

A typical location would be something like: fm19oc75hv

[1] https://en.wikipedia.org/wiki/Maidenhead_Locator_System

> do you have any thoughts on what causes these systems to stick to trains?

Trains are excellent for dense urban environments and better yet when integrated with another modes. I take Berlin as an example: You have fare zones and S/U-Bahn everywhere in the city center extending for to Potsdam, etc., trams in the former east, buses on the less dense parts of the city. Also trivial access to regional and long-distance trains. And it also disproves the typical excuse "You can't do that in an old city": some U-Bahn lines exists since 1902, the city got devastated by war and then there was the DDR. The reunification needed a lot of work and yet the system survived. Took me a long time to notice there was no Ubers, maybe because it was not that advantageous for people to use it and Uber Inc. just gave up instead of fighting city regulations, as they did everywhere).

I compare with the systems from my native Brazil, where public transportation ranges from pathetic inefficient on big cities to non-existent in small towns. Hell, I really miss Berlin.

This is also standard practice here in Brazil.

Why the hell aren't we migrating to the Fediverse (aka Mastodon) en masse ?

> So encryption isn't allowed, but is there any way to authenticate information sent over packet radio? Open communication has plenty of uses, but some of those can be spoiled by bad actors impersonating others.

You are not allowed to encrypt data on ham bands (this seems to happen Worldwide, it is also true here in Brazil), but there is no restriction on use of cryptographic primitives for authentication. But some countries (France, AFAIK) also require the protocol specs to be openly available, what should not be a problem in this field.

Digital signatures are Ok as long as the content of the message is not hidden (i.e. all listeners can receive and decode the information) and the transmission is identified (as usual in ham).

This is an example of title that could benefit from a simple, non-editorialized, and purely factual change: "Programming the Z3 SMT solver".

I am sure I was not the first to think it was related to Konrad Zuse's Z3.

So, did they just reinvent the Maidenhead locator ( https://en.wikipedia.org/wiki/Maidenhead_Locator_System ) or any of the previous systems?

Question: is Wired actively blocking archive.is? I tried to archive this article just to get a repeated "Network error" [1] which may be a sign of a Layer 3 block. A trivial search [2] shows no page is successfully archived since the end of September.

[1] https://archive.is/eU7Yn

[2] https://archive.is/www.wired.com

People are too quick to understand these new terms as solely necessary to provide service. The entire paragraph is:

> "By submitting, posting or displaying Content on or through the Services, you grant us a worldwide, non-exclusive, royalty-free license (with the right to sublicense) to use, copy, reproduce, process, adapt, modify, publish, transmit, display and distribute such Content in any and all media or distribution methods (now known or later developed). This license authorizes us to make your Content available to the rest of the world and to let others do the same. You agree that this license includes the right for Twitter to provide, promote, and improve the Services and to make Content submitted to or through the Services available to other companies, organizations or individuals for the syndication, broadcast, distribution, promotion or publication of such Content on other media and services, subject to our terms and conditions for such Content use. Such additional uses by Twitter, or other companies, organizations or individuals, may be made with no compensation paid to you with respect to the Content that you submit, post, transmit or otherwise make available through the Services."

It is easy to associate the concession of license (specially the "You agree that this license includes the right for Twitter to provide, ... to other companies, organizations or individuals for the syndication, broadcast, distribution, promotion or publication ... subject to our terms and conditions for such Content use.") with the service provided ("This license authorizes us to make your Content available to the rest of the world and to let others do the same"), but I do not see where it say that Twitter can only do this for providing the service. AFAIK, Twitter still can, for example, sell photos to a news agency through this same terms.

Of course, IANAL.

Wait no more, just install F-Droid and NewPipe ( https://f-droid.org/packages/org.schabi.newpipe/ ).

Bonus feature: it does not use the API so Youtube can not track what do you watch.

This site is absolutely unusable (breaks when I block some scripts, trackers, etc. and even fails to load in archive.is).

For anybody who wants to read the article, I just put a text-only transcript in https://pastebin.com/raw/k22WtvmG

Gun control is not a magic solution for firearm killings (after all it only affects law-abiding citizens who, by definition, are not murderers).

E.g.: here in Brazil it is almost impossible to legally own a firearm but we had 212 firearm-murders per million people in 2014 (Source: http://brasileiros.com.br/2016/08/o-brasil-e-o-pais-que-mais... ).

Their strategy is particularly awesome: a hundred of small short-lived satellites (really small, they're 3-unit cubesats, 30x10x10 cm) operating in a swarm. No big deal if a single one is lost: operation can continue with other ones once they are in position. Also, costs are spread due the possibility of servicing several customers simultaneously in separate locations around the globe.

I have the impression Tox withered and died, which is really sad considering how usable (when compared to alternatives) it is.

Same problem here. Despite this being the best MITM-prevention strategy, it will be hard to assemble a group of people.

Maybe allow copying/pasting keys but with a Signal-style post-validation or something like a PGP wordlist to allow voice-based confirmation?

Iep. Running the tests over the new commits before pushing is still required. Usually not a big problem.

> I don't understand. What do you mean by this?

Ads embedded in the video stream (i.e. "burnt" as one with subtitles) can't be blocked but also can't deliver any active content (JS, Flash, etc) used for tracking or infecting users.

> they could make the ads indistinguishable from the actual video (in the html), or even splice the videos into one stream.

And make ads unsuitable for the most egregious attacks on privacy, simple plain tracking or even as distribution channel for malware. Curiously, this nuclear option will make things better than the current situation.

That's the actual problem with these ads: bloat, bandwidth usage, javascript, profiling, de-anonymization, tracking, attacks on privacy, sound, unskippable videos, etc.

I will feel no remorse for adblocking until advertisers go back to static, single-request, non-tracking, non-targetting ads.

> Ads shorter than 30-seconds, including the 20-second spots, can be made unskippable.

uBlock Origin will continue to serve me well.

>No multi-stage commit pipeline is much easier conceptually -- mostly I just want to commit the changes I made to my repository and automatically sync upstream.

But forcing this approach precludes you of, for example, easily splitting your existing changes in two commits if required. If changes to the same file are to be committed separately, a non-zero amount of copy-pasting, resetting, temporary files, etc. will be required.

I see Git's separation of concerns of a strict superset for your use case. Just add an alias "git commit -a; git pull; git push".

>Genuinely curious: Why do you need rebasing?

Mostly to sort the code out before publication. People usually assume rebase as a tool for integration but forget how useful it is in the "local" development stage (ie. before pushing the code for the team).

Also, rewriting history (in the good sense of the term).

Git have some awesome approaches for minimizing the amount of semantically irrelevant commits in the repository (or plain garbage commits) that other VCSs lack. Mostly the possibility of having local branches (keeping them hidden away from everyone may be a plus in some cases) were a developer safely store that horrible-looking code everybody says they never write, go back, test, fix the code up, add test cases, fix indentation, documentation, etc. all in different commits and, then, rebase or squash-merge them in a self-contained, well-described and semantically split set of commits and then push them to the public repository in a way other team members can follow and understand.

For git, history is a tool for documenting the project -- and I love it.

Very informative. I just took the liberty of converting your post to units I can read (sorry for the pathological imperialphobia :) )

> Yes: because Samoa Air's fleet aircraft are all Cessna 172s. You are essentially paying for a personal charter flight in a small aircraft, so there are no "averages" there. A single obese passenger can directly increase a flight's payload weight by +100% or more. Not the case with an airliner, where you are averaging across 75-600 people.

> In general aviation just because the seat is there doesn't mean you can take off with someone in it. As a rule of thumb, "one seat" is a 68.03 kg person, no luggage, and sometimes that's counting some of your fuel there too. A 2-seat aircraft like the Cessna 152 doesn't take off with full tanks with 2 average adult males onboard even without luggage (163.29 kg full-fuel payload), and it's a struggle to get off the ground with 2 heavier adults even with reduced fuel.

> The C172 is a four-seater aircraft, 261.7 kg full-fuel payload (note: less than 68.03 kg per seat!). So with full fuel tanks you will get one pilot, one passenger, and either some luggage/cargo or a child passenger. Maybe a second adult passenger and no luggage if nobody is too heavy (above 79.37 kg average). And an over-water flight in the Pacific is not the trip to take with a reduced fuel load. So you can see how the numbers work out here: the pilot plus one obese adult might literally be the entire payload for the flight.

> (Note: a 2003 study from the New Zealand Ministry of Health set their "average" male passenger weight at 84.82 kg without carryon, or 93.89 kg with carryon, and the average female passenger weight at 72.12 kg without carryon or 76.65 kg with. Further, they noted that average passenger weight was increasing at about 2 kg/6.6 lbs per decade.)

> source: https://www.caa.govt.nz/pubdocs/2003_pax_weight_survey.pdf

They are the dominant player in this market, I simply can't understand why they didn't crewed it already.

I can only speculate: it's because WhatsApp is giving them an always-updated social graph of a billion people right now (including inferred information on people who, like me, didn't install the application but whose numbers are in the contacts books of people who did it) and crossing this information with FB data brings more revenue than anything they can do with WhatsApp itself.

Hibernation is a very nice feature (I use it for laptop and desktop machines) and it requires a swap partition. Also, a encrypted swap is even more important in this scenario.

In the laptop I'm typing this, swap is one of the partions over a LVM2 physical volume over LUKS.

> More of the "If you've got nothing to hide, then you've got nothing to worry about" attitude. This suspicion is so hostile to normal traffic that its chilling effect is undeniable. It's very sad to see.

It's worse -- these CPF numbers have nothing special but a simple checksum at the end. It is trivial to generate them and, if we get a used one, check the actual owner from our IRS website.

So we can assume everyone with bad intentions will simply use one from anyone else and the law will have no effect on criminals but will terrorize people who need/want to keep their PII private. Also, I suppose everyone will infringe that law at some level, opening the door to selective prosecution of "undesirables" or someone opposing the powers that be.

I changed the title to give some context to international headers and stay within the 80 character limit, I hope it stills within the spirit of the rule concerning editorial changes. A literal translation would be "Representative to require Brazilians to give CPF to post in social networks", but the text makes clear the proposed law will affect any website and, in Brazil, CPF is something alike a SSN originally used for taxes but now required for a lot of things, including financial operations, boarding a plane (sometimes even an interstate bus!), opening bank accounts, getting a job, going to school, etc.

The Google-translation is pretty good for an machine translation, but follows a few fixes:

---

Representative to require Brazilians to give CPF to post in social networks

The House of Representatives will discuss a bill that seeks to end anonymity on the Brazilian Internet.

Authored by Congressman Silvio Costa, from the Social Christian Party from Pernambuco, PL 1879/2015 wants to change the Internet Civil Mark to include an obligation to store the full name and CPF number of Internet users who want to publish something on the network.

Any site that allows exposure of ideas would have to store this information of its users. The obligation would be set by adding a paragraph to the Civil Mark as it would read: "Internet application provider, as defined in the head, which allows posting of public information by third parties, as in blog comments, forum posts, status updates on social networks, or any other method to insert information in the Internet, shall keep, in addition, records of these users including at least their full name and their Natural Person Record number (CPF)."

For the deputy Silvio Costa, "this simple requirement will certainly curb the attitudes of those who cowardly hide behind anonymity to disseminate criminal messages in the network. Also," he continues, "individuals who insist in this type of conduct will be more easily identified and properly prosecuted."

The project is still in the House for analysis from commissions of Science and Technology, Communication and Informatics, and Constitution and Justice and Citizenship.

Due to the general architecture, I think it's better compare Bleep with Tox.

I though the spies would interpret it as "We are tracking an undercover agent" but now I see it was a silly interpretation.

That's a pretty common application when you need to synchronize clocks to microsecond accuracy or to a second accuracy but have neither a stable network connection nor a time broadcast (like the German DCF77). It's also used to replace Cesium clocks in cell base stations or for the precision timing protocol (IEEE 1588) for PWE3 networks.

Iep, is there a lot of systems depending on GPS and a major system failure will bring us some chaos.