HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wordpress-mobile
WordPress-Editor-iOS
JavaScript2016–2016
wordpress-mobile / WordPress-Editor-iOS · Archived

WordPress-Editor-iOS

⛔️ [DEPRECATED] A reusable iOS rich text editor component.

7Distinct people
7Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

⛔️ [DEPRECATED] A reusable iOS rich text editor component.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour7 dated mentions

Observed mentions: 2016-10-29 20:32:39 UTC to 2016-10-30 19:20:45 UTC.

0122016-10-29 20:00:00 UTC to 2016-10-29 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 29, 20:002016-10-29 21:00:00 UTC to 2016-10-29 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-29 22:00:00 UTC to 2016-10-29 23:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-10-29 23:00:00 UTC to 2016-10-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 00:00:00 UTC to 2016-10-30 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 01:00:00 UTC to 2016-10-30 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 02:00:00 UTC to 2016-10-30 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 03:00:00 UTC to 2016-10-30 04:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-10-30 04:00:00 UTC to 2016-10-30 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 05:00:00 UTC to 2016-10-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 06:00:00 UTC to 2016-10-30 07:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2016-10-30 07:00:00 UTC to 2016-10-30 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 30, 07:002016-10-30 08:00:00 UTC to 2016-10-30 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 09:00:00 UTC to 2016-10-30 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 10:00:00 UTC to 2016-10-30 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 11:00:00 UTC to 2016-10-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 12:00:00 UTC to 2016-10-30 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 13:00:00 UTC to 2016-10-30 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 14:00:00 UTC to 2016-10-30 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 15:00:00 UTC to 2016-10-30 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 16:00:00 UTC to 2016-10-30 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 17:00:00 UTC to 2016-10-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 18:00:00 UTC to 2016-10-30 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-30 19:00:00 UTC to 2016-10-30 20:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 30, 19:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 29, 20:002016-10-29 20:00:00 UTC2016-10-29 21:00:00 UTC101
Oct 29, 21:002016-10-29 21:00:00 UTC2016-10-29 22:00:00 UTC000
Oct 29, 22:002016-10-29 22:00:00 UTC2016-10-29 23:00:00 UTC202
Oct 29, 23:002016-10-29 23:00:00 UTC2016-10-30 00:00:00 UTC000
Oct 30, 00:002016-10-30 00:00:00 UTC2016-10-30 01:00:00 UTC000
Oct 30, 01:002016-10-30 01:00:00 UTC2016-10-30 02:00:00 UTC000
Oct 30, 02:002016-10-30 02:00:00 UTC2016-10-30 03:00:00 UTC000
Oct 30, 03:002016-10-30 03:00:00 UTC2016-10-30 04:00:00 UTC101
Oct 30, 04:002016-10-30 04:00:00 UTC2016-10-30 05:00:00 UTC000
Oct 30, 05:002016-10-30 05:00:00 UTC2016-10-30 06:00:00 UTC000
Oct 30, 06:002016-10-30 06:00:00 UTC2016-10-30 07:00:00 UTC202
Oct 30, 07:002016-10-30 07:00:00 UTC2016-10-30 08:00:00 UTC000
Oct 30, 08:002016-10-30 08:00:00 UTC2016-10-30 09:00:00 UTC000
Oct 30, 09:002016-10-30 09:00:00 UTC2016-10-30 10:00:00 UTC000
Oct 30, 10:002016-10-30 10:00:00 UTC2016-10-30 11:00:00 UTC000
Oct 30, 11:002016-10-30 11:00:00 UTC2016-10-30 12:00:00 UTC000
Oct 30, 12:002016-10-30 12:00:00 UTC2016-10-30 13:00:00 UTC000
Oct 30, 13:002016-10-30 13:00:00 UTC2016-10-30 14:00:00 UTC000
Oct 30, 14:002016-10-30 14:00:00 UTC2016-10-30 15:00:00 UTC000
Oct 30, 15:002016-10-30 15:00:00 UTC2016-10-30 16:00:00 UTC000
Oct 30, 16:002016-10-30 16:00:00 UTC2016-10-30 17:00:00 UTC000
Oct 30, 17:002016-10-30 17:00:00 UTC2016-10-30 18:00:00 UTC000
Oct 30, 18:002016-10-30 18:00:00 UTC2016-10-30 19:00:00 UTC000
Oct 30, 19:002016-10-30 19:00:00 UTC2016-10-30 20:00:00 UTC110

What Hacker News says

1 sources
I'm not someone who'd know enough to be able to discuss this in detail. But in the linked post, Kal Tol mentions "The WordPress GPL Rich Text component in question, is actually a wrapper around another Rich Text component named ZSSRichTextEditor which is licensed MIT. In retrospect it would have been easier to use it directly." So it appears that although Wordpress is using GPL, the component that Wordpress based their wrapper on is using a MIT license; so it would seem there is a flexibility in being able to use either the GPL or MIT license. What I'm basically seeing based on Kol's article is: 1. MIT created ZSSRichTextEditor, and distributed it using MIT license. (see: https://github.com/nnhubbard/ZSSRichTextEditor/blob/master/L...) 2. Wordpress then created a wrapper for ZSSRichTextEditor, and subsequently had it covered by GPL inst
Read the rest
ead of MIT. (see: https://github.com/wordpress-mobile/WordPress-Editor-iOS/blo...) 3. Kol then took that stuff, implemented React, and re-applied MIT license to it, which whether intentional or not, was what the original license was. That being said, it's all open source and in the public domain. There's no theft here if it's was freely distributed. Kol even took it one step further (as he should), and gave proper credit where due -- not only within the project, but on social media.
In I Found Myself Accused of Stealing Code from WordPress

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.