laserjet

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.

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.

My impression from when I've encountered this is that it is an attempt to repel bots.

Speculating/knowing about the reason doesn't help when I'm confronted with having to input the password *6mA*P7CCuVyHo8kh%x34!63wm23&uhzSMY3Xy3$*8^%7j$VeH^7

He was at a drug-fueled party with wealthy, well-connected people. There would be no reason to believe that a 17 year old girl would have the wealth or connections needed to gain access to that party.

are you new?

of course a party like that would have underage girls. it is a situation that FAMOUSLY has underage girls.

can you at least tell me they were IDing at the door?

Gaetz had every reason to believe he was engaging in consensual (if abhorrent) sexual activity with a willing adult.

what reason?

The committee said it found evidence that Gaetz did not learn the victim’s age until a month after they had sex. But “statutory rape is a strict liability crime,” the report said, referring to crimes that don’t require proof of intent for a conviction.

I took no steps towards this. I can't see any hashtags from my end.

I don't use mastodon but I vaguely recall something about a bot that would add hashtags to lemmy posts to get them visibility on there. It was opt-in at some level but not per-user or per-post. Maybe the community moderator? Or the instance admin had to install something?

I posted to my instance here https://lemmy.dbzer0.com/c/obsidianmd@lemmy.world and the comm's home instance is https://lemmy.world/c/obsidianmd. Maybe someone at one of those can tell you how it happened.

I clicked through from your comment and I found my profile on your instance, https://masto.ai/@laserjet@lemmy.dbzer0.com. I see one other post has been tagged with #piracy which I also didn't take any active steps towards. Maybe if you use this method to look at a more active user you can deduce where it's coming from.

Sorry I was not clear. I want to use the lemmy formatting in obsidian and have it correctly render the effect. They for some reason invented their own novel spoiler code that nobody else uses or supports.

See the post, or documentation (ctrl-f "spoiler").

Or click the [!] button in the WYSIWYG toolbar above the comment text entry box:

If I paste your text into lemmy I get this:

If there would be a way to make the lemmy ::: spoiler code style render as details. That's what I want. So I can copy/paste the exact same text and it will work in both places.

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.