view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
That's sort of what I mean by "just how the internet works" where "it's that it's anybody's guess if any of the hops will pass it along."
Like yeah I understand TCP has protections against dropped packets, but that's only because it re-requests the packets it thinks are lost or corrupt.
Also HTTP and WOL are at a different layer, they're both TCP and UDP respectively, so it shouldn't matter whether if the App layer is obscure or not. Heck the routers of the internet only look at the IP layer, so it can't even tell if it's TCP 443, and you could probably even write your own Transport layer protocol and route it over the internet.
Although I guess firewalls could do some prioritisation, and wouldn't like this new transport layer, but they're usually near the ends of the connection, not in the middle, and I was taught to prioritise VoIP stuff anyway.
TCP/IP model for reference:
*I have not much experience so I may have made some mistakes, but I'm currently completing a CCNA so it should be somewhat correct.