laserjet

Thank you so much this is exactly what I needed to know!!

You should post it somewhere people can find it like trash guides or smthg. Surely I am not the only person who doesnt have all this knowledge to start with.

That is great info thank you I have been bothered by this issue for years and never able to find any useful insight into solving it. Because everyone who care about audio has fancier equipment of course. It makes sense I will try to select stereo instead of surround. I just use the TV speakers.

I was typing up a reply when you posted this. And as I mentioned, it so happened I tried to play a x265 file and my TV/device did crazy things I had never seen before requiring a hard reset. Now that I see how to look at the filenames I notice that >80% of my existing collection is x264 or h264. So I think I will do as you say and stick to this.

Thanks for the advice it is all helpful.

From what I can tell I have much much lower standards than anyone who is writing online about this stuff. :)

My TV is either 720p or 1020p. Sources disagree I am not sure why and haven't investigated too deeply; maybe it is situational. I am satisfied with whatever it is. So as I understand 4k would be indistinguishable in any case.

Looking in my reasonably-sized series/film directories I am seeing a lot of files named like [HDTV-720p][AAC 2.0][x264], [SDTV][AAC 2.0][h264].mp4 so your advice on 264s is probably good for me.

Is the h264 or x264 part of the name the bitrate? If so is there a list somewhere of what term corresponds to what bitrate? I also find terms like DivX, HEVC TrueHD 7 1 (is HEVC the bitrate there?), XVID (these ones are very small and actually seem not to be picked up by jellyfin/kodi--- it was an older hard to find TV show IIRC it was all I could find).

I just tried to play a file that is [HDTV-1080p][AAC 7.1][x265].mkv which has a pretty big filesize compared to length and it made my TV/device freak out--- had to hard reset it. Is it x265 that is so much harder to handle than x264? I don't find anything else in my collection that includes this.

I can only listen to podcasts and I really dislike the trend of everything being videos. Especially when it's about how to do some technical thing and you have to watch someone using a terminal or doing a physical repair.... I literally CANNOT. I can't attend to the visuals. Just zone out. I mostly listen to TV/movies. When I was a kid you could get TV stations on the radio at night and I was totally happy to just listen to them.

So you enjoy your half of the media and I'll enjoy my half. :)

broke what

the first thing you need to understand about the law is the concept of jurisdiction.

there is no meaningful way of asking a question about the law without specifying jurisdictions you are or may be subject to. which means you need to figure that out in the first place. or ask for help figuring it out.

there is no law of any kind which applies to everyone in all situations.

sudo docker compose up

OK, well that works enough to access the specified port and loads the webapp. So that's cool. :) There's a tcp error printed in the page itself but ?maybe? that is caused by improperly running it.

It could well be some self imposed error. But I'm always gonna be making those. If it is, it happened because I was trying to solve some other rudimentary issue. I've never gotten anything functional with this so it's not like I was trying to do something fancy and got in over my head.

Part of the issue with docker in this attempt and other times is it doesn't give good enough errors/output to diagnose. It's really kind of you to help me here but I can't call you every step. The documentation is too focused on making things look simple even when they're not, and therefor glossing over whatever system weirdies are getting in the way. You identified a user issue and even I suspected it (that's why I tried all those commands with and without sudo in the above comment). Yet it is not in the official documentation as a potential cause of said error. And now that I have confirmed it, I have no idea how to solve it. I see in my browser history I've previously looked up "rootless mode". Maybe that's how I screwed this up in the first place.

Moral of the story is, docker becomes a mess immediately. :D

I really appreciate the time you took to help me but seriously there is always issues even when it's supposed to be simple/basic. Nevertheless I am in the mood to be wrong and pleasantly surprised so I follow your instructions. (Spoiler: It doesn't work. But I am not trying to request further help about this, because I am fairly resigned to the situation. I am just showing you, that I tried.)

I already had docker and docker-compose installed; I was already in the docker group; and the service was already active per systemctl. I guess from last time I tried this (not too long ago). Create directory, file etc.

$ docker compose up
unable to get image 'zefhemel/silverbullet': Cannot connect to the Docker daemon at unix:///home/username/.docker/run/docker.sock. Is the docker daemon running?

So I find Troubleshooting the Docker daemon | Docker Docs. It has several methods to find out if docker is even running which now I am confused about.

reports as inactive: # systemctl is-active docker, # systemctl status docker.service, $ docker info

report as active: $ systemctl status docker.service, # systemctl is-active docker,
$ systemctl is-active docker, # docker info

$ env | grep DOCKER_HOST and # env | grep DOCKER_HOST have no output.

ps aux | grep docker and top | grep docker tell me dockerd is running by root. So I think maybe I need to start it as a regular user for this exercise?

Found Start the daemon | Docker Docs which advises the use of dockerd either with or without sudo depending on environment.

normal user:

Starting up
dockerd needs to be started with root privileges. To run dockerd in rootless mode as an unprivileged user, see https://docs.docker.com/go/rootless/

Oh it needs to be root. OK, try again with sudo:

Starting up
failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 3952 is still running

So it is running? 3952 was pid reported by top and ps. It is running. But it's not running.

Who knows... honestly this is how it goes every time. Maybe I am running services wrong... maybe I set something up last time because I was trying to solve another problem and it was suggested and that thing is now causing me am issue. I could chase my tail on this all week.

Like I said I completely believe everyone that once you're rolling with it, it's great. I'm happy for everyone who is able to access this. I will continue to live without it for the time being.

Also syncthing fork for years here.

I got worried when the official app was discontinued but from the fork repo it seems fine.

https://github.com/Catfriend1/syncthing-android/issues/1149

https://github.com/Catfriend1/syncthing-android

Even though syncthing is great you should MAKE BACKUPS while you are setting it set up and anytime you tweak things. Things can go wrong. They might not, and there are lots of people who can truely tell you they have not had a single problem. But if you have the bad luck to check a box you didn't understand or make some other error you will be SOL.

I wish more projects would have cheap rate subscriptions. Bitwarden was my first floss subscription and I don't even consider canceling it even though I don't really need any of the premium features. (I think its more like 1€ per month.)

But these "its the price of a fancy coffee per month" ones.... Girl I haven't had a fancy coffee since like 2018.

I would love to remove non floss obsidian from my day but its just so gosh darn useful. I came across Silverbullet a while ago in one of my periodic searches for alternatives.

Main issue getting in the way for me to even try it is docker. I understand that once you are comfortable with it, its convenient, but I never got there. I have tried running it every so often and its always some kind of issue that makes me give up. I keep a list of docker-only software to try in the event I ever get over that hump and this is on it.

As a competitor against obsidian, Joplin etc the docker pre req is a very high bar to clear. Overwhelming majority of users of note taking apps have not and will not run docker.

Knowing this, it makes me less excited about this project as it exists today because the best thing about obsidian is the giant user base creating so many plugins and tools to work with it. I wouldn't care for vanilla obsidian at all, it is made great by all the community generated add ons. So a small user base is kind of inherently a knock against any given project for me.

I don't know or presume this projects goals. If they want to be an alternative to desktop apps for less technical user-base, this would have to be resolved. But totally legit if that's not the priority.