Add posts/post-12/index.html and update posts/rssfeed.xml
This commit is contained in:
Primrose
parent
83d9b32bdd
commit
aff046d277
|
|
@ -0,0 +1,31 @@
|
|||
<!--Page design by Lilium_Snow (2022)-->
|
||||
<!--This HTML document is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. Get a copy of the license at https://creativecommons.org/licenses/by-sa/4.0/legalcode-->
|
||||
|
||||
<!DOCTYPE html>
|
||||
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<link rel="icon" type="image/x-icon" href="/assets/images/favicon.png">
|
||||
<link rel="stylesheet" href="/main_theme.css">
|
||||
<title>Post Viewer - Snowcake</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>12 - I hate ISP routers</h1>
|
||||
<h2>Date: 2022-11-18</h2>
|
||||
<div>
|
||||
<a href="/posts" class="button">📰 Back to Post List</a>
|
||||
</div>
|
||||
<br>
|
||||
<br>
|
||||
<div class="content">
|
||||
<p style="text-align: left">I hate ISP provided routers with a passion. They're always locked down, bloated, and always allow the ISP to remote into my fucking gateway. I know that this is mainly for remotely assisting with any issues a customer may encounter, or for remotely upgrading firmware on the router, as my ISP does. For most people, especially residential customers, this is a very good thing. But, as someone who knows more than her fair share of networking stuff, this has become an annoying pain to deal with. What makes this worse for me is that I don't have a static IP address at home, nor do I have an option to as a residential customer, so when my ISP decides to remote into my router, upgrade it's firmware, and reboot it, I get an entirely new WAN IP address, which is a pain in the ass, because since I host a web server from home, it means that I have to go into my registrar's DNS configuration and update my A record, which can be really annoying once you've had to do it enough (I know that you can use things like dynamic DNS to ease this issue, but my stupid ISP router doesn't support custom dynamic DNS providers, and I don't want to use any of the ones that are pre-selected for me in the web interface). Hell, I can't even close off the ports that are used for remoting into my gateway, since the firewall is very basic and only allows for custom allow inbound rules, not deny rules. As a network administrator at home, i'm just not okay with my ISP having remote access to my gateway, arguably one of the most crucial parts of my network. I'll be rectifying this issue soon enough though, so stay tuned.</p>
|
||||
<br>
|
||||
<p style="text-align: left">Signed,</p>
|
||||
<p style="text-align: left">Lilium_Snow (Primrose)</p>
|
||||
</div>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -101,5 +101,11 @@ My school uses google classroom as it's assignment and class information distrib
|
|||
<pubDate>2022-10-11</pubDate>
|
||||
<description>My school was making preparations for an event this month, and as part of those preparations, asked that students pick what group they'd like to be placed in for a certain activity. Students submitted a survey online with that information, and they were placed into groups shortly after. This is where things get absolutely stupid however, as someone in charge of the planning for this event thought it would be a great idea to publish student group placements on the school's public facing website. They embedded a spreadsheet onto a page which contained 440 students first and last names, grades, and school email addresses. That's right, a nice little fucking doxx by the people you'd expect to doxx you the least. Whoever published those changes onto the school website should lose their job, because if students personal information is in the hands of someone like that, I fear for what their next little "fuck up" might bring. As far as I know, students were too stupid to realize the severity of the situation, and parents did not see, only because I let school administators know of this little "fuck up" early on. That's right, a student, me, let them know of their mistake, not a staff member. What a joke. [2022-10-16] UPDATE: I have spoken with a few invididuals, and it has come to my attention that the person responsible for this error was the only one working on this big event. I no longer believe that she deserves to lose her job, and I no longer believe she deserves 100% of the blame for this incident. I believe my school's upper administration deserves some, if not most of the blame for this error for it's poor coordination in preparing a team for the event in question.</description>
|
||||
</item>
|
||||
<item>
|
||||
<title>I hate ISP routers</title>
|
||||
<link>https://snowcake.me/posts/post-12</link>
|
||||
<pubDate>2022-11-18</pubDate>
|
||||
<description>I hate ISP provided routers with a passion. They're always locked down, bloated, and always allow the ISP to remote into my fucking gateway. I know that this is mainly for remotely assisting with any issues a customer may encounter, or for remotely upgrading firmware on the router, as my ISP does. For most people, especially residential customers, this is a very good thing. But, as someone who knows more than her fair share of networking stuff, this has become an annoying pain to deal with. What makes this worse for me is that I don't have a static IP address at home, nor do I have an option to as a residential customer, so when my ISP decides to remote into my router, upgrade it's firmware, and reboot it, I get an entirely new WAN IP address, which is a pain in the ass, because since I host a web server from home, it means that I have to go into my registrar's DNS configuration and update my A record, which can be really annoying once you've had to do it enough (I know that you can use things like dynamic DNS to ease this issue, but my stupid ISP router doesn't support custom dynamic DNS providers, and I don't want to use any of the ones that are pre-selected for me in the web interface). Hell, I can't even close off the ports that are used for remoting into my gateway, since the firewall is very basic and only allows for custom allow inbound rules, not deny rules. As a network administrator at home, i'm just not okay with my ISP having remote access to my gateway, arguably one of the most crucial parts of my network. I'll be rectifying this issue soon enough though, so stay tuned.</description>
|
||||
</item>
|
||||
</channel>
|
||||
</rss>
|
||||
|
|
|
|||
Loading…
Reference in New Issue