As an aside, for very good analysis of current Chess games (as well as older sagas around certain legends of the game), I heartily recommend checking out agadmator's Youtube channel[1].
It was tied to the beginning of Covid lockdowns as well. Chess has had a very strong year in terms of numbers coming to the game. Queen's Gambit seems to have exploded that again.
Not arguing that this could be used in an abusive relationship, but if we work on the basis that someone could install a similar program on their partner's phone that's not Google. There are a lot of pro's for the tracked person with the Google implementation.
Google email you quite frequently (I believe monthly?) to tell you that you are sharing your location and with whom.
You can disable it at any time. Obviously disabling such a feature in an abusive relationship may not be an option.
I think you are misunderstanding. The secret does not need to be hardcoded in the python file. If it's read in from an environment variable or some other external source, it will also be in the pyc
Enjoyed the article. For once, this article showed some flaws in the original process/idea, and showed very nicely how an original seed idea turned into something different, and more involved/interesting.
Clearly a lot of work and sweat went into getting the results you did, and the final output looks very polished.
I recently did this manually by piping responses to a temp file called before and after, and then using vimdiff as my differ which proved quite effective.
This tool looks great, but would not have worked with my particular use case, which was doing some migration of user data, and diffing the user accounts to make sure that they had changed in the expected way.
It might be an idea to add the ability to query the same host twice, but have a user input trigger when to test each host.
I quite like this style of video, I have only watched the first ~15 minutes, but I find it a much more engaging way to jump right into code like this, or learn some Go while I watch.
I would love to see some popular figures in the open source world, talk us through a pull request etc. I would be surprised if it didn't drive a few more contributors to the project and if nothing else would be a powerful introduction to the project.
My first linux that I managed to run on a vm. I only had access to dial up internet and thus could only download a very small package. The screenshots make me very nostalgic indeed.
Presuming this is closed source? Although it looks like a neat concept, it would be a more attractive option if I knew something that was dealing with my browsing history was open source.
What is wrong with the sort of thing that whatsapp do? a small fee (~€1) a year.
If they could make it payable via some easy method (SMS?) then people would willingly pay a small fee for the use of snapchat. Sure people would go "Bah Humbug! Snapchat want me to pay a €1" but they have a very strong userbase, one that is extremely active. In the long run, I think their user base would prefer a one off payment than being inundated with advertising.
This shows only files that are tracked.
I tend to do a lot of work which leaves files that I don't want to check in lying around in my git repo, this eliminates these and lets me see exactly what I have been working on. The slight caveat to this is when you are working on a new file that you have not yet checked in ever.
This goes hand in hand with:
git add -u
Which only adds untracked files. With aliased commands this usually results in a flow like this:
Another advantage to this system is that reading and commenting becomes less prone to these sort of comments:
"Where is X defined"
"Ah I see, this is where X is defined, disregard older comment"
A publish system allows you to basically stage comments before publishing. I used rietveld before github and this alongside side by side diffs was killer.
So I use github enterprise and use the review tool a lot.
It has improved our overall code review experience, but there is a few things which have proved problematic and even have caused major headaches in the last year or so.
1. No Side by Side diffs.
2. Pushing new commits will often collapse conversations from the review. (i.e these conversations are folded)
Really, I want some way to look at my PR and say hey I've addressed all the comments on this pull request, and I am good to merge.
This is not even getting into what happens if you rebase your branch and then force a push to the remote.
[1] https://www.youtube.com/c/AGADMATOR