Awesome! Thanks for your work. For me this renders correctly on whatsapp in landscape and on the element desktop client.
Here is a monospace optimized version:
No No
No No
NoNo NoNo
NoNoNo NoNoNo NoNoNo
No No No No
No NoNoNoNo NoNoNo
No No No
No NoNoNo NoNoNo
I have searched for alternatives. There are none that I am aware of. I just want a streaming box that can run jellyfin with a simple remote. I really don't want to use a keyboard in bed.
If anyone knows a simple setup that boots straight into jellyfin with a remote, I would love to hear about it.
So you would need buffer barrieres essentially.
Still user watches video. Ad avoidance skips forward to buffer barrier to play ad in the background. Streamed ad is thrown away and new buffer data is received. User does not notice if the video is long enough.
In this case the buffer limit is the metadata.
Can you provide some sources that support this claim?
Well the player and its controls are client side.
I think dd is the right tool for the job. Consider using pv though. It can be much much faster.
If you are on a samsung you can maybe still enable the good swipe up actions with good lock navstar. There one can enable advanced gestures. Then you can disable the app again. The old swipe settings should be back.
I tried the new ones but the swipe up ones are just way way better.
I went from DL380g6 to DL380g9 they are quite powerful for what you get. Also very noisy though. I have installed two p40s. I love it.
I have a samsung tv from 2016 and it always lags terribly when switching inputs. Sometimes the menu takes 20 seconds to load. What is it doing?
The biggest offenders for me are:
- I struggle to navigate and make out alle the controls of the settings app. Somehow finding the settings visually is very difficult.
- The new settings app is single instance. The control panel had lots of popup windows and you could open it multiple times which allowed parallel open settings windows.
It's like spectre and meltdown you also lost the advertised performance. Less performance is better than a gaping security hole or a broken chip.
Take a look at tubearchivisit. Works great and is in development.
And clearnet use is very difficult through Tor. Exit node ips are flagged and you have impossible captchas on many sites.
Unfortunate :/
And the custom Dvorak layout with the umlauts on linux?
Nice there is a great keyboard layout creator for windows.
If you use linux do you mind sharing your custom layout and how you did it?
Sonarr prowlarr radarr and many more. These are very powerful media download managers. I recommend using usenet.
Well you can power things like egpus, monitors and gaming laptops soon. Very neat actually.
One router (opnsense) a big Poe switch and unifi aps made a huge difference. Also wiring Ethernet everywhere helped a lot.
Previously we had devolo mesh plugs.
I have a static ip (lets say 142.251.208.110).
I own the domain: website.tld
My registrar is godaddy.
If I want to change my nameserver godaddy won't allow me to enter a static ip. It wants a hostname. I observed that many use ns1.website.tld and ns2.website.tld.
I don't understand how this can work because ns1.website.tld would be served by my dns server which is not yet known by others.
Do I need a second domain like domains.tld where I use the registrars dns server for serving ns1.domains.tld which I can then use as the nameserver for website.tld?
I would like to avoid the registrars nameserver and avoid getting a second domain just for dns.
Thank you for your input.
I have two machines running docker. A (powerful) and B (tiny vps).
All my services are hosted at home on machine A. All dns records point to A. I want to point them to B and implement split horizon dns in my local network to still directly access A. Ideally A is no longer reachable from outside without going over B.
How can I forward requests on machine B to A over a tunnel like wireguard without loosing the source ip addresses?
I tried to get this working by creating two wireguard containers. I think I only need iptable rules on the WG container A but I am not sure. I am a bit confused about the iptable rules needed to get wireguard to properly forward the request through the tunnel.
What are your solutions for such a setup? Is there a better way to do this? I would also be glad for some keywords/existing solutions.
Additional info:
- Ideally I would like to not leave docker.
- Split horizon dns is no problem.
- I have a static ipv6 and ipv4 on both machines.
- I also have spare ipv6 subnets that I can use for intermediate routing.
- I would like to avoid cloudflare.
A Containerized Night Out: Docker, Podman, and LXC Walk into a Bar
---
🌆 Setting: The Busy Byte Bar, a local hangout spot for tech processes, daemons, and containerization tools.
---
🍺 Docker: walks in and takes a seat at the bar Bartender, give me something light and easy-to-use—just like my platform.
🍸 Bartender: Sure thing, Docker. One "Microservice Mojito" coming up.
---
🥃 Podman: strides in, surveying the scene Ah, Docker, there you are. I heard you've been spinning up a lot of containers today.
🍺 Docker: Ah, Podman, the one who claims to be just like me but rootless. What'll it be?
🥃 Podman: I'll have what he's having but make it daemonless.
---
🍹 LXC: joins the party, looking slightly overworked You two and your high-level functionalities! I've been busy setting up entire systems, right down to the init processes.
🍺 Docker: Oh, look who decided to join us. Mr. Low-Level himself!
🥃 Podman: You may call it low-level, but I call it flexibility, my friends.
🍸 Bartender: So, LXC, what can I get you?
🍹 LXC: Give me the strongest thing you've got. I need all the CPU shares I can get.
---
🍺 Docker: sips his mojito So, Podman, still trying to "replace" me?
🥃 Podman: Replace is such a strong word. I prefer to think of it as giving users more options, that's all. winks
🍹 LXC: laughs While you two bicker, I've got entire Linux distributions depending on me. No time for small talk.
---
🍺 Docker: Ah, but that's the beauty of abstraction, my dear LXC. We get to focus on the fun parts.
🥃 Podman: Plus, I can run Docker containers now, so really, we're like siblings. Siblings where one doesn't need superuser permissions all the time.
🍹 LXC: downs his strong drink Well, enjoy your easy lives. Some of us have more... weight to carry.
---
🍸 Bartender: Last call, folks! Anyone need a quick save and exit?
🍺 Docker: I'm good. Just gonna commit this state.
🥃 Podman: I'll podman checkpoint this moment; it's been fun.
🍹 LXC: Save and snapshot for me. Who knows what tomorrow's workloads will be?
---
And so, Docker, Podman, and LXC closed their tabs, leaving the Busy Byte Bar to its quiet hum of background processes. They may have different architectures, capabilities, and constraints, but at the end of the day, they all exist to make life easier in the ever-expanding universe of software development.
And they all knew they’d be back at it, spinning up containers, after a well-deserved system reboot.
🌙 The End.
I was bored a bit after working with podman, docker and lxc. So I asked chat gpt to generate a fun story about these technologies. I think its really funny and way better than these things usually turn out. I did a quick search to see if I can find something similar but I couldn't find anything. I really suspect it being repurposed from somewhere.
I hope you can enjoy it despite being ai generated.