I hope you didn’t literally use XOR

It's XOR(key, block) with IV and chaining: https://github.com/RommieEcho/qrcatalyst-open/blob/main/src/routes/anon/XORCipher.js

Since it's chained at the byte level, you can strip it out by just XORing each byte against all following bytes. Then the IV can be XORed out of the first block, at which point you have just a series of XOR(key, plaintext) blocks that can be attacked with conventional methods.

Isn't that a classic corporate raid technique? Sell the company's assets to you or an organization you control, then lease them back to the original owners.

This isn't just about teens - the article shows that every age under 45 is less happy, and - excluding a brief bump in the late 20s - people just keep getting unhappy as they get older. There's no "it gets better" age to look forward to.

From the Privacy Policy:

Your Location

When you create an account, we ask you to share your location with us through the App in order to use all features. We use your location to determine your distance from other users and to help you find personals and missed connections in your area. We collect this information automatically by collecting your Internet Protocol address and your Unique Device ID. It is possible to opt out of sharing your location at sign up, but app functionality is limited.

yeah, don't use this app.

I have concerns about this site, tbh. I can't find anything overtly wrong, but a few things stand out:

• Unclear focus / purpose. (is this for dating? social interaction? both?)
• App-only model, but with a read-only webview for some reason. (Why would you do this, except to allow anonymous scraping and/or collect extra data?)
• Supposedly built by a solo trans person, who somehow has resources to create a website and two separate apps.
• Includes an iOS app, which has hurdles that few indies are able to deal with.
• Closed-source, no clear ownership or transparency.
• App collects location data, according to Google.

It could just be my paranoia speaking, but I'd advise against using this. It feels like a honeypot or some kind of trap.

That's not entirely true. Practice is important, but homework actually has a negative impact on learning: https://hachyderm.io/@Impossible_PhD/112969358305278574

In my experience, the larger threadiverse instances have gradually collected the worst ex-redditors, who have brought the worst of reddit's culture. I'm unfortunately not surprised that lemmy.world has queerphobic mods, given how the users behave. 😕

My product manager is doing the opposite - pushing us to replace "bandwidth" and "effort" with "time". We're now expected to provide an accurate hour estimate for all work items, projects, and bugs. Getting it done later or sooner is penalized on the metrics.

Thanks for the reminder! I almost forgot to set up my repo. 🤦‍♀️ I'll be publishing my solutions on GitHub for anyone interested. This year I finally got around to restructuring things to keep the input files out of git, so I won't have to feel guilty about leaking the problem inputs.

I appreciate the transparency through all of this. It's nice to know about the problem while there's still some time to handle it. To be honest - I probably would not follow Beehaw to any new non-federated platform. Its nothing against Beehaw (I love this community and its admins) but I'm just not convinced that we could ever attain enough regular users to keep critical mass on the niche topics I follow. That's the real advantage of Lemmy - all (well-behaved) instances get to share their user base.

Unfortunately, I also understand why staying on Lemmy might not be an option. Same with forking or using another Fedi software. Either way - I trust y'all to consider all the options and make the best choice. 🐝💙

I agree that this is nothing to panic over, but I want to clarify that Lemmy is not safe from this. Lemmy and Mastodon both use the same protocol (ActivityPub) and that's also the protocol that Threads will use to federate. Just as Mastodon users can like, boost, and reply to Lemmy threads / comments, Threads users will be able to do the same. That's why it's important to defederate Threads on all ActivityPub-enabled instances.

I was working through a list of nature-related names, looking for an uncommon one that still sounded like a real name. I was almost ready to try out "Ember", but then I saw "Hazel" and it just clicked. So that's what I've called myself ever since!