• 0 Posts
  • 32 Comments
Joined 1 year 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.



  • I’m very torn on disco. Season 2 is probably the best (due in no small part that it sets up SNW), but the rest are a chore to watch. Most of them have some neat ideas, but they’re badly executed more often than not. They also were too heavy handed with each season arcs serialization, most episodes don’t stand on their own, and the writing and consistency is just bad. I just finished the final season, and I’m glad they’re done with it so they can put more money on good Trek like SNW - hopefully they don’t screw it up eventually.






  • 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.





  • Actually, we just entered spring, on late September. And we did so in the midst of a heatwave that broke heat records for this year - we had days with 37C, which is high even for summer, and it won’t be summer here until December.

    Yes, I’m scared af as well. My family is sort of ignoring my warnings and actually planning to move to the coast (Santos), which is even hotter.

    Some guys here in the comments said about migrating to the north, and that’s something that has been on my mind as well as a long term plan, although I find it unlikely I can move to North America in the short term, so I’m thinking more realistically maybe southern Argentina?



  • Just FYI, Barrier has been abandoned / unsupported for awhile. Although the last release mostly works, don’t expect future support.

    Its successor is https://github.com/input-leap/input-leap, and although there have been some coy maintainance on it, they have yet to provide an installable release, due to “reasons”.

    I use Synergy myself, which is the ancestor of both of the above. Although it started as open source, it has been turned into a commercial product a long time ago, which is why I’m not providing the link here. It’s still maintained, for better or for worse, but in the latest release-to-be they revamped the UI and for some reason I couldn’t get it to work at all on my setup - it seems to rely on some auto configuration / autodetection gimmickry which simply is not working here. To make matters worse, the new UI is essentially an electron app, which means it has become a lot more bloated. And then there’s also the telemetry thing. I’ve been using the old 1.1 legacy version, holding out hope that input-leap eventually lifts off.





  • fernandofig@reddthat.comtoAsklemmy@lemmy.mlWhy Mastodon?
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Yeah, but then we’re not talking about social media anymore, but brand and company names in general.

    When you want a brand name to be part of people’s everyday vocabulary, as is the case with social media, it needs to be succint and easily referred to. Hell, sometimes people even turn those names into verbs (tweeeting, facebooking, etc.), how do you do that with Mastodon without compounding the problem? (E: I know about “toots”, but now that’s coming up with unintuitive jargon for the platform - which is fine, but shouldn’t have been necessary in the first place if more thought had been put into the brand)