Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
flutas
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
121.
▲
by
flutas
2y ago
Nah, it's absolutely all apps on google play. > For a period of three years, Google will permit third-party Android app stores to access the Google Play Store's catalog of apps so that they may offer the Play Store apps to user
122.
▲
by
flutas
2y ago
WPEngine has already done both of those. Literally at this point the only customers this is hurting are standard WordPress users not on WPEngine.
123.
▲
by
flutas
2y ago
The Tweets original content was[0]: > Automattic's security team has responsibly disclosed a vulnerability in @wp_acf to @wpengine. As is standard, they have 30 days to issue a fix before public disclosure. We have reserved this CVE
124.
▲
by
flutas
2y ago
The other comment has a link with a good overview of the fight, but there's a tiny but of nuance to why this is especially "bad." Essentially they are announcing a CVE on software while holding the fix for it hostage to norma
125.
▲
by
flutas
2y ago
Would you mind posting what would be the better headline instead of a shallow dismissal of it? I actually struggled with a good one and felt this is the most fair take when seen in context of A) Matt's post <8 hours before this disc
126.
▲
by
flutas
2y ago
Not that I'm aware of. Couple that with Matt's clearly hinting post earlier today[0] and it really feels... calculated. Just another thing for them to throw on the lawsuit I guess. [0]: https://x.com/photomatt/
127.
▲
by
flutas
2y ago
Yup. Basically: 1. Ban them from updating the plugin. 2. "btw, here's a CVE for that plugin, you have 30 days until it gets removed or ownership changed." You can guess what's going to happen next... "Oh, they didn&
128.
▲
Automattic turns to weaponizing responsible disclosure against WP Engine
(twitter.com)
63 points
by
flutas
2y ago
|
31 comments
129.
▲
by
flutas
2y ago
> I wonder how much of that was just echoing the corporate mission statement of Automattic for the sake of any colleagues who happen to stumble across the blog. It's fairly obvious that's what it is. Or they are being forced to
130.
▲
by
flutas
2y ago
I refuse to even look at devices like this anymore after they removed features and locked them behind a paywall. If you want ongoing revenue from a device, don't charge up front. If you want to charge up front, don't try to get on
131.
▲
by
flutas
2y ago
Right, this all feels like (and I'm not trying to be rude with this, I'm speaking from experience) a mental break. Or he's got some sort of vendetta that he feels burning everything down is worth it over. Some of his comments
132.
▲
by
flutas
2y ago
> Automattic employs ~100 people that work full-time on WordPress.org. I can appoint them into positions on WordPress.org , if I think that's appropriate. So are you now using company resources for personal projects (as they point
133.
▲
by
flutas
2y ago
More like tithe it all to the LDS.
134.
▲
by
flutas
2y ago
> Why is WP.org obligated to provide free services to WP Engine and their users? Why the entitlement? Think about the questions I asked about this. Why did I ask for API PRICING if I think anyone is entitled to it for free? Stop trying
135.
▲
by
flutas
2y ago
> Which I believe was their legal response Really? I see extortion in those texts, not a legal lawsuit to enforce a trademark. I mean, is this a legal and well crafted lawsuit? Or just extortion. > Just called. Should I run these slid
136.
▲
by
flutas
2y ago
> In fact, you know what confuses regular users ? wordpress.org vs wordpress.com. Yup, it's mentioned by others in this thread but I was also confused by this for a small period before doing further research early in the .COM beginn
137.
▲
by
flutas
2y ago
> WordPress.org isn't renting anything and WP.org isn't being targeted at all by WP Engine. > The analogy with AWS doesn't work because with WP money doesn't change hands. WP Engine or their users aren't payin
138.
▲
by
flutas
2y ago
> unless you really meant a “donation” from the foundation to the company Yeah, that's what I meant. Essentially laundering money through the 501c3 to try and negate taxes. In this case actual money never changed hands, but what is
139.
▲
by
flutas
2y ago
> The resources of Wordpress.org and the Wordpress Foundation should not be leverage in this dispute. I honestly wonder if it crosses any legal boundaries. From what I can tell, it's essentially the non-profit acting on commands fro
140.
▲
by
flutas
2y ago
In short, section 174[0]. It pushed almost all SWE jobs to be classified as R&D jobs, which changed how taxes are calculated on companies. They have an example at [0], but I'll copy it here. For a $1mm income, $1mm cost of SW dev,
141.
▲
by
flutas
2y ago
Honestly not that surprised, the only surprising thing to me is how little of a slap on the wrist this feels like. It felt like a shaky premise at best as far back as I can remember. Even "standard" things often have many intricac
142.
▲
by
flutas
2y ago
I doubt it has anything to do with the battery, pagers typically use the far more stable (and less energy dense) NiMH composition over a typical lithium one.
143.
▲
by
flutas
2y ago
I think the intent was to disable a bunch of fighters honestly. Make the pager ring, they grab it, it explodes in their hand disabling them for life and making them useless for the soldier role.
144.
▲
by
flutas
2y ago
Also pagers typically use NiMH batteries, not Lithium. So take those estimates down another notch.
145.
▲
by
flutas
2y ago
> Hard to see how a remote exploit could detonate the battery Especially seeing as pagers typically use more stable NiMH batteries over lithium ones.
146.
▲
by
flutas
2y ago
Just did it myself today. Personally it was fairly easy using the standard reset UI through settings over doing a full recovery wipe. 1. Upgrade to Sequoia 2. "Erase all Content and Settings" from Settings.
147.
▲
by
flutas
2y ago
Good call-out!
148.
▲
by
flutas
2y ago
As the other commenter said it does seem like Apple might have either straight up removed it or is disabling it in software entirely for now. Comparison page lists the "Blood Oxygen app" for the S6 through S8, but S9 and S10 both
149.
▲
by
flutas
2y ago
Yeah, I should have said with rather than for. They're doing server side verification of the TEE environment using their protected download service from what I can tell. https://github.com/google/private-compute-se
150.
▲
by
flutas
2y ago
It does the same thing re: hooking, but downloads most (if not all?) of the models, only at the end does it fail with "precondition check failed" from the server which aicore just repeats. I haven't gotten further in it to fi
More ›