🅿🅸🆇🅴🅻

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.

‘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.

Where is Captain Planet?

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.

No, logins should be harder in order to be secure. Hence the addition of 2FA (which is also incompatible with your proposal).

As developers, we strive to make things more secure, not less, and unfortunately, good security always comes with the trade-off of less convenience for the user (larger entropy passwords, session expiration, captchas, etc).

Now, of course, it depends on how sensible the data in that account is. I wouldn’t want this for my email account, for example, or online password manager, which are the entry gates to all my other accounts. The Kagi search engine offers the possibility to login on another device via a session URL which you can copy-paste. And this is fine, if the site / app clearly states the dangers, implemented it securely, tracks and lists the sessions and allows you to invalidate a session for all devices, and you are fine with potentially disclosing the data for that account (forgetting to log out, or disclose the session URL somewhere) - which is not much, as they don’t log the searches, only the daily counts. And their use-case makes sense, people aren’t used to authenticating in order to search something on the internet.

So, this should be an optional feature offering from the website / app, not built-in in the browser which would make it trivial to be abused by anyone.

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.

Instead of my ID, I submitted a picture of dolphins and the text “So long and thanks for all the fish!”. And never came back.

I assume blocking is supported by the server so it should be more optimized / faster. Filtering is a client-side feature.

The position is randomized.

Is Keepass there? Good. Upvote.

Unique style paintings will become even more valuable in the future. Generative AI only spews “art” based on previous styles it learned / was trained on. Everything will be even more rehashed than it is today (nod to Everything is a Remix). Having a painting made by an actual human hand on your wall will be more ego-boosting than an AI generated one.

Sure, for general digital art (ie logos, game character design, etc) when uniqueness isn’t really mandatory, AI is a good, very cheap tool.

As for the “everyone becomes a programmer” part… naah.

Turris Omnia. Powerful hardware, auto updates, config backup / restore (with anti-bricking feature), SIM slot, etc

Excuse my ignorance, I don’t know much about 3D printer material types / filament resistance, but from a few 3D printed cases for small devices I had, isn’t the plastic brittle? Or the joints of layers. Especially for a long cylinder shape where force is going to be applied to. I dropped 2 cases on the floor and they broke in multiple pieces where 2 layers of filament joined. But granted, their thickness was 2-3 millimeters.