• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle
  • Barrier has been abandoned quite awhile ago. Its successor is supposed to be InputLeap, and although their GitHub repo is very active, they have yet to make a release.

    I didn’t even know that Synergy provided a “community” version of their app until very recently. I’ve paid for a license many years ago, so I’ve been using their 1.1x versions, which for better or worse, are still maintained along with the 3.x branch (which I’ve tried using but could never make it work, which is for the best because the fact they pivoted their UI to electron-based also left a bad taste in my mouth).

    Edit: also, if I understand correctly, Synergy’s latest versions on the 1.x branch borrows a lot from InputLeap.



  • This. It’s not as simple to get it working as it is on non-free OS’s, but with rclone I can get on Linux pretty much the same functionality I get from (eg.) Google Drive on Windows, including have most of the drive with on-demand access (meaning files are not stored locally, but downloaded / uploaded as needed) with a few specific folders synced for offline use. Since it supports a lot of storage services, I suppose it shouldn’t be that different to set it up the same way with Proton Drive.





  • This sounds like dev sour grapes but what the company was asking them to do seems better from the customer pov and for cyber security I’m general.

    As a developer myself (though not on the level of these guys): sorry, but just, no.

    The key point is this:

    […] we did not issue CVEs for experimental features and instead would patch the relevant code and release it as part of a standard release.

    Emphasis mine. In software, features marked as “experimental” usually are not meant to be used in a production environment, and if they are, it’s in a “do it at your own risk” understanding. Software features in an experimental state are expected to be less tested and have bugs - it’s essentially a “beta” feature. It has a security bug? Though - you weren’t supposed to be using it in a security-sensitive environment in the first place, it sounds perfectly reasonable to me that it should be addressed in a normal release as opposed to an out-of-band one.

    We can argue if forking the project is or isn’t extreme, but the devs absolutely have good reason to be pissed. This is typical management making decisions without understanding technical nuances and - from what is being told by the devs - not talking it through before doing it.





  • Maybe I’m bitter, and I know a lot of people wouldn’t agree with this, but honestly? I think the non-corporate part of the Fediverse should just assume malice from the get go and preemptively defederate from whatever Meta put out. That way nothing’s changed - Meta would essentially have a private / proprietary / isolated network, as far as users are concerned (much like Facebook already is), and even if the Fediverse will see less growth in the short term because of that, there will be no confusion on where everybody stands.


  • I don’t know about Jerboa, but this happens on the web too, and it’s usually on more fringe / less popular communities. There’s a workaround that works for me, I mostly heard about it from someone else here on Lemmy. It’s not great user experience, but it works.

    • Go to the search function;
    • Type in the name of the community, hit enter;
    • Select “Commnities” on the search type dropdown (yes, you have to do it after submitting the search as per the previous steps, seems like another UI bug);
    • If after doing the above the community is not found, then here enters the magic sauce:
      • Change the search terms so the community is fully qualified / keyed as !communityname@instance.server, all in lowercase. So, for example, if you’re looking for the “kreisvegs” community on feddit.de, type !kreisvegs@feddit.de on the search field;
      • Submit. It still won’t be found. Give it a few seconds, change back the search terms to only the community name (without the instace and “!” at the start). Submit. It should now show up.

    You may have to repeat step 4 onwards a couple times, sometimes.

    My uneducated guess as to what’s happening: the federated communities listing is probably cached on the instance, and by default it’ll only look for communities cached on your instance. My guess is that federated communities only gets into the instance cache when members of the current instance have searched / subscribed to that community. Typing the fully qualified community name on the search field (which is the tip I got from someone else) apparently forces the search function to actually contact the external instance to look for the community, instead of looking in the cache, but that can take some time, hence why you should wait a few seconds on the 6th step. That guess could also explain the problem also happening on Jerboa, since the problem would be server-side.



  • I think what he’s getting at here is people asking him about building an alternative platform to Reddit - much like Lemmy, Kbin, Tildes, etc. are - as opposed to an app serving as the frontend for an existing alternative platform. I’ve seen poeple buzzing about that on some of those threads about Apollo on Reddit. Those people are so in denial, and there were so many of them, that I couldn’t conjure to effort to point how ridiculous that idea is. Some people did, and were quickly shut down with the usual complaints (fediverse is confusing / doesn’t work, etc.)