mgreenleaf

Several things to think about, weak points could be:

Domain name, since the registrar will probably have your information. Namecheap allows bitcoin payment, but I think they still require contact information. Going with an onion url would limit that impact.

Hosting, again, they will almost certainly have your information. Swisslayer allows bitcoin payments, but contact info might still be required. Could be mitigated by going with Tor or some other service, but that limits discoverability.

Server software -- you would want to limit the ability to be compromised, so something like OpenBSD with the built in httpd and raw html files would be a reasonable bet for preventing intrusion. Keeping it simple would leave less attack surface, and less potential to leak information.

Using Tor to connect would mean less logs between.

Any information you gave in content could be used to trace, but that is difficult and would require being careful in the writing style, and what information is leaked in that channel.

EDIT: As beefhash points out, piggybacking on an already accessible public endpoint negates a lot of the leaking of your information through your own services.

I second the needing a single, searchable source of truth. One of the main needs is for it to be maintained and updated. Having it all in one place helps with that and reduces the cognitive load of making the decision of where to update.

We use fossil; a bit minimalistic, but you get a wiki + code repository + tech notes + issue tracking all in one place and auto-updated with the code, and you can run it as a server with a web interface for those who don't need permissions to clone the repo.

Thank you!

Do you have urls for any sources? sounds like an interesting read.

Hmm, just a thought, but maybe that is an argument against the hyper-specialization of modern society. It would be nice to choose different things throughout a day/week/year, all productive, and all requiring some skill, but each one being a bit different providing physical or mental exercise of different types. Bending over all day to build something might not be great for humans, but sitting in a chair all day focusing probably isn't either. It would be nice to arrange a productive society that gave people the opportunity to move between the different types of productivity.

Great work, thank you for the effort you have put into this.

It would be nice if someone came up with a "network VM" that could run sandboxed code that was more like traditional native applications, but seamlessly networked to a server (like Erlang or Phoenix LiveView on multiple nodes but simplified for server-client). Then it would be possible to write more standard apps on a well designed, purpose-built system which would simplify a lot of Dev work. Then you could have a well designed markup language for easier building of documents too. But start fresh in a VM system with all the hindsight of what purposes the web is used for, and the layout systems that are most flexible/popular.

You could have some low level thing like web assembly (or even just we assembly itself and get all of the current optimization and standardization work for free) that other languages compile too. And a low level GUI library like Vulkan that you can build libraries on top of.

Worldwide

I've been impressed with several of the Bing projects; I recently found that they open sourced the JIT compiler for C++ they use on Bing [1] I've been more and more impressed with Microsoft's efforts in Open Source and elsewhere. Especially with these under the MIT license.

[1] https://github.com/BitFunnel/NativeJIT

I agree; when I interview I tend to talk to them for a bit to get a feel for how they view the world and how they code. I ask about personal projects, how they learn new things, sources of information for keeping current, what they've worked with, personal interests. I ask what they've worked with and why and why they would choose a particular solution. You can get some really interesting answers (programmers tend to be polymath-y types). I think the best hires we've made were people who had personal side projects, naturally curious with learning hobbies (not just programming), and were open and honest about questions, willing to have a good discussion, and weren't just trying to give the expected answers. There are two sides to that coin, since the interviewer also has to value that, and maybe it just depends on who you are and what you are looking for, but it has worked well for us.

I love the idea about doing the paid project on the real project; I'd love to implement that too.

I believe this is a post by Facebook about Facebook engineering. I may be wrong, but I think that it is a facebook blog thing.

PySide2 makes this way easier. I recently setup a PySide2 Project in PyCharm with the integrated package-management and it was a breeze (I guess the official support helps a lot as opposed to PySide[1]). First tried several other graphical libraries and was getting nowhere, but was happy that the Qt integration was relatively painless.

On a related note, does anyone know of a way of creating a "stand-alone binary" or installer for PySide2?