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 don't actually care about the drama per se at this point either. I mentioned it because, along with the fact that:
- development is not very open (in that only that one guy commits and releases stuff)
- release cadence is very erratic and often lags behind upstream chromium, which is a direct consequence of the previous point
- you mentioned about the guys absence - the first time was some time ago and he was inpatient in the hospital for (IIRC) alcohol abuse, and this absence actually coincided with the drama over the furry and the other stuff, so it took awhile for it to be addressed, which only added more fuel to the fire. The second was just this last couple of months were he was house sitting for his parents (mentioned on the release notes I linked before)
All of this paints a bleak outlook for the long term health of this project, IMO. Which is too bad , because I still think it's one of the better forks of chromium.
Doesn’t PS2 use a PowerPC architecture?
No, it uses a custom architecture around a custom CPU, the "Emotion Engine", a MIPS-based CPU. You must be thinking of the Wii or XBox360 that came after it.
Not the guy you're replying to, but I have been using Thorium for the past couple of weeks. It's pretty nice, kinda like what Edge was before going to shit for the past year or so. But being a Chromium browser, it eventually will be hit with the ManifestV2-no-more hammer. The maintainer said the best he'll be able to do is use some patches to keep ManifestV2 active through enterprise group policies, but it's expected google will eventually remove the ManifestV2 code entirely, at which point he said he's not going to be able to maintain a fork to keep ManifestV2 in.
I dislike Brave for some of its sketchyness in the past, and the other Chromium forks haven't made clear guidelines on what they're going to do when ManifestV3 is made the default, so I'm bracing because I think I'm going to be forced to go back to Firefox because of AdBlock shenanigans.
there's almost nobody with 3 legs
Hol up there, tell me about those people with 3 legs!
Be sure to hear the 2000's re-record. It's one of those rare cases where the re-record blows the original (IMHO, at least)
Same here. In fact, I bought my Legion (which btw I feel like it was a good choice on OPs part because I believe Lenovo's laptops tend to have better cooling engineering in general, for whatever laptop category, compared to other brands) to serve first as a work laptop, and then some gaming on the side, which I'm not too picky about because I don't really play on PC that often anyway. My reasoning for that is that the business laptops I had been looking before going with the Legion were frankly overpriced crap with limited expandability, shoddy components and build, and full of built-in bloatware pre-installed. I find that gaming laptops tend to have higher quality components and slightly better expandability, so it was a win all around.
While I personally do not think that all Chromium browsers (especially since there are projects like ungoogled-chromium) transmit your personal data, I can't verify this myself because the Chromium codebase is far too much of an undertaking for myself to review.
Don't you think that, with so many contributors and projects having eyes on it (arguably more so than on gecko), if there was foul play wouldn't anyone have sounded the alarm?
I heard the same - over a decade ago.
Not disagreeing with you, although that information might be outdated. But the fact that you don't see, e.g. , applications that use gecko to embed web content, speaks volumes. I get the feeling that their codebase is very monolithic.
I would really like to hear from a current or former contributor though.
Oh well, maybe it’s relevant for some of the new people joining.
Rest assured, it was :-)
If you haven’t joined the community, you should see this button to block it below where the Subscribe button is.
My ADD is on full swing because I've been on Lemmy for the past month and never noticed that button until you mentioned it (although in my defense, it seems sometimes that button shows up as plain text, not clickable - apparently another UI bug). I finally blocked some silly communities that tended to show up on the "All" listing.
after typing that last edit, I see that the original question was asked 9 months ago.
Probably something to do with that bug of very old posts showing up at random on the "Hot" sorting.
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](/c/communityname@instance.server)
, all in lowercase. So, for example, if you're looking for the "kreisvegs" community on feddit.de, type[!kreisvegs@feddit.de](/c/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.
- Change the search terms so the community is fully qualified / keyed as
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.
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.