# Dropping iOS 15 & other old browsers in July 2025

**URL:** https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131
**Category:** Announcements
**Created:** [March 20, 2025, 1:57pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131 "2025-03-20T13:57:41Z")
**Posts on this page:** 20
**Page:** 5

<div class="post-metadata">

### Author: ![Tech2](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@Tech2](https://meta.discourse.org/u/Tech2)
#### Post date: [April 6, 2025, 2:25pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/83 "2025-04-06T14:25:57Z")

</div>

If Discourse truly has tens of millions of users, locking out even a small percentage of them in May is a poor decision, especially just to add a few non-essential features. Users with older devices/OS’s are aware of potential risks, are smart enough not to do dumb things, and have valid reasons for not upgrading. Dismissing them as illegitimate users is unfair and contradicts the inclusive spirit of a ‘community.’

---

<div class="post-metadata">

### Author: ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [April 6, 2025, 3:46pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/84 "2025-04-06T15:46:57Z")

</div>

I’ve been following along here, and am interested in continuing to better understand what the impact of this change will be on different communities.

The way I’m thinking of it, for a given community, one could break that down as follows:

- `T` total number of users in the community
  - `x` number of those users impacted by this change
    - `a` number of those users who don’t have an acceptable workaround
    - `b` complement of `a`

  - `y` complement of `x`

- `t` time we wait to make this change.

For a given community, I assume there _is_ a high probability that `x > 0`, and that even `a > 0`.

We could think of the impact of this change on a given community as being modeled as a function `f(t)` that returns the values `T, x, a`.

If we accept that `x` and `a` will be hard to get to 0, what should we be aiming for?

Perhaps we bucket impact by `a/T` and set some threshold on what we find acceptable.

We could think of this impact of this change on communities as a whole as being a similar function `F(t)` that returns a population of communities `[]{T, x, a}`

We could use the same threshold above and measure how _many_ communities are impacted beyond what we’ve determined as acceptable.

If we were to wait another year for this, I assume that for many communities, both `x` and `a` would decrease, but still be greater than 0.

So there’s no perfect decision here.

Then, what should factor into our decision?

What is an acceptable value for `a` for a given community? How many communities are we willing to have cross that threshold? should we make this change?

We haven’t done anything as rigorous as this, but we have looked as some of the data we have to inform our decision, and felt like May is a reasonable answer for `t`.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [April 6, 2025, 4:14pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/85 "2025-04-06T16:14:59Z")

</div>

I remember this topic from a couple of years ago about a similar situation which I found quite moving:

