• 0 Posts
  • 37 Comments
Joined 4 years ago
cake
Cake day: June 23rd, 2020

help-circle
  • GitHub (since the Microsoft acquisition) is good to users because that’s their MO, it’s called Embrace, Extend, Extinguish, and the whole point is to centralize users and projects and make them dependent on the Microsoft ecosystem.

    Of course now there’s also the whole issue of Copilot, which means any code you put on GitHub could very well show up piecemeal in someone’s AI-generated code. If it wasn’t for that novel avenue of monetization, you can bet your ass GitHub would have already made the free user experience a lot shittier.


  • Sorry, if you remove my ability to interact with posts through the all feed, I will stop using this site. With how little content exists on this platform, there’s little point in curating a feed. You either visit a specific community for specific information, or you browse all. It would just be an annoyance anyway, akin to the awful reddit “no-participation link”. These measures do absolutely nothing to stop bad faith actors and only serve to annoy normal users and push them away from the site.











  • river is a tiling window manager for Wayland. Most of the big tiling wms are for X, and to my knowledge not many are planning Wayland versions. It makes sense, as for a tiling wm you’d just be rewriting most of the code. So instead you get these roughly parallel projects that start at attempts to basically port wms to Wayland: Sway for i3, river for bspwm, and dwl for dwm.

    Sway is by far the most popular, but river and dwl are both functional alternatives, even if the feature sets are a little barebones. Personally I’m waiting for a Wayland version of herbstluftwm, it’s my favorite.




  • From the comment thread it sounds like the contract might be on shaky ground. The original dev seems to be under the impression that a project licensed under GPLv3 can just be freely changed to another license, which it cannot without explicit consent from all contributors. We don’t know the contract language of course, but the dev said it would “likely” not remain open source, which indicates that he told them they could change it. ZippApps’ lawyers will hopefully notice that and refuse to buy, though either way we shouldn’t trust this maintainer again and should move to the forks.






  • It’s literally not. I’ve seen multiple performance-impacting bugs that people mention, which is a bummer for those users… But none of them happen to me (Pixel 5, android 13) or plenty of other users. Insisting that FF is just hopelessly broken on Android is simply untrue.