These references are almost definitely tied to the newly discovered "IoT Enterprise Subscription" edition of Windows 11, not the client version of Windows vNext.
With that said, I don't think it's unlikely that the next version of Windows will have some new capabilities that require a subscription to utilize, tied to your Microsoft account and services.
I found it easy to get the front end showing but the backend stuff required a little trial, error, and searching to get sorted. Here's a part-example of what I needed to make sure the correct traffic was sent to the back end (this is using a yaml file, not inline in a compose file):
I second this. I’m a big fan of homepage. Easy to set up so long as you don’t mind a yaml config file (you can copy and paste the examples if you’re new to the format).
Ok, sure. But that’s not what you’ve shown in your post. What you’ve shown definitely won’t do what you want.
HomeKit Bridge is used to get device from Home Assistant into HomeKit. There’s another integration, HomeKit Devices, that will do what you’re wanting.
I came across this with a quick search. It looks pretty good!
Slskd is a modern client-server application for the Soulseek file-sharing network.
From the article:
These references are almost definitely tied to the newly discovered "IoT Enterprise Subscription" edition of Windows 11, not the client version of Windows vNext.
With that said, I don't think it's unlikely that the next version of Windows will have some new capabilities that require a subscription to utilize, tied to your Microsoft account and services.
And the zsh equivalent Oh My Zsh
I found it easy to get the front end showing but the backend stuff required a little trial, error, and searching to get sorted. Here's a part-example of what I needed to make sure the correct traffic was sent to the back end (this is using a yaml file, not inline in a compose file):
rule: "(Host(`domain.com`) && (PathPrefix(`/pictrs`) || PathPrefix(`/api`) || PathPrefix(`/feeds`) || PathPrefix(`/nodeinfo`) || PathPrefix(`/.well-known`))) || (Host(`domain.com`) && Method(`POST`)) || (Host(`domain.com`) && Headers(`Accept`, `application/activity+json`)) || (Host(`domain.com`) && Headers(`Accept`, `application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"`))"I also decommissioned mine as I was seeing comments and posts coming up a lot quicker and more reliably on the lemmy.nz instance.
tldr:
Their paywall is so painful.
I second this. I’m a big fan of homepage. Easy to set up so long as you don’t mind a yaml config file (you can copy and paste the examples if you’re new to the format).
It’s called homepage
Agreed. Fed by my self hosted FreshRSS server.
I hadn’t thought of that. Nice tip!