StrawberryPigtails

joined 11 months ago

https://smartgun.com/

It’s a thing, and has been since the late 90’s (I think). Reliability is the main issue. The first one I had heard of had mechanical reliability problems If I remember correctly.

Haven’t looked at Biofires products lately, but they weren’t really weatherproof last I heard and weren’t recommended for duty use as a result. And then there is the eye watering sticker price. A Taurus PT92 is less than half the price of the Biofire, and has a track record for good reliability.

I seem to remember a state, New Jersey, I think, had a law on the books saying that if multiple manufacturers came out with biometricly locked firearms that biometric locks would then become mandatory. As for if that would help things, probably not.

Last time I tried (several years ago, pre-Proton) iTunes would run fine under Wine but couldn’t see a connected iPhone.

[–] StrawberryPigtails@lemmy.sdf.org 6 points 21 hours ago (2 children)

I agree with @qocu@hexbear.net . It sounds like you are trying to replicate your workflow. Windows and Linux come from different mentalities. There won’t always be a drop in replacement.

I’m short on time but perhaps I can help with your point 9 though.

Each distro’s repos are built by the people that use that particular distro. Somebody needed a particular piece of software, found it wasn’t in the repository and decided to package it and perhaps maintain it for the repo. Sometimes this is the original developer, sometimes not.

All software is built from source code. If the source code is available for Linux, you can compile it yourself. Instructions for how to do so are usually provided by the developer along with the source code, nowadays usually found at their git repository.

Of course, you don’t have to compile all your own software (it can be a headache, which is why someone came up with precompiled packages), but it is an option if the software in question is not available in your distribution’s repo.

Your number 1 point: I like Kate, vscode and micro as text editors. They are fairly simple.

Thank you. I was trying to figure this out as well.

Currently I use Jellyfin and found it simple enough to setup. My personal setup is https on the public internet using Caddy as a reverse proxy to handle the https part, but you can set it up for local network access only using http.

Jellyfin itself is not the greatest music player ever, (UI is more setup for movies and tv) but there are music-centric apps that use it as a backend that are really good, for most platforms. On my phone and tablet, I really like Finamp, and on the desktop I use Sonixd.

I’m also considering just getting a portable, 128GB FLAC player with a minijack connection and moving on with my life without getting involved in networking at all.

I used this setup for the better part of 20 years. Nothing wrong with it, my music collection simply expanded to the point where it simply wasn't feasible to store all of it on my iPod anymore and from day to day I never really know what I'm going to be in the mood to listen to. Setting up a streaming service made more sense for me.

It sounds like a decent way to fund a server. It's not something I'm interested in, but you might get some takers.

[–] StrawberryPigtails@lemmy.sdf.org 1 points 2 weeks ago (4 children)

The simplest way to do this, is to put the server on a private vpn (I use Tailscale, there are others) and expose ports only to the vpn. Then you share access to the vpn with your friends.

With Tailscale, this is as simple as sending them a share link for the host. They will need to have an account at Tailscale, and have the client running, but they will then be able to access the host with a static ip address.

As a general rule of thumb, nothing should be exposed to the public internet unless you want that service to be public access and then you need to keep it up to date. If a vulnerability doesn’t currently exist for the service, one will sooner rather than later. SSH, especially password only ssh, can be broken into fairly easily. If you must expose ssh to the public internet for whatever reason, you need to be using IP white lists, password protected keys, change the default port, and turn off service advertisements and ping responses. I’m probably missing something. When someone scans your server randomly, they should see nothing. And if they fail login they should be ip blocked.

  1. Host family media through Jellyfin, etc. This would include tv, music, and possibly books as well. Many of these will be managed through the Arr apps.
  2. Degoogle my phone - I'm beginning by replacing Photos with Immich, but hope to also use Home Assistant, backup other phone data such as messages media, shopping lists, etc. I hope to replace Google storage/backup with Proton Drive.

Seems like a solid plan. I used Nextcloud as a Google Drive/Photos/Calander/Lists replacement, but depending on what you are running as your server it may be a bit too heavy.

I’ve heard that once you get into it, Linux distros like Ubuntu are not very user friendly for self-hosting as a beginner.

Not sure who is saying this. Granted, if your not used to *nix, our ways of doing things can be a bit obtuse from time to time but the Ubuntu based distros are some of the most heavily documented distros available with only Arch being better documented (Don't use Arch unless you've got stock in Bayer. /joking, kinda).

Your current OS choice is maybe not what I would choose, but it is fine. Xubuntu just Ubuntu Server with the XFCE desktop installed. A bit heavy for a server install as a result. One thing I will say is that most server software is setup via the command line and setup via configuration files (These are just regular text files readable by any text editor. I like micro, but anything will work). The desktop environment is just extra weight you don't really need in this application. Doesn't hurt anything, just heavy and not really needed.

So is it better on the whole for a beginner to have a popular distro with lots if documentation and step by step guides, or to have a purpose-built OS like TrueNAS that might be more straightforward, but with less support?

Stick with what you have. Ubuntu is a very well supported server distro, and the XFCE desktop doesn't change that. Things like TrueNAS, UnRAID, and whatever is the flavor of the week tend to cover things up to simplify things. This is fine when they work correctly, the problem comes when things inevitably break. You won't know where to go looking to fix things. Also TrueNAS is a network storage OS, not really suited for what you are trying to do currently, which seems to be hosting services.

It seems to be working well, but I’ve had a few hiccups trying to update it,

What hiccups were you running into? And were you using the GUI tool or apt on the command line?

[–] StrawberryPigtails@lemmy.sdf.org 18 points 3 weeks ago (1 children)

I seem to remember a scene in Babylon 5 where Vir got sick eating at a place that sounded like a rebranded McDonalds. Londo was chastising him saying you know Centauri stomachs can’t handle fast food. I wish I had time to rewatch that show.

I’m short on time, but here’s the general idea. Telegrams front end, the part you use I the open source part. The backend is the closed off part. The two parts are separate but communicate via a protocol, kinda like email. The forked project can change anything they want, to make it do whatever they want, but it still needs to be able to speak to the backend server.

[–] StrawberryPigtails@lemmy.sdf.org 12 points 1 month ago (2 children)

I don’t know about Silverblue, but I know you can use NixOS on pretty much any VPS using the tool nixos-infect.

Not sure how it would reduce your attack surface though. That’s not really the problem that they are trying to solve.

 

A question here recently brought up memories of listening to this song growing up. Long since lost my copy and had to hear it again. Figured some here might get a trip out it.

view more: next ›