Lantern: Alternative Censorship Circumvention Tool
Lantern [archive] is a censorship circumvention tool which can provide an alternative to Tor bridges. The design is similar to a VPN and encrypts all of a user's data through their servers and then proxies blocked sites. Note that Lantern in isolation is not an anonymity tool because it is technically possible to spy on user activity under this model. Another downside is that bandwidth limits also exist for non-subscribers: 
Lantern is designed to provide you with fast unfettered access to information online. Lantern is secure and encrypts your connection to blocked sites, but it is not an anonymity tool, so if you need or would like to be anonymous online, please use Tor. Otherwise, Lantern will give you faster access to blocked sites. ... To keep our free version running, we implemented a bandwidth limitation of 500 MB/ month. When the bandwidth limit is reached, the connection is slowed down and Free users are prompted to upgrade to Lantern Pro.
After bandwidth limits are reached the connection slows down to approximately 20KB/s, making Lantern virtually unusable. In order to remove this restriction, users must pay for the 'Lantern Pro' service.  The available options mean any payment is likely traceable, but this is not necessarily any more 'damaging' to privacy and/or anonymity than connecting to Lantern in the first place.  Interested readers can learn more at the Lantern forums [archive] and developers Q&A [archive].
- There is limited documentation available describing how Lantern functions. Although it states it unblocks websites, this mechanism is undocumented. Further, the developer FAQ is empty.
- Lantern developers state they are based in Los Angeles, but their GitHub repositories, Twitter accounts and the Terms of Service have a lot of Chinese text.
- The primary GitHub repository has numerous stars and forks (even though it seems to be a small project) from what appears to be bot accounts, as many have no activity. The GitHub account also has hundreds of repositories that are completely irrelevant to Lantern.
- Links are provided to a forum which does not even exist.
The Wikipedia Lantern entry also notes: 
- User information can be shared with various third parties, including advertisers.
- Content blockers like uBlock Origin are ineffective in preventing data collection because Lantern operates at the TCP/IP stack layer.
- Personally identifiable information may be subject to disclosure to governments in the country of operation.
In summary, Lantern is not recommended unless the user has limited other options for censorship circumvention.
Connecting to Lantern before Tor
It is possible to configure Tor to use Lantern as a proxy to establish the following tunnel:
Before applying the following instructions, it is recommended to first read:
- The warning section above.
- Combining Tunnels with Tor.
- Current limitations discussed in this blog post / forum discussion [archive].
- https://getlantern.org/en_US/faq.html [archive]
- In early-2019, this costs $32 (USD) for one year, or $48 (USD) for two years.
- This is because advanced adversaries can discover that a user connected to Lantern (via logs), and pluggable transports are incapable of successfully hiding Tor use in all cases. Therefore, a payment trail simply acts as another confirmation mechanism and is not necessarily 'worse' under the circumstances.
- https://en.wikipedia.org/wiki/Lantern_%28software%29#Privacy_Policy [archive]
- Non-Qubes-Whonix ™ is unsupported at present.
- Lack of a dependency declaration when installing Lantern on Debian [archive] - broken link.
- Proper Debian deb package: https://github.com/getlantern/lantern/issues/4837 [archive]
- Debian APT repository with Lantern: https://github.com/getlantern/lantern/issues/4837 [archive]
- Add Lantern to official Debian repositories: https://github.com/getlantern/lantern/issues/4837 [archive]
- Debian Lantern RFP (request for packaging) [archive]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828932 [archive]
- SOCKS is considered to be better. According to this issue [archive], Lantern already has SOCKS support. Open issues: https://github.com/getlantern/lantern/issues/4838 [archive]
- Setup should now be easier (less need for IP changes) because Qubes has implemented optional static IP addresses [archive].