Arch celebrating plasma 6 dropping a week after NixOS
genie @ genie @lemmy.world Posts 1Comments 68Joined 2 yr. ago
Exactly this. In a fucked up way a rule like that would actually incentivise whistleblowers to become martyrs.
I'd agree with you in the context of standard (google) android.
One caveat that I'd like to highlight, though, is that for me GrapheneOS and F-Droid handily achieve the privacy and rich FOSS ecosystem parts. Useful terminal depends on your definition :) but for my use case Termux fills the void.
It doesn't feel like Linux (you can't even use Wifi and Ethernet at the same time for crying out loud) but for a relatively cheap low-power device, I like the flexibility.
It's far enough from being a foot gun that I can give a Pixel 5 with GrapheneOS and some F-Droid apps to my grandmother and know she'll have no problems. Balancing that with having enough extensibility to scratch the itch for 99% of tinkerers is a feat to appreciate in my view.
I see a lot of love for proxmox in this thread.
Word of warning from my experience, sometimes PfSense seems to get confused with virtual interfaces. It works flawlessly once it's up and running, but every time I reboot I have to assign interfaces. It will hang until I do so and will not completely come back online until I manually intervene.
Oh cool! I didn't realize pandoc was extensible enough to deal with this kind of conversion. I'll give it a look!
With the rise of these .md based personal knowledge database applications it would be amazing to see some conversion software.
I understand that each has their special sauce. Does anyone know what would be the most difficult part about building a tool like that to copy in Logseq data to SB for example?
As an avid NewPipe user I like that it's an approximately identical tool with more functionality!
It seems like a fork where (I wish) a plugin could (ideally) be in NewPipe. It may also be a nice nod to the original devs to change the default color scheme of the fork so nobody gets confused as to who forked from who.
Overall very cool work! I hope they continue to have success and make progress.
Right!! Just like anything there's a trade-off.
Glad you phrased the well-intentioned (and fair) critique in a kind way! I love it when there's good discourse around these topics
You make a great point. I really shouldn't contribute to the boogeyman-ification of port forwarding.
I certainly agree there is nothing inherently wrong or dangerous with port forwarding in and of itself. It's like saying a hammer is bad. Not true in the slightest! A newbie swinging it around like there's no tomorrow might smack their fingers a few times, but that's no fault of hammer :)
Port forwarding is a tool, and is great/necessary for many jobs. For my use case I love that Wireguard offers a great alternative that: completes my goal, forces the use of keys, and makes it easy to do so.
Couldn't agree more! Tailscale also lets you use Mullvad (up to 5 devices per Mullvad account, across all clients) as an exit node.
I'll assume you mean what I mean when I say I want to be safe with my self hosting -- that is, "safe" but also easily accessible enough that my friends/family don't balk the first time they try to log in or reset their password. There are all kinds of strategies you can use to protect your data, but I'll cover the few that I find to be reasonable.
- Port Forwarding -- as someone mentioned already, port forwarding raw internet traffic to a server is probably a bad idea based on the information given. Especially since it isn't strictly necessary.
- Consumer Grade Tunnel Services -- I'm sure there are others, but cloudflare tunnels can be a safer option of exposing a service to the public internet.
- Personal VPN (my pick) -- if your number of users is small, it may be easiest to set up a private VPN. This has the added benefit of making things like PiHole available to all of your devices wherever you go. Popular options include Tailscale (easiest, but relies on trusting Tailscale) or Wireguard/OpenVPN (bare bones with excellent documentation). I think there are similar options to tailscale through NordVPN (and probably others), where it "magically" handles connecting your devices but then you face a ~5 device limit.
With Wireguard or OpenVPN you may ask: "How do I do that without opening a port? You just said that was a bad idea!" Well, the best way that I have come up with is to use a VPS (providers include Digital Ocean, Linode to name a few) where you typically get a public IP address for free (as in free beer). You still have a public port open in your virtual private network, but it's an acceptable risk (in my mind, for my threat model) given it's on a machine that you don't own or care about. You can wipe that VPS machine any time you want, the cost is time.
It's all a trade-off. You can go to much further lengths than I've described here to be "safer" but this is the threshold that I've found to be easy and Good Enough for Me™.
If I were starting over I would start with Tailscale and work up from there. There are many many good options and only you can decide which one is best for your situation!
It's definitely a skill that I haven't mastered either! That being said I think it's one of the pillars of being a bonafide "super user" and I'd like to set there one day :)
Maybe I'll take inspiration from this post and write something up about what I learn in the future about manpages.
Cheers and happy tinkering!
Thanks for putting this out for public benefit! I haven't messed around with MacOS much but the things you've mentioned are nice to know.
I believe that’s a shell/bash standard variable, but I need to learn where it came from and how it works
You may know this already, but I've found the man
(as in manual) utility to be one of the most useful things in GNU/Linux user space. I don't have much insight into '${file##*/}' off the cuff, but I can tell you there's manual entries for file
, sh
, and bash
that may help you track it down.
bash
# simply type man [some-command] man file man sh man bash man man # very useful for getting started!
Manpages are local to your system so they're extremely fast to pull up and searchable!
Here's some online info on man
if you're interested:
Exactly what I came here to say.
Prompt me for Ubuntu Pro once (in the GUI on first login)? Shame on you, but I'll move past it.
Put an ad in the terminal every time I update my system though? Straight to jail.
Right? TPUs make more sense at scale (especially for LLMs & similar). The consumer market is more about hype and being a household name than it is about revenue.
Couldn't agree more! Abstracting to a general economic case -- those hundreds of dollars are a double digit percentage of the overall cost! Double digit % cost increase for single digit % performance doesn't quite add up @nvidia :)
Especially with Google going with TPUs for their AI monstrosities it makes less and less sense at large scale for a consumers to pay the Nvidia tax just for CUDA compatibility. Especially with the entrance of things like SYCL that help programmers avoid vendor lock.
For the self hosters -- Nextcloud news!
But the underlying answer for me is an RSS feed aggregator. Set up your own feeds and tweak as needed.
Ah! I think I see the confusion.
bash
# /etc/subuid privatenoob:100000:65536
This denotes the range of subuids that are available to your user.
-u 100000:65536
This part specifies two things ([UID]:[GID]) even though it's the same syntax as the earlier part that specifies one range :)
I suspect what you will want to do is use the following:
bash
# change ownership of the directory to the UID:GID that matches something in your subuid:subgid range, in this case 10000:10000 podman unshare chown -R 100000:10000 /home/privatenoob/media/storage1/Filmek/
Then we can specify that the user in the container can match the user (UID) we specified above:
bash
ExecStart=podman run --name=radarr -u 10000:10000 -p 7878:7878 -v radarr-config:/config -v /home/privatenoob/media/storage1/Filmek:/data --restart unless-stopped lscr.io/linuxserver/radarr:latest
As a note, if you copy/pasted that ExecStart line, you might have gotten the invalid argument error because you entered 100000
(outside of your subuid range, i.e. >65536) instead of 10000
.
There's a nice guide that gives a great walkthrough. I'll dig through my bookmarks and add it here when I get some time.
Hope this helps!
There are a few ways around it. The simplest is to add the --privileged
option.
The more secure method with podman is by specifying a user (ex -u 10001:10001
) from your extended subuid:subgid range after your full and proper setup of rootless podman :-)
Then instead of chown
you'll want to use the oddly named podman unshare
tool to automatically set the permissions of the host directory. You would then want to start your service with systemctl --user
instead of sudo systemctl
*testing :)
Maybe you should learn to read the manual or debug your system without hand holding 😉