Appreciate the heads up. Looks like they use merge bots to auto update the package version JSON files for git packages, making for a very large/frequent commit history. Was that what made bisecting imposable?
I also see they pin the nixpkgs input, but do others normally modify that nixpkgs input to follow their global nixpkgs from their own system flake, or does that invalidate the use of Nyx community cache?
Mainly the official git CLI for controlling branches and sub modules, and sometimes the GitHub CLI if quickly checking out a pull request from a forked repo.
Also use the source control tab in VSCode rather often, as it's really convenient to review and stage individual line changes from its diff view, and writing commit messages with a spell check extension.
If it's a big diff or merge conflict, I'll break out the big guns like Meld, which has better visualizations for comparing file trees and directories.
About a decade ago, I used to use SmartGit, then tried GitKraken when that came around, but never really use much of the bells and whistles and wasn't keen on subscription pricing. Especially as the UX for GitHub and other code hosting platforms online have matured.
What about a semi transparent terminal window? When I started out learning linux command line interfaces, it helped having the docs just behind my shell session for reference when all I had was a tiny old laptop. But now I don't bother ricing up my DE anymore. I just want some default window tilling keybindings that work out of the box, and I'm good to go.
Is there a GitHub ticket to track this issue?
The current Lemmy workaround sounds non-optimal.
What is your local system clock; 16 seconds behind your NTP server? That, or OP just has a similarly inverted clock skew.
I guess OP could be posting from the future. Hey @akrz@programming.dev , what is the closing price of SMP 500 tomorrow? :P
The video player in Lemmy-UI really needs the loop feature in the playback settings. At least I'm not seeing the option via Chrome or Firefox for Android.
If meta connects with Lemmy, that’s an influx of a potential 3.74 billion people…
That sounds like it could be really hard for us to moderate. All those users would be coming from the same domain(s), so we'd have fewer options to protect ourselves from brigading, bots, and bad actors. Our moderation tooling and FOSS infrastructure is still in it's infancy.
I fear it would quickly grow into something "to big to ~fail~ban", as too much of our community's users would inevitably be centralised on Facebook's instance. Our instance, and users not Facebook, could lose a lot of autonomy if they couldn't partake here without realisticly opening their floodgates to every actor behind Thread's domains.
FYI, others commenting on hosting Lemmy in an AskLemmy thread:
For posterity, I later stumbled upon the authors original post here:
The community that this was posted from also looks interesting:
Do you have any links or references to learn more? Perhaps any github tickets to follow? By bootstrap, are you referring to this?
But that seems like a small minority - the software world is fickle and the number of projects that last that long is small.
Indeed, although imagine the projects that do: a granddaughter resurrecting your repo and bringing a feature to completion well after your passing, such as porting it to use modern materials/libraries:
Where they have to dig through archived web forms and tutorials to find the manual/documentation that you would have used to put the project initially together. I'm sure there'll be some content creators in the future telling the same stories as the one above, but via a newer medium and with a Computer Science twist.
I'm in search for the same white whale. There's quite a bit of documentation for multi-seat configurations for Linux, i.e. supporting the use of multiple screens and keyboards for separate simultaneous logins.
However I'd like to remote into a separate game scope session with its own human interface inputs and virtual audio and video outputs, as the same primary user normally logged in active desktop environment session. I'd like it so the remote and local sessions would not interfere with each other state, but without necessitating multiple Linux users for each session use case.
That last bit is what makes it more tricky and very niche. Supporting essentially multiple desktop environments probably demands separate user debus sockets. Using c groups via containers makes that viable, but like you, I also like to avoid containers and extensive volume mounts.