Talk:Replicant (operating system)
This is the talk page for discussing improvements to the Replicant (operating system) article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: Index, 1Auto-archiving period: 90 days |
This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
|
The following Wikipedia contributors may be personally or professionally connected to the subject of this article. Relevant policies and guidelines may include conflict of interest, autobiography, and neutral point of view.
|
Index
|
|
This page has archives. Sections older than 90 days may be automatically archived by ClueBot III when more than 5 sections are present. |
Stagefright security flaw
editPlease add info about potential use of Replicant to protect from the Stagefright Security Flaw.-96.233.20.34 (talk) 21:59, 27 July 2015 (UTC)
- Wikipedia is not a collection of unverifiable speculation. See WP:SPECULATION. --Dodi 8238 (talk) 22:22, 27 July 2015 (UTC)
- By all means, indeed -- let us gather the best real information about Stagefright! Which WP articles are most relevant?-96.233.20.34 (talk) 14:11, 28 July 2015 (UTC)
- There is already an article about it: Stagefright (bug). That wasn't my point. Please take a moment to familiarize yourself with these two Wikipedia policies: WP:Verifiability and WP:SPECULATION. If you can't find a reliable source (preferably independent of Replicant) that says that Replicant can be "used to protect from the Stagefright Security Flaw", even "potentially", then we can't make that claim in this article. --Dodi 8238 (talk) 14:42, 28 July 2015 (UTC) [edited 16:15, 28 July 2015 (UTC)]
- Hello! There are currently no indications that Replicant has already included patches against the Stagefright bug. Please see this ticket for further information. — Dsimic (talk | contribs) 16:31, 28 July 2015 (UTC)
- Thank you for the new Stagefright WP article, which did not exist when I started this Talk topic. I hope that article gets further fleshed out over the coming days -- almost a billion users are affected! And thanks extremely much Dsimic for this very helpful link to the Bug #1287 Stagefright vulnerability Replicant ticket!!! If Replicant does protect from Stagefright, it becomes much more important than formerly, since many stock Android users have no current good options, and may never. If it is determined that Replicant does not protect from Stagefright and is unlikely to in future, that would be good information to mention in the article.-96.233.20.34 (talk) 17:30, 30 July 2015 (UTC)
- You're welcome. :) Let's hope that the Stagefright bug will increase the overall awareness of the lack of a proper update system for numerous Android devices. It's somewhat like plane crashes, which unfortunately must happen for certain aircraft design changes to be made. — Dsimic (talk | contribs) 19:23, 30 July 2015 (UTC)
Ambiguity
edit'many members of the original Replicant team retired from the project', that line raises some concerns re. the health of these members...Noiv (talk) 19:45, 23 December 2015 (UTC)
- Most of them probably got busy with other things.
- As for Paul Kocialkowski he got more interested in contributing to upstream projects as the quality of the low level Android code and architecture lags strongly behind GNU/Linux GNUtoo(my point of views(for npov)) | talk 16:47, 12 November 2019 (UTC)
POSIX?
editIs Replicant POSIX-compliant? — Preceding unsigned comment added by 75.139.254.117 (talk) 18:14, 18 November 2016 (UTC)
- Probably not. It's also an Android distribution. GNUtoo(my point of views(for npov)) | talk 16:44, 12 November 2019 (UTC)
Replicant 6.0 released
editReplicant 6.0 was released May 13. https://blog.replicant.us/2017/05/replicant-6-0-released/ — Preceding unsigned comment added by Allen Me (talk • contribs) 21:21, 11 June 2017 (UTC)
Name origin
editHi,
The name of the project was also named Replicant because this time we could easily Replicate what was effectively for end users a nonfree operating system with minimal efforts. Practically speaking the user interface and most of the system would be the same as the nonfree one it but would be free software.
The name was chosen while discussing about it on IRC. I remember that the idea of using 'Replicant' as a name came from Bradley_M._Kuhn. I don't remember exactly who was present in that discussion though. GNUtoo(my point of views(for npov)) | talk 22:50, 7 November 2019 (UTC)
- Hey GNUtoo, I spent some minutes searching for a source to reference for the "replicant replicate" connection, but didn't find anything. If you could point to even a self-published, primary source, I'd be happy to add some words to the Article. Unfortunately, it seems Wikipedia values sourcing higher than "truth," and I'm trying to follow the rulez... -- Yae4 (talk) 04:06, 8 November 2019 (UTC)
- I'll look in my old backups and around if someone has the logs. Else I'll publish it on the Replicant website in the FAQ. GNUtoo(my point of views(for npov)) | talk 16:48, 12 November 2019 (UTC)