> [@Backwards compatibility with older browsers](https://meta.discourse.org/t/backwards-compatibility-with-older-browsers/255820):
>
> I help run a messageboard for people affected by a neurodegenerative disease that is powered by Discourse. I keep the software up to date by following the security list at [Commit search results · GitHub](https://github.com/discourse/discourse/search?utf8=%E2%9C%93&q=SECURITY&type=Commits) and updating whenever there is security issue. However this has the unintended side effect of locking out increasing number of users who have older machines. It has locked out one user who is a carer for her husband and only had access to the messageboard through an iPad that no longer receives …

Perhaps @codev has some tips for how they (and their community) handled this at the time?

Out of curiosity, how is the deprecation handled for those sites tracking `stable`? As it’s between major releases, will they see this warning or will it just happen next time they update to the next major version?

---

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [April 6, 2025, 7:14pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/86 "2025-04-06T19:14:14Z")

</div>

> [@mcwumbly](#):
>
> If we were to wait another year for this, I assume that for many communities, both `x` and `a` would decrease, but still be greater than 0.

It feels to me the best answer (for the users) is not about waiting for some while until not too many people are affected, but committing to implementing workarounds - graceful degradation of the forum, retaining read and write capability - before dropping support for older browsers.

What’s the rush with implementing new features that demand newer browsers? Why not always have a graceful fallback?

---

<div class="post-metadata">

### Author: ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [April 6, 2025, 7:38pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/87 "2025-04-06T19:38:20Z")

</div>

> [@Ed\_S](#):
>
> What’s the rush with implementing new features that demand newer browsers? Why not always have a graceful fallback?

I think “rush” is the word I’m pushing back against here, by describing the decision as a function of time, with some impact the decreases but may never reach zero

If we said we were planning to do this in 1 year from now vs. 1 month, does that feel like a rush?

Assuming I can ignore that word for now and reframe the question without it:

> What’s the [reason for] implementing new features that demand newer browsers? Why not always have a graceful fallback?

It’s about cost, and the relative value of doing this vs. doing other things.

Implementing those fallbacks would take attention and time. And maintaining them would do the same. That’s time and attention that isn’t available for other things.

It may be something we consider in the future, but at the moment, our assessment is that we have to make some tradeoff here.

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [April 6, 2025, 7:44pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/88 "2025-04-06T19:44:44Z")

</div>

> [@mcwumbly](#):
>
> The way I’m thinking of it, for a given community, one could break that down as follows:
> 
> - `T` total number of users in the community
> - `x` number of those users impacted by this change
> - `a` number of those users who don’t have an acceptable workaround
> - `b` complement of `a`
> 
> - `y` complement of `x`
> 
> - `t` time we wait to make this change

Maybe a [data explorer](https://meta.discourse.org/t/32566?silent=true) query to audit browser versions users are using?

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [April 6, 2025, 7:51pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/89 "2025-04-06T19:51:08Z")

</div>

> [@mcwumbly](#):
>
> I think “rush” is the word I’m pushing back against here, by describing the decision as a function of time, with some impact the decreases but may never reach zero

Indeed “rush” is not really accurate. Though maybe earlier warnings their browser support is ending ETA.

Project like Discorkie maybe the key for folks who are not willing/able/capable of exploring an OS change. Otherwise would need some kind of fallback basic interface. As the affected user can still browse the forum in a read only mode. How difficult would it maybe be to add ability to post/respond using a JSON load like Discorkie while still using the other code for decoration like in the current read only mode?

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [April 6, 2025, 8:26pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/90 "2025-04-06T20:26:54Z")

</div>

> [@Heliosurge](#):
>
> Project like Discorkie maybe the key for folks who are not willing/able/capable of exploring an OS change.

Something along those lines seems like the obvious solution to me. That way the Discourse team can keep focusing on providing the best possible experience for modern browsers without having to complicate the code with a bunch of fallbacks.

---

<div class="post-metadata">

### Author: ![thorny\_locust](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@thorny\_locust](https://meta.discourse.org/u/thorny_locust)
#### Post date: [April 7, 2025, 1:31am UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/91 "2025-04-07T01:31:30Z")

</div>

Late 2014 Mac Mini running 10.13.4.

I may be able to update it somewhat from that, though I’m not sure that it’ll fix the problem. I’m looking into update possibilities; but I can’t afford to replace it. And even if my particular device will update – that doesn’t change the overall issue.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [April 7, 2025, 2:18am UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/92 "2025-04-07T02:18:24Z")

</div>

Have you considered using bootcamp on the machine and updating to Windows 10 (which will give you till 14 october) or Window 11? It should work according to the internet and will put you on a train that is still getting security updates.

There is enormous amount of risk having an OS that is no longer getting security updates on the wide Internet.

OSes that get updates, are only vulnerable to zero day exploits that cost millions of dollars in the black market.

OSes that are no longer updated are vulnerable to **known** and disclosed issues, that leaves high risk around junior hackers just enlisting a computer to a DDoS botnet or worse still crypto style attacks where you have to send money to decrypt your computer.

We often underestimate how bad this can be, but there have been quite a few attacks we have seen over the past 10 years that can take out a computer simply by visiting a website.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 7, 2025, 1:58pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/93 "2025-04-07T13:58:02Z")

</div>

> [@thorny\_locust](#):
>
> Late 2014 Mac Mini

I’ve read that this one support updates all the way to Monterrey, which is still supported by Firefox, so you get the same version of Firefox I’m running right now.

And you still can run either Windows 11 like @sam suggested or Linux as options. Both will give access to supported browsers.

---

<div class="post-metadata">

### Author: ![thorny\_locust](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@thorny\_locust](https://meta.discourse.org/u/thorny_locust)
#### Post date: [April 7, 2025, 2:07pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/94 "2025-04-07T14:07:23Z")

</div>

> [@sam](#):
>
> Have you considered using bootcamp on the machine and updating to Windows 10 (which will give you till 14 october) or Window 11?

I don’t have the time to first learn how to make my old Mac run Windows and then learn how to use a Windows system that I don’t want and that apparently even a lot of Windows people don’t like. I’m running a farm and will be extremely busy between now and October 14 and for some time after that.

And wouldn’t I have to pay to use the Windows system, with money that I haven’t got?

> [@Falco](#):
>
> I’ve read that this one support updates all the way to Monterrey, which is still supported by Firefox, so you get the same version of Firefox I’m running right now.

Yeah, I’m looking into that, and might try that. Seems like it might be a temporary fix at some risk of screwing up something else I routinely do on the Mini; but it might also stand some chance of fixing something else currently not working right.

---

<div class="post-metadata">

### Author: ![thorny\_locust](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@thorny\_locust](https://meta.discourse.org/u/thorny_locust)
#### Post date: [April 7, 2025, 2:15pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/95 "2025-04-07T14:15:30Z")

</div>

I just posted in that thread, or at least tried to; and now the only thing I can see is

“HTML content omitted because you are logged in or using a modern mobile device”

How do I get that thread visible again? and what sense does it make to tell me I can’t see it because I’m logged in? and yes I’m using the desktop.

---

<div class="post-metadata">

### Author: ![JNighthawk](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@JNighthawk](https://meta.discourse.org/u/JNighthawk)
#### Post date: [April 7, 2025, 4:50pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/96 "2025-04-07T16:50:57Z")

</div>

Sorry for the interruption, but I would rather ask: _“What is the reason for giving up on many users just to implement **one** useless and frankly even annoying feature at all costs?”_

Because, let’s be honest, who cares about managing alternative colors, given that most users follow forums that use your platform _for their content_ and not for aesthetic appearance?

If you look closely, the “relative color syntax” feature is essentially the only one that is not supported by many of the older browsers, while the other two are supported (or at least, even my old Firefox passes the tests for the other two, as useless as they might be, and only fails on the relative color syntax, which is TOTALLY unnecessary for forum content).

It’s not so hard to decide not to implement something totally useless, right?

Also consider that, according to some sources, Windows 7 is completely insecure (which is false, but let’s leave that aside for now), and that it is no longer used by anyone… According to various online analysis sites (none of which give exact numbers, so it’s an estimate), there are still between 60 and 100 million users for various reasons (backward compatibility, software that no longer works on Win10/11, lack of financial means to upgrade, CNC machines that run on Win7Pro but not on 10/11, and others).

Although this is a small percentage compared to the estimated 1.5 billion users who use a PC (NOT all Windows, including Mac, Linux, etc.), it’s still not insignificant… Considering that, since discourse is " infiltrating" many environments, even just 1 or 2% of these users who use any service based on discourse (probably more, but let’s be conservative), and if they have not yet switched to something better, like newer machines or operating systems, they may be unable or unwilling to do so now. This represents a potential user loss (excluding bad publicity and loss of trust) that could range from a minimum of 60,000 to a maximum of 200,000 (or more). I find it hard to believe that the discourse management cares little about this… Am I wrong?

Wouldn’t it be better to simply remove the pointless implementation of the only “feature” (let’s call it that, because I don’t want to be rude) that causes most of the problems, and only implement the other two, provided they are really useful?

---

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [April 7, 2025, 5:51pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/98 "2025-04-07T17:51:42Z")

</div>

As moderator, want to jump in here. This is an important topic and we appreciate hearing feedback from many voices. We are listening! However, I do want to remind about the [community guidelines](https://meta.discourse.org/faq). Let’s keep it civil, please. 🙏

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [April 7, 2025, 8:26pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/102 "2025-04-07T20:26:58Z")

</div>

> [@thorny\_locust](#):
>
> > [@sam](#):
> >
> > Have you considered using bootcamp on the machine and updating to Windows 10 (which will give you till 14 october) or Window 11?
> 
> I don’t have the time to first learn how to make my old Mac run Windows and then learn how to use a Windows system that I don’t want

This may work to let you run Windows applications on your Mac. I have used it on Linux so in theory just need to install it. No windows license required.

[https://www.winehq.org/](https://www.winehq.org/)

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [April 7, 2025, 8:34pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/103 "2025-04-07T20:34:17Z")

</div>

> [@thorny\_locust](#):
>
> How do I get that thread visible again?

Goto to sidebar and select “My Posts”

I think this might be the topic/post you’re looking for.

> [@Dropping iOS 15 & other old browsers in July 2025](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-may-2025/358131/79):
>
> Discourse isn’t supporting the most updated Firefox ESR. I just updated that on an old Mac Mini; it updates to 115.22.0esr and I’m still seeing the message that I’ll be effectively thrown off the boards – I don’t want to just read in the Straight Dope community, I want to be able to post there. I can’t afford a new computer. Please don’t bother telling me that a new Mac Mini is “only” $599 – I’m scraping to buy groceries. Is it? How many people currently using message boards are upset about…

---

<div class="post-metadata">

### Author: ![thorny\_locust](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@thorny\_locust](https://meta.discourse.org/u/thorny_locust)
#### Post date: [April 7, 2025, 11:19pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/104 "2025-04-07T23:19:36Z")

</div>

> [@Heliosurge](#):
>
> > [@thorny\_locust](#):
> >
> > How do I get that thread visible again?
> 
> Goto to sidebar and select “My Posts”

Actually the problem was that I had turned off some javascript that needs to be enabled to use this site.

It would have been much more useful for Discourse to tell me to turn on Java than to give me a message that appeared to have nothing at all to do with the actual problem.

---

<div class="post-metadata">

### Author: ![thorny\_locust](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@thorny\_locust](https://meta.discourse.org/u/thorny_locust)
#### Post date: [April 7, 2025, 11:30pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/105 "2025-04-07T23:30:32Z")

</div>

> [@Heliosurge](#):
>
> This may work to let you run Windows applications on your Mac. I have used it on Linux so in theory just need to install it. No windows license required.

You’re saying it might let me run an updated Windows browser? All the test reports I can find on the site for this os appear to be for games.

---

<div class="post-metadata">

### Author: ![Heliosurge](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heliosurge/32/571810_2.png) [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [April 7, 2025, 11:33pm UTC](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131/106 "2025-04-07T23:33:52Z")

</div>

Using the search on the link I provided with Fire fox

[https://www.winehq.org/search?q=Firefox](https://www.winehq.org/search?q=Firefox)

[Previous page](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131.md?page=4)

[Next page](https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-july-2025/358131.md?page=6)
