![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Hardening aside, I like that LibreWolf actually lets you turn on JPEG XL.
he/him
Hardening aside, I like that LibreWolf actually lets you turn on JPEG XL.
Sorry for clarity. The eventual consistency model is a result of wanting decentralization for Slack/Telegram/Discord’s design of thinking the entire history needs to be saved for chat rather than seen as ephemeral (which allows for better search & resilience, but at a major cost to storage, but also a knock-on effect of folks treating chat as permanent which is why we have huge, cut-off information silos on these chat platforms that the rest of the net can’t index & often trawling the search is difficult so the repeated questions/answers are common since a simple web search doesn’t yield good results). When you take away the concept that all text & attachments need to be seen from origin til the end of time, you would never bother in all the work of cloning the entire history & reassembling it on every server listening to the conversation. …Which is why many chat protocols forgo the more then enough history to keep you up to speed with a conversation & structured forums + feeds used to be the primary way to ask questions & make announcements (where simple programs could parse the data instead of needing gobs of natural language processing for chat soup when it is pulling multiple duties).
All the Matrix clients are buggy using far too many resources & the protocol is slow as balls about joining new rooms while being wasteful about data duplication for throwaway bits of text/multimedia. I don’t think eventual consistency is the right model for chat & following Slack & Discord’s model is the way.
Gerrit is probably the poster child for branchless, stack-based diffs in Git. It takes some get getting used to, but once adjust your thruput is really ramps up. In some sense tho, this is a hack by tagging changelist values in the commit message to help reconstruct what the heck is going on due to Git limitations, but it’s old & robust enough to trust that system & many of its users absolutely swear by it (I have limited exposure but have used it more recently I can feel the appeal). You should be able to slap it in front of any Git server—even just straight host HTTP if not something lightweight like cgit, gitweb, or Ayllu. (Jujutsu is the same commit hackery in a different package & I don’t think it moves the needle as much as folks think being ultimately shackled to Git’s design decisions).
If you look outside of snapshot-based tools like Git, Mercurial, & so on, patch-theory-based options offer refuge. Darcs & Pijul are the leading (D)VCSs in the space. Darcs is very mature & shows its age in many ways (but is still developed & works good enough). Pijul is largely based on Darcs but meant be faster (& is), but it is immature; some features are missing on purpose to avoid the swell of Git commands, but I am personally surprised theres no good story for sending patches nor rebase. That said its identity system is how VCS should do it. Both VCSs have a lot less tooling built around them. Darcs is still supported by tools like Nix (but not Flakes) as well as Opam for OCaml with darcs hub & Smederee for maintained public forges. Pijul isn’t supported by much at all unfortunately & while Nest is a public forge, its lacking in features & basic usability like being able to fetch a tarball (despite pijul archive
). All the latter negativity may sound bad, but all tooling requires momentum. They would be prime candidates for the Gerrit workflow–just without the hacks needed. With the two being similar, I hope we see more tooling pop up to support them & just like trying a new paradigm of programming gives you insight on the ones you know, a new way to do VCS will teach you about version control. Do recommend.
If ForgeFed gets up & running you should be able to self-host your own compatible VCS repository & send pull/merge requests from it instead of needing to create an account then for & use up space on another’s forge. The Forgejo lineage has a strong interest in this technology. Currently the only decentralized+popular way to send patches is via email so this will help put the D back in distributed version control system (DVCS). This would not only be great for users getting to keep their private data, but the distributed nature adds a layer of resilience for downed Microsoft servers (happens often) or censorship/sancations as with even a little momentum, your project will have mirrors in multiple jurisdictions.
GitLab is open core, which is a step up from fully-closed, but isn’t fully open (nothing inherently wrong with that, but it is of note). The bigger issues with GitLab to me are twofold: 1) it’s slow built on Ruby & React (I think) where it can’t run on a potato requiring both excessive CPU as well as data usage while also requiring JavaScript & 2) GitLab is publicly traded which means there are shareholder requirements for them that can easily get in the way of what is good for users (or even what will be or continue to be licensed with a free software license).
Codeberg is ran by a German nonprofit which means they aren’t trying to put profits in the way of users, but also being in the EU, they will have strict requirements for user data which means it’s safer. As far as I can tell, there are no ads & it runs fast & works well enough without JavaScript. I would rather see more self-hosting personally, but if it isn’t practical for you, this is a good option. With it being built with Forgejo, it should in theory introduce a lot less friction migrating from Codeberg to self-hosted Forgejo in the future.
Forgejo isn’t without flaws tho. One of the goals of Gitea (forked from Gogs) vs. Forgejo (forked from Gitea) is trying to be more compatible with Microsoft GitHub even moving its continuous integration (CI) to Forgejo Action to be compatible with all the bugs & YAML spaghetti that MS GitHub uses. They copy the generally-bad pull request model too which only is optimal in certain uses cases, bottlenecking review & having a UI that leads maintainers more to commenting on how to fix something rather than saying “thanks”, merging, then fixing small nits themselves to not waste the contributor’s time in review if they just want a small bugfix, not to learn your entire codebase + style + process. By copying MS GitHub too closely, you can up being a clone that is just FOSS while risking having something that is technically differentiating which is ironically counter to inspiriting migration since while it might be easier, the benefits seem moot (maybe even just philosophical) instead of providing something users want to leave for (which is what I think you might be getting at). Additionally being Git-based as well means Forgejo (& others) are stuck with snapshots that factor in time & patch order causing unnecessary merge conflicts with multiple users which is solved by choosing a better version control system (VCS).
Using free software to create free software is already a good reason.
But if you need more:
youtube-dl
, etc.)Disappointed as I was hoping for some Richard Stallchan x Linus Torvaldsan fanfic
Have you seen new gamers try to navigate 3D spaces? 2D is much more accessible to a lot of folks.
I’m just hoping wlroots can copy these any day now. Color management (& DisplayLink) are my 2 Wayland blockers.
Fish for interactive shell. “It depends” for scripting, but usually ends up Bash since it is the NixOS default.
Felt. VR took priority over color management with ICC profiles & HDR which is more important for commercial & general entertainment applications. I’ve had to switch back to X11 too.
It’s great to see this project still chugging along. I tried it on an old phone & it worked, but it would run into readonly filesystem errors after a few hours of usage. I never got to figure out why since I ended up actually needing to use the phone while mine had broken so it’s LineageOS for microG now.
He pointed out a bunch of JavaScript plugins don’t work in WINE but I’m not following what it does that Picard + ffmpeg + many other audio players can’t do. It seems worth losing a feature or two or having to adopt a small composition of tools …or building it yourself / paying a bounty for a feature.
He’s the perfect size—they shouldn’t make YouTubers bigger than that
The hardware is good & you can get phones under 6".
They have 2 big flaws: price & years of continued support. The catch 22 is you can get a good price on them after the support window (2 years, but looks like 5 will be going forward). Luckily LineageOS always picks up after the support window if willing to take on possible firmware vulnerabilities knowing software will continue to be updated—but the camera requires the proprietary apps/libs or it looks low-end.
Not in my ideal spot but tolerating Android via LineageOS for microG on a Sony Xperia 5 III as their ROMs make microG painless & hardware-wise I get a fast-enough CPU, OLED, a headphone jack, & microSD.
The appeal would be with a limited albeit large set of characters, items, & rules, you can have effectively an infinite set of outcomes due to the dice rolls of teammates but also champions/heroes chosen on team. It is almost impossible to see the same game twice unlike. There is skill expression & build mechanics that allow a player to outplay or recover matchups & adjust to the state of the game on the fly. With every game starting over at zero, you don’t get invested in building a specific character, but in mastering the gameplay which can go from micro mechanics to macro. I think a lot of folks liked it coincidentally at a time with better broadband for communications for this style of game, developers doing frequent patches to force meta shakeups & e-sports + streaming also taking off. But also a sunk cost fallacy of having invested the time to git gud not bothering to learn any game too similar.
I just had a nice cup of Thai white tea, which induced the opposite of rage 🍵
IIRC it might be on by default (tho this would hurt anonymity if you can request JXL files & stock Fx cannot), else open
about:config
& search for “jxl”. Upstream has kept this flag—toggle on or off—only working in Fx Nightly.