I only played the first one, because the second one was more finnicky and required newer hardware. But I must say, NOLF 1 is one of the best and most unique FPS games ever. It should be far, far more famous than it is.
The major shortcoming of NextCloud, in my opinion, is that that it's not able to do sync over LAN. Imagine wanting to synchronize 1TB+ of data and not being able to do so over a 1 Gbps+ local connection, when another local device has all the necessary data. There is some workaround involving "split DNS", but I haven't gotten around to it. Other than that, I thought NC was absolutely fantastic.
If not, and you don't want to set up dnsmasq just for Nextcloud over LAN, then DNS-based adblock software like AdGuard Home would be a good option (as in, it would give you more benefit for the amount of time/effort required). With AdGuard, you just add a line under Filters -> DNS rewrites. PiHole can do this as well (it's been awhile since I've used it, but I believe there's a Local DNS settings page).
Otherwise, if you only have a small handful of devices, you could add an entry to /etc/hosts (or equivalent) on each device. Not pretty, but it works.
You could also upload directly to the filesystem and then run occ files:scan, or if the storage is mounted as external it just works.
Another method is to set your machines /etc/hosts (or equivalent) to the local IP of the instance (if the device is only on lan you can keep it, otherwise remove it after the large transfer).
Now your rounter should not send traffic to itself away, just loop it internally so it never has to go over your isps connection - so running over lan only helps if your switch is faster than your router..
I had a similar issue with a public game server that required connecting through the WAN even if clients were local on the LAN. I considered split DNS (resolving the name differently depending on the source) but it was complicated for my setup. Instead I found a one-line solution on my OpenBSD router:
pass in on $lan_if inet proto tcp to (egress) port 12345 rdr-to 192.168.1.10
It basically says "pass packets from the LAN interface towards the WAN (egress) on the game port and redirect the traffic to the local game server". The local client doesn't know anything happened, it just worked.
> The major shortcoming of NextCloud, in my opinion, is that that it's not able to do sync over LAN.
That’s an interesting way to describe a lack of configuration on your part.
Imagine me saying: "The major shortcoming of Google drive, in my opinion, is that that it's not able to sync files from my phone. There is some workaround involving an app called 'Google drive' that I have to install on my phone, but I haven't gotten around to it. Other than that, Google drive is absolutely fantastic.
I don't know why the sarcasm is so necessary. I very much enjoyed Nextcloud and I proudly ran it for the better part of a year. I even ran various NC-ecosystem apps, such as the Office ones. However, my objective was to try it out from the standpoint of regular self-hosting. I wanted to contrast the 'out-of-the-box' experience to Dropbox, which I had been using for many years up to that point. Yes, one was centrally hosted, while the other was self-hosted, but still, that was the experiment I was running. So I'm sorry if I didn't live up to your standards of what a user should be doing to their software, but I sure had lots of fun self-hosting tons of software at that time.
Not sure why you took it so personally, I was simply pointing out that if you don't configure a feature then that feature would obviously not work, for example phone sync for google drive won't work if you don't download the google drive app, and lan access for nextcloud won't work if you don't set up lan access.
I'm curious what you mean by this. I've never had trouble syncing files with the Nextcloud client, inside or outside of my LAN. I didn't do anything special to make it work internally. It's definitely not the fastest thing ever, but it works pretty seamlessly in my experience.
I have a very silly primary reason for preferring the Kitty terminal - I configured it to look very minimalistic and compact. It doesn't even have the customary app titlebar at the top. The other benefit is that it's actually a lot faster to start up than Terminal.app when you first invoke it. I know iTerm2 is really well-liked, but to me, it gave the "Breakin' 2: Electric Boogaloo" vibes.
- Terminal search and focus (you can list kitty tabs and windows and get the window content from the socket, implementing a BM25 based search is quite easy)
- Giving the current terminal content for AI, so I can do things like run `ls` and then write "Rename the files (in some way)", and push the whole thing to LLM that replaces the command line without me having to write the full context
I even have a Codex session finder that uses codex session files to list and select the session I want, and then uses the kitty socket to find and focus the window which matches the session content
I have thought of things to do with kitty remote but have always been lazy to actually write the code. Do you have it open source by any chance for me to steal?
The ones that I use the most are designed to reduce context switching, like:
Mutt, personal wiki (fzf searching and neovim editing) and todo (a long never ending markdown file), they all have dedicated shortcut (cmd+m/cmd+z/cmd+d) to open(switch to) their window. These applications, always reside in the first tab with stack layout. For example, I can press cmd+m to switch to mutt (or open it), and press cmd+m again to switch back to the previously focused window.
Depending on which repl is running, I can usually open up vim to edit the line with the same cmd+e shortcut, which sends C-X C-E in bash/zsh, ESC O in iex, C-O in aichat ... Also vertical split in tmux and kitty tab share the same shortcut, cmd+|.
Kitty does not have a command palette, and I use fzf to search some of my frequently used operations and make this my command palette.
I don't see the point of that, but I switched to Kitty from Terminal.app and it feel much snappier all around. Even faster than iTerm2 (which I liked, but not enough to ditch Terminal.app).
Kitty supports full 24-bit color and ligatures while being fast as hell and not weighing down your CPU like iterm will. Plus it supports plugins and is wonderfully customize able (visually, fonts, key binds for everything). I switched after couple years ago after realizing the Mac terminal looked like shit and iterm2 was a dog and never looked back. Have not noticed any bugs during daily use. It is my only Mac and Linux terminal.
Omarchy sounds very compelling (though I'm personally done with trying to run Linux on the desktop), but tiling window managers are just not very practical, for numerous reasons. DHH would be wise to also offer and optimize non-tiling WM setups.
Plasma isn't bad and better than Windows in most respects, but it's kind of the opposite of Omarchy in that it has a trillion toggles and its defaults don't work for many, so a good deal of tweaking is required to make it "cozy".
I'm curious which defaults you find so unusable. I'm rather fiddly and particular, but I haven't done much more to my KDE setup than disable mouse acceleration.
I agree, but that seems unlikely given his inclinations. While there's loads of options for distributions that ship with a traditional floating window manager/desktop environment, few have gone the extra mile in holistic design with e.g. unified configuration and eliminating hoop-jumping to the greatest extent possible.
> tiling window managers are just not very practical, for numerous reasons
What reasons? I've been using tilling window managers for years now, and I feel like it's 1995 whenever I need to deal with dragging and maximizing windows.
I agree with the gp. I like some aspects of tiling vms but gave up after a while.
The main pain points for me were
1) I often end up with two windows each taking a side of the screen leaving basically nothing of interest in the centre. So I end up jumping through some tetris-like hoops to make a window be centered.
2) If I close any window all the others move, often causing a repeat of problem 1
3) apps not supporting it properly causing weird graphical glitches
4) some apps should never be small windows, others never large.
Basically I ended up spending more time managing windows with a tiling vm than I ever did before, which eventually outweighed the benefits.
reply