🅿🅸🆇🅴🅻

And some copyrighted shit from Dolby. Granted, header files only.

At first I was… wow, no shit! Open source Winamp!

But then I went through the Github issues (because, 6 hours since first commit and already 5 issues open?). As someone else put it, “This has got to be the most embarrassing open-sourcing i’ve seen to date.”. The licensing is a mess, the coverup is a dumpster fire. By tomorrow this is going to be as viral as Twitter’s “open sourcing” of its recommendation algorithm they did last year. Not sure if I should make coffee or popcorn in the morning.

Those share buttons are trackers themselves. So it’s not about “supporting” those websites by publishing content to them, it’s about undermining the privacy of your readers and doing the opposite of what you preach, and “supporting” those websites by feeding them much more valuable user data. As another comment said, just put a button to copy the permalink and let them paste themselves if they want to share.

As for you sharing a link on the mainstream social media platforms yourself, I’d actually encourage that. Cory Doctorow auto-publishes links (not content) to his articles on as many social media platforms as he can (sorry, can’t find the article in which he describes it). The point is that he still retains control over his content by hosting it himself, he controls the (lack of) trackers and ads, and gaining traffic from these platforms is still to his and his potential readers benefit. Bending your rules a little to reach more people and maybe even convert them to be more privacy-aware is fine.

deleted by creator

‘no immediate timeline’ toward monetization

Soo, starting tomorrow

Pffffft.

I second the idea of a VPN instead of directly exposing devices or software to the internet. Requires more work and learning but it’s more secure. I would argue that well-known VPNs are more scrutinized and pentested than any camera software ever.

A hash has a fixed length, including MD5. There’s no reason to cap password (input) Iength. You can hash the whole bible and still get the same length hash. So either they don’t even hash it, they’re idiots, or they try to be unnecessarily cautious to avoid some other limit / overflow, like POST max size (which would still be counted in at least KB, not several characters). The limit on what special characters you can use is also highly suspicious - that’s not how you deal with injections / escaping your inputs.

I’m rebooting my router every week via a crontab because some dynamic dns update process fails from time to time and I find it hanging. No time to debug the actual problem.

Well, that’s what you get for hosting on a Windows server. XAMPP / WAMPP should only be used for local development environments. And I’m sure they still have horrible non-production config defaults.

My best friend, the Uber driver, which I prefer to shut up all the way home. But hey, what are friends for, he keeps me hydrated!

I’m not sure what you’re comparing it to. Keepass is free too, in fact it’s open source. In my opinion, local software and database that is under your control is always superior to cloud.

Keepass over Bitwarden offers a lot of plugins and integrations, again, if you want more customization or automation.

But, I would say you can use any online password manager as long as it’s end to end encrypted, so Bitwarden is a good choice.