That’s insane. I would consider a ipv4 -> ipv6 cloud hosted haproxy style setup if this was my only option.
That’s insane. I would consider a ipv4 -> ipv6 cloud hosted haproxy style setup if this was my only option.
i would just ask for an Ipv4 address. I asked Vodafone for one and they just gave it to me for free.
It does?
Pixel Camera (previously known as Google Camera) can take full advantage of the available cameras and image processing hardware as it can on the stock OS and does not require GSF or sandboxed Google Play on GrapheneOS. Direct TPU and GXP access by Google apps including Pixel Camera is controlled by a toggle added by GrapheneOS and doesn’t provide them with any additional access to data. The toggle exists for attack surface reduction. Every app can use the TPU and GXP via standard APIs including the Android Neural Networks API and Camera2 API regardless.
TPUs and GXP are what enable apps to do on device ais with whatever model they choose to bring.
Who knows. We do know that all of the pixel photo features work assuming you install the pixel photo app and give it NPU permissions.
The exciting bit is that we know you can deny internet access and all the picture AI stuff still works.
If people saying “don’t vote, both sides are the same” and the like is understood to be electioneering I think this would be fair.
I do most of my cad stuff on openscad and I will say that is impressive!
Particularly since the openscad language is purely functional and side effect free.
At the cool network kids hate nat. 😤
I don’t think you have Stockholm syndrome. You just like what you already understand well. It’s a normal part of the human condition.
All those features of nat also work with IPV6 with no nat in the exact same way. When I want to open up a port I just make a new firewall rule. Plus you get the advantages of being able to address the ach host behind the firewall. It’s a huge win with no losses.
I think it’s worth taking the time to learn IPv6 property. If you have a good understanding of IPv4 it shouldn’t take you more than an afternoon.
Eliminating NAT and just using firewall rules (ie what NAT does behind your back) is incredibly freeing.
I don’t get people complaining about typing out IPs. I like to give all of my clients full FQDNs but you don’t have to. Just using mDNS would be enough to avoid typing a bunch of numbers.
You shouldn’t have to?? Maybe you might need to change the mask in your firewall settings if the ipv6 allocation block size changes but that should be it.
Everything else should just work as normal.
Yes. The left side of the : in the volume is the file on the host. You can see this directory on the host. The right side of the : is where that directory is replicated into the docker container.
All you need to do is to interact with the directory on the host.
You should use volumes over bind. You just move your media into the volume location on the local host and try will show up in docker. You should never need to ssh or sftp into the container.
There is a lot here but I think the most important thing is that docker containers should always be disposable. Don’t put any data into the container ever.
All of your data and configuration should be done in volumes. Local disk to inside the container is all you really need.
By doing this you make updating any given docker container easy as just pulling the newest tagged version of the container. If you are using docker and not podman you can use tools like watchtower to do this automatically.
As for what distro, it depends on your goals. Do you want to learn and improve your skills? Stick with Fedora or Rocky or Debian or openSUSE. I recommend learning the command line as you go, but if you want a nice UI openSUSE has Yast which is a very robust tool.
If you want to just have a home NAS but don’t want to learn that’s a different question. In this case if you’re getting a proprietary NAS anyway you could just get one that supports docker (like synology) and kill 2 birds with 1 stone.
https://codeberg.org/forgejo/discussions/issues/67
The biggest issue is they require your to give them your rights as they pertain to copyrights.
That means even if you submit MIT or GPL licensed code they can just instantly say “we relicense this code as proprietary” and there is nothing anyone can do.
They rejected a bunch of valid PRs. Including the one linked here because the author refused to assigned their copyrights to the Gitea corporation.
Right now Forgejo is a drop in replacement. This article is them announcing that Forgejo will eventually not be one.
Because gitea is fully the victim of corporate capture. Any PRs that make gitea better in a way that would reduce the main corporate “sponsor” profit are rejected.
The company has a conflict of interest with the community and it shows. Forgejo is sponsored by a non profit open source cooperative.
+1 For Seafile. They put out a docker image that works well. It hasthe fastest sync I’ve ever seen and it has good clients.
Consider yourself one of today’s 10.000. :)
What differentiates a podcast from other forms of media like YouTube is that it is delivered via RSS feeds. This lets people subscribe to the podcast using any sort of RSS reader or standards compliant podcast app.
RSS is an open source standard way subscribe to a stream of content. Sort of like a proto version of pub/sub protocol that the fediverse uses.
The reason why podcasts took off in the first place was that any mp3 player (or now days smart phone) could receive the media by subscribing to the open standards RSS feed. There was no proprietary lock in.
Mega corps obviously are not a fan of that so they try to lock people into their services regardless of this open standard. When Spotify did that exclusivity deal with Joe Rogen it was very controversial because it took the most popular podcast of the time and turned it into a proprietary media stream that you can only listen to on Spotify.
https://github.com/Podcast-Standards-Project/PSP-1-Podcast-RSS-Specification
Back in the days of windows xp and Alcohol 120% it didn’t. I remember having like 12 virtual disk drives each with an independent iso just to avoid swapping disks.