x0x0
Joined 13 years ago
Joined 13 years ago
> That's a bold accusation. Would you care proving which bits of the code are "stolen"?
https://github.com/eolix/photosuite/issues/77#issuecomment-5...
to banning photopea, to when photopea responds with a 2nd account re: some duplicate code which is very hard to explain w/o being, well, duplicated to what you pasted above.
I really dislike this point of view.
1 - we're all going to suffer because meta are scum. It's not "all application developers", it's "exactly who you assumed it would be", and also too, "exactly the same scum who've spent the last 10 years working around privacy controls any possible way they can and deliberately obfuscating the choices people make around their privacy." The people who made pervert glasses and did covert web-to-app tracking by opening local ports [1] and bought sketchy spyware to track everything you did and scurried away from the light the second someone asked about it [2], [3]. And on and on and on.
Spotify has long asked for it and... they use it to copy my local mp3s onto my phone so I can listen to them away from my computer. It's awesome.
This doesn't mean that Apple isn't champing at the bit to use Meta as an excuse to screw all software developers. If Apple cared about their users, they'd do something like revoke Meta's software keys and leave responsible developers alone. Alas, Apple will obviously exploit this too :(
[1] https://localmess.github.io/
[2] https://en.wikipedia.org/wiki/Onavo
[3] https://uk.practicallaw.thomsonreuters.com/w-040-4130?transi...
> we'll stop supporting RSS feeds on November 13, 2026
3 sentences later:
> RSS has been a beloved part of the open web for a long time, and we’re grateful to everyone who used it to stay connected to Reddit.
That's not to say that pets can cause tons of damage: if someone let's a cat spray inside and doesn't immediately clean it, that can cost tens of thousands if it seeps down to the underlayment. But (1) that ain't getting covered by the $50 - $100 they want to gouge people for; and (2) tenants are liable for that either way.
> When TechCrunch asked Mullenweg if his comments about being back as CEO were legitimate, he promised a blog post was coming. When it arrived, however, it was about him buying a houseboat. When we asked if his comments about being back were also him trolling, he replied, “I’m not a troll I’m a pirate, obviously.” Mullenweg never provided any official comment about his return, but noted on X that this was likely the fifth time he’s faced a “coup.”
And like all well-run companies, it's not clear who the ceo is.
The reason to store that data is to be able to build analytics and funnels you didn't anticipate and construct them retrospectively. You can of course save massive amounts of storage by building rollups and aggregating, but that prevents you from being able to eg change the funnels and see the funnel in the past.
10M users × 100 events/day × 1KB ≈ 1TB/day. A couple years gets you into PB range.
The other obvious thing is logs. Being able to have a vulnerability then go back in time and see if you were exploited is super valuable. See eg log4shell: if you kept records, you probably could go back and see if you'd been exploited.
I went to the dentist recently. They wanted to do a "deep cleaning". cost: somewhere between $0 (covered) and $5k (fully out of pocket). I asked the obvious: that's one hell of a range. "Depends on how much the insurer will pay." They weren't happy when I demanded to know that number before committing, as it takes them hours on the phone.
https://www.androidauthority.com/google-account-bans-3654171...
Not taking a side, but I remember that too and had looked later.
That said, I deliberately don't trust any google services. Fastmail is great; you all should try it. Google capriciously bans accounts, so keep your email elsewhere.
That's some revisionist lies. Slow, crashy, a memory pig with a big leak problem, stuck on a single process architecture. It was none of fast or modern. Whether it was extremely nice to use is debatable, but lots of people rapidly voted by switching.
It very regularly crashed and took down the entire process.
It's fine to lament the Chrome monoculture, but we misdiagnosis it if we don't remember the seeds were sown via Mozilla's incompetence. They made it crystal clear they couldn't and wouldn't do better, and the next 5 or more years made that inarguable.