localtunnel VS TinyMCE

Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:

OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...

Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...

ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...

I'll see that OG localtunnel gets added to the list for posterity.

[0]: https://github.com/anderspitman/awesome-tunneling

[1]: https://github.com/localtunnel/localtunnel

These is a very common problem. Luckily, it's been solved already. My go-to tool for this was ngrok or localtunnel. Both of these tools are great, but they didn't fit my needs perfectly.

localtunnel — Expose locally running servers over a tunnel to a public URL. Free hosted version, and open source.

Localtunnel used to be a nice tunnel. It has gone through some enshittification lately.

> tunnel consent page now requires the tunnel creator's public IP in order to access tunnel content

https://github.com/localtunnel/localtunnel/issues/598

There are free non kafkaesque competitors out there.

I recently went through having to tunnel my development environment to setup an oauth2 flow for a rails integration. I found that using https://github.com/localtunnel/localtunnel was a better fit.

I prefer localtunnel: https://github.com/localtunnel/localtunnel

There's also Local Tunnel (http://localtunnel.me)

Not sure if it works combined with ngrok: https://www.npmjs.com/package/localtunnel

TinyMCE provided a bit more information about this change in a GitHub discussion thread here: https://github.com/tinymce/tinymce/discussions/9496

As I posted there, this directly affects my open source project which is heavily tied to TinyMCE so I may end up forking, and reducing down to what my project needs to reduce maintenance scope & burden.

TinyMCE have been jumping around with their licensing. They were under LGPL, with some (what I believe were) misleading guidance into meeting the LGPL (they specified rules about keeping specific branding elements). They then jumped to MIT, and since moved some of the open plugins to their commercial offering. Now they're making this change.

TinyMCE 7 includes fixes for 17 bug fixes reported by the community. See the changelog for details.

TinyMCE - rich text editing API. Core features are free for unlimited usage.

Website

Any idea how i could replace the current classic editor with the newest tinymce wyswig editor: https://www.tiny.cloud/ it looks so modern and clean and i would love to use it but the default wordpress classic editor is so old and is some really old version of tinymce and I'm unsure of how to change it, any plugins or scripts to do this?

Any idea how i could disable the default crappy wordpres ugtenbergs block and instead replace it with the newest tinymce wyswig editor: https://www.tiny.cloud/ it looks so modern and clean and i would love to use it but the default wordpress classic editor is so old and honestly makes me sick, any plugins or scripts to do this?

Luckily, implementing a basic text editor in your React application is a fairly straightforward process. In this article I will show you how to implement a rich text editor using TinyMCE.

Check https://www.tiny.cloud/

I'm using TinyMCE as the rich text editor, you can replace it with something else, or simply use a if you wish.