Add post excerpts to the main page.
This commit is contained in:
parent
16f4661f42
commit
5c4fa35905
|
|
@ -5,6 +5,7 @@
|
|||
<h2>
|
||||
<a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
|
||||
</h2>
|
||||
{{ post.excerpt }}
|
||||
</li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Self-indulgent musings on total knowledge strategy games
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Vendetta Online
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Vendetta redux, Eve Online, and the MMO bug
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Scratching the itch
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Heavy Rain
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: The Rebel Flesh / The Almost People'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Rambling Review: Portal 2'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Obligatory River Song speculation thread
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: A Good Man Goes to War'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'D&D Post-mortem: I wanna cast ''magic missile''!'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Duke Nukem Forever should not exist
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Rambling Review: Braid'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: I know what's going to happen in Doctor Who series 6
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'D&D Post-mortem: Getting creative with your mage hands'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Puzzle Log: Dante Shepherd''s twitter puzzle'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: Let''s Kill Hitler'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: Night Terrors'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: The Girl Who Waited'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: The God Complex'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Puzzle Log: MGWCC #172 - The Vision Thing'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: Closing Time'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: The Wedding of River Song'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Why I'm excited about The Legend of Korra
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Wandering Son Reflections: Episode 1 - "Onna no Kotte, Nande Dekiteru?"'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Wandering Son Reflections: Episode 2 - "Kirai, Kirai, Daikirai"'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Wandering Son Reflections: Episode 3 - "Romio to Jurietto"'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Wandering Son Reflections: Episode 4 - "Watashi no Namae o Ageru"'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: The Doctor, The Widow, and the Wardrobe'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Wandering Son Reflections: Episode 5 - "Natsu no Owari ni"'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: MIT Mystery Hunt 2012
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Wandering Son Reflections: Episode 6 - "Bunkasai"'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Wandering Son Reflections: Episode 7 - "Barairo no Hoho"'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Concerto for a Rainy Day - 2012 Carolina Spring Go Tournament report
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: Languages of Skyrim
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: Asylum of the Daleks'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: Dinosaurs on a Spaceship'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: A Town Called Mercy'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: 'Doctor Who: The Power of Three'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: media
|
||||
layout: post
|
||||
title: An adventure in transliteration
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Programming: The theory'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Technophobia
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Decentralizing Second Life
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 2^8
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Then They Fight You
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Linux on the Desktop - a partial solution
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Nintendo and the Homebrew Arms Race
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Paranoid Security: Establishing a Connection the Hard Way'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: ".com is the new .org"
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: An aside on Education
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 5 things I hate about Fedora 10
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: It is pitch black. You are likely to be flamed by a fanboy.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: The Case of the Odd NetworkManager Behavior
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: How to fix PulseAudio in Fedora in 2 easy steps!
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: My new project - netjatafl
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Twitter from the command line
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Thoughts on the Transhuman revolution
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: d20tools 0.3 is here
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: The Decentralized Metaverse
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: emacs 23, dbus, and libnotify
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: so close, Netflix
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Tutorial: Creating OpenSim terrain with Blender'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Bulding bridges in the metaverse
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: BitTorrent, the Linux way
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Gaming in Linux - my adventures with wine
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Tabletop Roleplaying over the Internet
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: The Escapist - decline of a website
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Project TreeWars: The Beginning'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Project TreeWars: How to write bad code'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Project TreeWars: the road to OpenGL'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Project TreeWars: When is an OpenGL not an OpenGL?'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Project TreeWars: How Anna got her Title Screen back'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: More thoughts on the Escapist
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'EA Origin, or: a Case Study in bad consumer experience'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: dmr
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: Desura - what Steam should have been
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: 'Project Treewars: Going in Circles'
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br/>
|
||||
category: technology
|
||||
layout: post
|
||||
title: pygo - a go game client
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br />
|
||||
category: technology
|
||||
layout: post
|
||||
title: What the hell is happening to PSN?
|
||||
|
|
@ -17,4 +18,4 @@ blogger_id: tag:blogger.com,1999:blog-4209116010564764361.post-31280314593617704
|
|||
blogger_orig_url: http://www.stringofbits.net/2014/12/what-hell-is-happening-to-psn.html
|
||||
---
|
||||
|
||||
All day yesterday, I watched my husband trying to log into FF XIV on the PS4. All day, the PSN sign in servers remained down. They're still listed as offline now. Xbox Live has been back up since yesterday afternoon. So what's taking Sony so long?<br /><br />Keeping production servers online is a large part of what I do professionally, so... I know this problem domain pretty well. And I've seen a lot of... speculation that is deeply misinformed. Here are my thoughts on the problem.<br /><br />First: the cause of the outage. All evidence points to this being a DDoS (<a href="http://en.wikipedia.org/wiki/Denial-of-service_attack">Distributed Denial of Service</a>) attack. This is when a whole lot of computers from a lot of different locations send as much traffic as they can at a service, in an attempt to overwhelm it and knock it offline. The most common tool used to send all this traffic is a <a href="http://en.wikipedia.org/wiki/Botnet">botnet</a>. Building and maintaining a botnet requires a large amount of technical expertise. *Using* a botnet, on the other hand, just requires money and connections. Because the people who take the time to build a botnet often want to make money from it, so they sell time on them.<br /><br />Which brings us to the culprits of the DDoS; a group calling themselves Lizard Squad has taken credit for the attack. Whether they have any technical expertise is unknown, but they certainly seem to have access to one or more reasonably effective botnets. However, they claim to have stopped their attack yesterday, and PSN remains offline. Mitigating DDoS attacks is a tricky problem; there are things that work pretty well, but there's always an upper bound on how much traffic you can mitigate.<br /><br />So there are a few possibilities.<br /><br /><br /><ol><li><b>Lizard Squad is lying, and is still attacking PSN.</b> If they have some vested interest in making Microsoft look more competent than Sony, this is pretty plausible. Mitigating a DDoS is a real challenge, and Sony and Microsoft both clearly can't cope with these attacks. The usual solution would be to bring up more instances of the signin server; if that isn't mitigating the issue then the network infrastructure may not be able to cope either. Which doesn't say great things about Sony or Microsoft's network infrastructure. But then, this whole scenario doesn't say great things about the infrastructures of either services.</li><li><b>Another group is also attacking PSN.</b> Not much to add here; if Sony is still overwhelmed with traffic there's little they can do.</li><li><b>Sony intentionally kept PSN offline to do some sort of emergency upgrades.</b> This seems really unlikely to me; there's simply too much demand during the holidays to justify this. Sony would surely bring the servers back up and work on patches in parallel with that.</li><li><b>The attack exposed a software bug in Sony's signin servers.</b> If the signin server software is crash-looping or inexplicably serving errors now, it may be down despite engineers working on a fix as hard as they can. This would suggest that they're relying pretty heavily on some sort of stateful information that has entered a bad state, possibly a cache of some kind. (which can't be invalidated for some reason) Another possibility, which would suck for everyone involved, is that some bug caused user authentication data to be corrupted when the server was overloaded. If Sony is having to restore username/password hash data from a backup, that would explain why they are still offline. It would also explain why PSN seems to be working for some users but not others right now.</li></ol><div>Personally, I suspect #4. It fits the evidence and observed behavior of the system the best. If so, we can only hope that there's no permanent authentication data lost, because that could mean broken, unrecoverable login accounts.</div>
|
||||
All day yesterday, I watched my husband trying to log into FF XIV on the PS4. All day, the PSN sign in servers remained down. They're still listed as offline now. Xbox Live has been back up since yesterday afternoon. So what's taking Sony so long?<br /><br />Keeping production servers online is a large part of what I do professionally, so... I know this problem domain pretty well. And I've seen a lot of... speculation that is deeply misinformed. Here are my thoughts on the problem.<br /><br />First: the cause of the outage. All evidence points to this being a DDoS (<a href="http://en.wikipedia.org/wiki/Denial-of-service_attack">Distributed Denial of Service</a>) attack. This is when a whole lot of computers from a lot of different locations send as much traffic as they can at a service, in an attempt to overwhelm it and knock it offline. The most common tool used to send all this traffic is a <a href="http://en.wikipedia.org/wiki/Botnet">botnet</a>. Building and maintaining a botnet requires a large amount of technical expertise. *Using* a botnet, on the other hand, just requires money and connections. Because the people who take the time to build a botnet often want to make money from it, so they sell time on them.<br /><br />Which brings us to the culprits of the DDoS; a group calling themselves Lizard Squad has taken credit for the attack. Whether they have any technical expertise is unknown, but they certainly seem to have access to one or more reasonably effective botnets. However, they claim to have stopped their attack yesterday, and PSN remains offline. Mitigating DDoS attacks is a tricky problem; there are things that work pretty well, but there's always an upper bound on how much traffic you can mitigate.<br /><br />So there are a few possibilities.<br /><br /><br /><ol><li><b>Lizard Squad is lying, and is still attacking PSN.</b> If they have some vested interest in making Microsoft look more competent than Sony, this is pretty plausible. Mitigating a DDoS is a real challenge, and Sony and Microsoft both clearly can't cope with these attacks. The usual solution would be to bring up more instances of the signin server; if that isn't mitigating the issue then the network infrastructure may not be able to cope either. Which doesn't say great things about Sony or Microsoft's network infrastructure. But then, this whole scenario doesn't say great things about the infrastructures of either services.</li><li><b>Another group is also attacking PSN.</b> Not much to add here; if Sony is still overwhelmed with traffic there's little they can do.</li><li><b>Sony intentionally kept PSN offline to do some sort of emergency upgrades.</b> This seems really unlikely to me; there's simply too much demand during the holidays to justify this. Sony would surely bring the servers back up and work on patches in parallel with that.</li><li><b>The attack exposed a software bug in Sony's signin servers.</b> If the signin server software is crash-looping or inexplicably serving errors now, it may be down despite engineers working on a fix as hard as they can. This would suggest that they're relying pretty heavily on some sort of stateful information that has entered a bad state, possibly a cache of some kind. (which can't be invalidated for some reason) Another possibility, which would suck for everyone involved, is that some bug caused user authentication data to be corrupted when the server was overloaded. If Sony is having to restore username/password hash data from a backup, that would explain why they are still offline. It would also explain why PSN seems to be working for some users but not others right now.</li></ol><div>Personally, I suspect #4. It fits the evidence and observed behavior of the system the best. If so, we can only hope that there's no permanent authentication data lost, because that could mean broken, unrecoverable login accounts.</div>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
---
|
||||
excerpt_separator: <br />
|
||||
category: technology
|
||||
layout: post
|
||||
title: Intel NUC, remote controls, and Fedora 22
|
||||
|
|
@ -14,4 +15,4 @@ blogger_id: tag:blogger.com,1999:blog-4209116010564764361.post-24671501109772029
|
|||
blogger_orig_url: http://www.stringofbits.net/2015/10/intel-nuc-remote-controls-and-fedora-22.html
|
||||
---
|
||||
|
||||
I've had a fun time getting <a href="http://kodi.tv/" target="_blank">kodi</a> to work with <a href="http://www.amazon.com/gp/product/B003WM5J0O?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00" target="_blank">my new remote</a> on an <a href="http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i3ryh.html" target="_blank">Intel NUC</a>. So, in case you're in a similar situation, here's what worked for me! These instructions are for Fedora 22 and the hardware I linked to in this paragraph, but a lot of the instructions should be applicable in slightly different situations as well.<br /><ol><li>Update your Intel NUC to the latest bios. At least on the RYH line, they fixed some problems with the IR receiver in a recent update.</li><li>In the NUC bios, make sure the IR port is enabled and set the IR controller type to "RC6". Kodi works much better out of the box with this protocol. Some of your buttons aren't going to work right, though. The hard part is fixing that.</li><li><b>Do not install lirc. lirc is an unintentional trap created by well-meaning people. It will not help you here.</b></li><li>Instead of lirc, install v4l-utils to get ir-keytable:<br /><code>dnf -y install v4l-utils</code></li><li>Now, here's why you don't want lirc: with an RC6 receiver, the kernel is going to parse your remote's input and output keyboard events. Unfortunately, many of the keysyms it sends aren't properly handled by Xorg. So, you need to remap those keysyms to working keysyms of your choice. To do that, you need exactly one bit of the process described <a href="http://forum.kodi.tv/showthread.php?tid=114124" target="_blank">here</a>. Copy the <code>/etc/rc_keymaps/rc6_mce</code> file provided by wstewart at that link, and then run the command they mention:<br /><code>ir-keytable -c -p RC-5,RC-6 -w /etc/rc_keymaps/rc6_mce</code><br />You'll need to get that command to run at startup, as well. I found that all the rest of wstewart's instructions were unnecessary with a modern kernel and kodi installation.</li><li>Now, fire up kodi, and bask in the glory of your remote working correctly!</li></ol>If you want to remap what some of the buttons do, you can get the scancodes with <code>ir-keytable -t</code>, then edit <code>/etc/rc_keymaps/rc6_mce</code>. See the <a href="http://kodi.wiki/view/Keyboard_controls" target="_blank">kodi keyboard shortcuts</a> page for details on what keypress you need to send. If you can't figure out what the constant name for a key is, (most of them are obvious) refer to the kernel source's <a href="http://lxr.free-electrons.com/source/include/uapi/linux/input.h" target="_blank">input.h</a>.
|
||||
I've had a fun time getting <a href="http://kodi.tv/" target="_blank">kodi</a> to work with <a href="http://www.amazon.com/gp/product/B003WM5J0O?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00" target="_blank">my new remote</a> on an <a href="http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i3ryh.html" target="_blank">Intel NUC</a>. So, in case you're in a similar situation, here's what worked for me! These instructions are for Fedora 22 and the hardware I linked to in this paragraph, but a lot of the instructions should be applicable in slightly different situations as well.<br /><ol><li>Update your Intel NUC to the latest bios. At least on the RYH line, they fixed some problems with the IR receiver in a recent update.</li><li>In the NUC bios, make sure the IR port is enabled and set the IR controller type to "RC6". Kodi works much better out of the box with this protocol. Some of your buttons aren't going to work right, though. The hard part is fixing that.</li><li><b>Do not install lirc. lirc is an unintentional trap created by well-meaning people. It will not help you here.</b></li><li>Instead of lirc, install v4l-utils to get ir-keytable:<br /><code>dnf -y install v4l-utils</code></li><li>Now, here's why you don't want lirc: with an RC6 receiver, the kernel is going to parse your remote's input and output keyboard events. Unfortunately, many of the keysyms it sends aren't properly handled by Xorg. So, you need to remap those keysyms to working keysyms of your choice. To do that, you need exactly one bit of the process described <a href="http://forum.kodi.tv/showthread.php?tid=114124" target="_blank">here</a>. Copy the <code>/etc/rc_keymaps/rc6_mce</code> file provided by wstewart at that link, and then run the command they mention:<br /><code>ir-keytable -c -p RC-5,RC-6 -w /etc/rc_keymaps/rc6_mce</code><br />You'll need to get that command to run at startup, as well. I found that all the rest of wstewart's instructions were unnecessary with a modern kernel and kodi installation.</li><li>Now, fire up kodi, and bask in the glory of your remote working correctly!</li></ol>If you want to remap what some of the buttons do, you can get the scancodes with <code>ir-keytable -t</code>, then edit <code>/etc/rc_keymaps/rc6_mce</code>. See the <a href="http://kodi.wiki/view/Keyboard_controls" target="_blank">kodi keyboard shortcuts</a> page for details on what keypress you need to send. If you can't figure out what the constant name for a key is, (most of them are obvious) refer to the kernel source's <a href="http://lxr.free-electrons.com/source/include/uapi/linux/input.h" target="_blank">input.h</a>.
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
Loading…
Reference in New Issue
Block a user