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 and updating whenever there is security issue. However this has the unintended side effect of loc…

I think the productive and helpful thing to do here is not so much to worry about what mega-corporations could do or should do, because we can’t affect that, but to look at what can be done. How about these questions instead… what can a person do, if they happen to own an older device and need to…

I brought this up recently for iOS12 (original iPad Air in my case) in another thread. The problem for that generation of WebKit is that Discourse added a requirement for some JavsScript functions that are not present in old WebKit. The check that Discourse makes is not a simple version number comp…

One possible workaround that was suggested in another discussion about this is to help users who are unable to access the forum directly interact more via email. That could be helping them set various categories to “watching” or enabling mailing list mode.

For the record, iPads going back to late 2015 are still receiving the latest iPadOS updates. [이미지] As for the WebKit restriction, Google and Mozilla seem to believe that it’ll be lifted in the near future. https://9to5mac.com/2022/12/13/apple-mulls-opening-browser-engine-nfc-and-more-to-third-pa…

Tactically, you might have a good answer here: by what means can people with old devices run new enough software to keep using Discourse. It would be quite involved if one had a distributed community each of whom needed individual assistance. Strategically, it would take effort, discipline, and te…

[이미지] RZASF: Discourse possibly have a simpler version of the UI (and not read-only)), the original issue could be solved. I don’t think people have a full understanding of the scope of “simpler” here given the richness of Discourse. Login via Email Login via Google/Twitter etc Login via Di…

[이미지] Sam Saffron: building a new “shadow” Discourse read-write solution for IE6 and Lynx it technically feasible Well, that is quite extreme example. I’m guessing the focus is for example on iPhone6 instead Lynx. Perhaps iPhone 6 is a big risk. And after a year or so my 7 starts to be risk.…

[이미지] Jakke Flemming: But it is not matter of IE6 or Lynx, that is a fact :wink: Actually, as someone who supports some people with accessibility issues that use Lynx as their daily browse I can assure you that it matters. That said, having had to write a custom interface to Discourse that w…

To me there are 2 very distinct arguments here. iOS 12 is still getting security releases from Apple. Can CDCK support it? [image] What about ancient browsers that are no longer getting any security fixes. With (1) I am much more sympathetic, however Apple are not making it easy for us. We do…

It’s ok to admit that Discourse can’t be all things to all people. I’ve led projects which have taken technology closer to the leading edge than they maybe should. In hindsight, some of the components selected weren’t in the best interest of the users they served. User demographics and their clien…

구형 브라우저와의 역방향 호환성

제품 지원

Stephen (Stephen) 2월 28, 2023, 2:13오후 71

아, CR-48이군요. 좋은 기억이 납니다. 하드웨어가 너무 약했던 것이 아쉬울 뿐, 당시 기준으로 보면 케이스는 꽤 훌륭했거든요.

지금은 13년 된 기종이죠

Why does Discourse prevent users to login with Safari 14.8?

글		댓글	조회수
Why does Discourse prevent users to login with Safari 14.8? General	35	3062	7월 11, 2023
Dropping iOS 15 & other old browsers in July 2025 Announcements	143	65134	8월 21, 2025
Discourse not working on an old phone with an unsupported browser Product Support	14	2423	2월 7, 2020
Maintaining support for iOS 12 - 14 until January 2023 Announcements	22	22286	1월 16, 2023
Discourse forum owners: Are you interested in native mobile apps? Marketplace	39	7391	9월 8, 2019

구형 브라우저와의 역방향 호환성

Related topics