HN user

rafaelcosta

218 karma

Software Engineer

Posts1
Comments17
View on HN
Leaving Mozilla 1 month ago

I don’t think that it is reductionist at all. The examples provided are either qualified with “dedicated” or “many of”. It’s also not surprising at all that people who have an interest in driving the goals of the organization usually gravitate more to operational roles and people who have no interest in it at all gravitate towards organizational roles – but that’s not a rule.

I would totally be pissed as someone in an “organizational” role of someone reduced me to someone “not interested in the goals of the organization”, but magpi3 didn’t do that. They correctly stated a pattern. If you are around organizational/administrative people, ask yourself honestly if the pattern isn’t the least bit accurate…

”Facebook is paying out to creators of monetized content because that content is popular”

Would also work as a headline. But wouldn’t attract as many clicks I guess. The implication that Facebook is actively promoting a certain view point is disgusting, and old media loves to do that (even though they were historically the ones doing so). I’m all for local filtering (on some level) and preventing foreign interference on local political matters, and social media companies ought to do better. But I twist my nose at old media shamelessly trying to manipulate the views of people on tech. And this is Facebook we’re talking about here…

As it should. Date notwithstanding, I would actually enjoy if there was a manually induced latency penalty for "legacy IP" that needs to be manually turned off on Linux. I know some people don't care at all, but the internet was made to be addressable. IPv6 is the only shot we have to go back to that.

I don't get why this applies on the Cloudflare outage but not on the AWS ones... I'd argue that the big cloud providers are WAY more impactful when they go down than Cloudflare. The only difference is that the average techie uses Cloudflare more and sees the impact more, but this point was already there before...

There's a reason why this went from widely supported/used to... not so much. And even if most people claim it's big-co's locking down their ecosystems (which is partly true), the "extensibility" of XMPP allows for a very convoluted ecosystem with some servers supporting certain XEP and some not. Also, sorry, but XML just sucks to work with nowadays :(

Easy from your point of view... This is the argument I mostly hear from Apple folks, but my experience (especially with less tech savvy folks) is that they have no idea where or how to cancel a subscription on IAP and they think that the multiple "Apple" charges are just some iCloud thing or something along those lines. With Credit Card flows the alarm bells go off waaaay earlier: when a website asks for their CC data, they immediately scrutinize more (and thus, conversion rates are lower)

Right now, yes, but there's a potential to:

- Most legit services move to a web based Apple Pay (note to the unaware reader: this is NOT In-App Purchases and has never had 30% fees) due to the ease of implementing and lower fee (easier to do cross platform + web) - Non-legit developers keep the In-App flow

Over time this would skew In-App Purchases to be scammy-only (and therefore, easier to spot). I'm sure people at Apple consider this possibility too – and therefore, now that there's actual competition, IAP flows will probably have to change to prevent this and compete for actual developer preference (and keep it a viable legit-developer choice)

There's a whole class of sh*t-software that only exists (and is profitable) because users subscribe to them and then forget – primarily because the subscription fee is charged as "Apple" on their Credit Card. I wonder what's gonna happen with this type of scam.

I'm wondering what the "because when we read it in, we mangle it" part really means... does this mean that there's no way to reference the commit (signaling that it's just a reference and has no actual data) without actually reading the contents of it?

-- Update: just realized why it wouldn't make sense: `git push` would send only the delta from the previous commit and the previous commit is... non-existent (we only know it's ID), so we'd be back in square 1 (sending everything).

Let's go back to each city having its own time. _Because making train companies happy is so much more important than making users happy?_

All jokes and "snarkiness" aside, it's just a matter of habit. If the whole world used UTC and working hours/social time were set differently per-country, I bet we'd get used to it eventually.