Jump to content
Not connected, Your IP: 216.73.216.139

Leaderboard


Popular Content

Showing content with the highest reputation on 08/14/19 in Posts

  1. 2 points
    schwabe explained what was required to get the code merged upstream, you decided to close the PR as can be seen here. This would be the same if you were submitting a patch to the kernel, subsystem maintainers have requirements and they themselves have requirements to get it merged in the next release branch by Linus or Greg for stable. So as it turns out, he told you what needs be done and you refused. Whether his requirements are suitable is not for discussion since it's not your project. You may have requirements for PR's on Eddie branches as most OSS does. You need to comply or you can just maintain your own fork which is worse for the community as a whole. To be clear, you may see this as "see, this guy is stopping us!" but instead it's "hey, we didn't comply with the requirements of this software to get our PR merged".
  2. 1 point
    Clodo

    Has Air given up on Eddie for desktop?

    Hi, I'm sorry about the delay on Eddie development, but in the next release we changed all source code from the ground up, to separate what needs elevated privileges and what not. So we are re-testing all Eddie features. For example, in the next release UI runs as normal user, and this can fix or cause worse issues in different Linux distributions. Re-testing all major distributions requires a lot of time. Anyway, I hope to release it (as a beta version for feedback) when all supported OS (Win/macOS/Linux) are ready for use. This is related to the next release of 2.X branch (the same UI you know). In the meantime, we are building also the new universal UI for 3.X branch. I hope we can release the new 2.x version as soon as possible. I hope I can give you a date in a few days. Sorry again for the delay.
  3. 1 point
    This has been driving me nuts ever since I updated to the latest version of Eddie. However this has worked for me (so far).. Open Eddie Main Window Select Preferences Select Networking Against Layer IPv4 select Inside tunnel (must be supported) Untick Switch to ‘block’ if issue is detected Against Layer Ipv6i select Block Untick Switch to ‘block’ if issue is detected Against Internet Protocol used for connection select IPv4, IPv6 Against Interface used for connection select Automatic It seems to be a problem of IPv4/ IPv6 settings so try experimenting with different ones if the above doesn’t work for you.
×
×
  • Create New...