McSinyx @mcsinyx@librem.one

I made it with half of the code being random hardcoded strings: https://git.sr.ht/~cnx/ipwhl-utils/commit/b085828

Am I cool or what. Don't answer that.

@The_Quantum_Alpha@mstdn.social, I might sound like a dick, but you are not obligated to make an expensive wedding if that's gonna cripple you financially, and even it isn't, spending less on the wedding would save you and your spouse money for other necessities and/or vacations. After all, a wedding is supposed to mark a happy day of your life and set a foundation to your marriage: don't let it have negative effects on your future life.

I actually went look for it this year: https://www.youtube.com/watch?v=m-tKnjFwleU

@huy_ngo, torify(1) is a simple wrapper that calls torsocks(1) with a tor-specific configuration file. It is provided for backward compatibility; instead you should use torsocks(1). Probably your distro does not ship the wrapper.

@huy_ngo, I think this is the second time you ask this, torify is the command name, not a pun.

By Tor, @huy_ngo, did you mean the Tor Browser? In case of emergency to bypass censorship, you might want to consider torifying any web browser (or HTTP client), there's a high chance that it will just work.

Really, I meant it. Please at least try to. I wish to be wrong rather than trying to find programatic way to split the OS and architecture in

* manylinux2014_x86_64, manylinux_2_24_i686
* macos_10_9_x86_64, macos_10_9_i386, macos_10_9_intel (and what are those fat{64,32,} even?)
* win32, win_amd64

I know that I will have to have to go with the hardcoded way, but does anyone even know the tags for the *BSD and other *nix?

Python wheels' platform tags are confusing and has zero standardization. The reference and only parser implementation packaging.tags is even more difficult to cope with. Change my mind!

May I join, @fafnir?

@xpil@fosstodon.org, you might be interested in an add-on I published a while ago: https://addons.mozilla.org/en-US/firefox/addon/alful

@linmob, with pmOS patch applied, this is actually the behavior after F11 twice. Never dig into it to find out why though.

Pet peeve, @huy_ngo: H2 is rendered with a distracting horizontal line below, and since most issues are rather short, it can be preferable to use H3.

I bet they're going to pull off a Reddit, @xahteiwi