I had a similar thought - it seems like most of the concerns could be addressed by adding better request tracing and improving the resiliency of the existing system. I wonder if this is just the result of an organizational tension where the load balancing team isn’t motivated to address this particular use case (which seems likely if the organization is large enough).
AFAIK in the current setup, only the UI is Apple's; any time you message customer service or open a dispute, that is handled directly by
Goldman employees, and decisions to raise/lower your credit limit are also made by Goldman. All of those parts will be handled by Chase now.
AFAIK, "email HTML" isn't standardized either; most organizations that make nice-looking HTML emails have to do a ton of testing across different clients and come up with workarounds to make everything look consistent.
My personal favorite UX-failure-of-the-moment in Teams: If I open the teams tab > Browse, it shows a big list of company-wide channels that I could join. There's a search box, but unlike any normal search box, it only does a prefix search, so if your channel is named "some test channel", and you search for "test", it doesn't find it! Several times I've given up at guessing the right channel name and had to ask coworkers to tell me the exact name in order to join.
I used to have a problem very similar to this, where the "working hours" Teams showed on my profile were in the wrong time zone. It turned out the solution was to go deep into some submenu of the Microsoft account settings website (_not_ anywhere in the actual Teams app) and edit the account time zone preferences, so perhaps look into that and make sure those match the local settings in the Teams app.
In the US, most rentals (except for very cheap ones) include a fridge/washer/dryer/dishwasher, but if you're buying the property, typically only the dishwasher is included unless you negotiate with the seller.
Reducing this to age is overly simplistic. When Linux was younger and simpler, it may've been easier to fork, but today it's a massive system with huge inertia behind it. Even if you are right in principle regarding your changes, it's extremely hard to overcome that inertia.
In the related submission on this topic [1], the author makes this argument in a lot more detail, that it's essentially impossible to make a Linux fork sustainable without massive investment that no one can realistically obtain.
> I am 100% sure you, as a manufacturer, could develop a very lightweight shim over a linux or BSD kernel that has significantly better performance than Android does
I’m not sure why this would be true, unless you’re willing to cut back significantly on features. Google already spends quite a bit of effort on performance improvements, and most manufacturers aren’t exactly known for being able to produce high-quality software.
There have been a couple projects that have tried to make phones based on pure Linux (Librem, Pinephone). Their performance is limited a lot by not having good CPU options, but it doesn’t seem like they’ve been able to achieve much performance improvement on the software side either.
I think it may be linked to the Bing integration. If I ask about my location in a new conversation, I don't get back anything. But if I start with your example query, and then follow up with "is it available where I am?", I get
> To determine if Stripe Connect is available where you are, could you let me know your country? If you prefer, I can also look up Stripe's support availability based on the country linked to your query.
[me] yes, do that
> Yes, Stripe Connect is available in [my country], including [my city].
I'm having a bit of a hard time imagining what kind of payment Google could make under this structure. Do you have something in mind?
I agree that if Google was paying a browser for something other than default search placement, that would likely fall outside the scope of the proposal. But historically, default placement = traffic, and is also the only leverage the browsers have - ie if Google wasn't the default, Google would only get users who explicitly selected it, and if Google knows all of their users are actively selecting them already, they have no reason to pay extra for that traffic.
API access seems like a good alternative way for Google to monetize, but it doesn't solve the problem of providing funding for browsers (except in your case, since you're combining a search engine and browser in one company). Or am I missing something?
This has already been discussed extensively in prior threads, but the biggest question is, how does a spun-off Chrome get funded?
Chrome/Firefox/Safari all cost hundreds of millions of dollars a year to maintain. Currently, Safari and Firefox both make essentially all their revenue through default search agreements. Chrome, Edge, and now Brave are produced by companies that also own the search engines, so they're essentially a loss-generating product, that exist because they cancel out distribution costs that Google and Microsoft would otherwise have to pay other browsers.
But the DOJ order is also asking to ban payments between search engines and browser makers:
> As detailed in Section IV, the PFJ prohibits Google from providing third parties something of value (including financial payments) in order to make Google the default general search engine or otherwise discouraging those third parties from offering competing search products
With that revenue gone, the only real options to fund a browser are:
* Directly charge users for it. This is effectively a non-starter, because the vast majority of people aren't willing to pay for it.
* Insert ads or sell user data - users also hate this, it's probably not legal in the EU, and it may not be legal in most of the US in the future either.
* Use the browser as a platform to push some product that does make money - a non-Google search engine? A social network? An LLM interface?
Alternatively, a narrow reading of the proposed order is that this only applies to Google. In that case, perhaps Bing or OpenAI takes over all the distribution agreements and becomes the top search engine. Whether that's better for consumers seems fairly questionable.
> As set forth in Section IV, the PFJ prohibits Google from offering Apple anything of value for any form of default, placement, or preinstallation distribution (including choice screens) related to general search or a search access point.
That’s not stupid though. It might seem obvious, but then you have things like sun butter, which are specifically designed to imitate peanut butter while not having peanuts.
Sure, you can look at all the words on the package and ingredients and figure out if something probably contains allergens, but the point of the rule is that it gives you one standardized line of text that you can read and be 100% certain whether something is safe for you to eat or not.
All of the domains are pointing to the same hosted services run by Firebase, meaning only Firebase themselves has the private key, so the customers whose domains use the certificate shouldn’t be able to MITM anything.
Cloudflare used to do (or maybe still does?) this with their free certificates as well.
Not to diminish OP’s project, but the stated goal of “know when each transit line has an upcoming train/tram/bus” is probably already achieved by https://transitapp.com/ - the default view when you open the app is a list of nearby transit lines, sorted by distance and showing the next departure for each.
If you’re editing Openstreetmap, using data from Street View is prohibited by the license, even if you pay for it I believe. However, Microsoft has licensed Bing Streetside for this use for free; the dataset isn’t as good as Street View, but is much better than Mapillary.
I think the typical approach is to use the regular site name (so just "Google Arts and Culture") and let people click on it assuming there's something interesting about it to justifying being posted. That doesn't work super well when the original title is vague, like this one, but I think it does correspond to this guideline:
> Please don't do things to make titles stand out, like using uppercase or exclamation points, or saying how great an article is. It's implicit in submitting something that you think it's important.
If you assume there is some population whose house size is mismatched to what they want (in particular, the house is too large), lowering the transaction costs could encourage more people to move, which would mean that more people end up with an appropriately-sized house.