spash
Joined 12 years ago
Joined 12 years ago
To someone who happened to live under a de facto Soviet occupation (not de jure, after all it was just a "requested friendly intervention with the noble intent of suppressing the rising nation-wide anti-people criminal elements, that just kind of somehow happened to last for a few decades"), this kind of wording (and the associated themes) sound indeed very familiar.
But it's interesting to see how many HN users don't see this as troubling at all, at least judging by the dozen (-s?) of downvotes that my original comment earned me since posting, not even mentioning how quickly other people that somehow dared to draw a parallel between censorship and the other, friendly kind of censorship got quickly downvoted into white five minutes from posting.
Could you elaborate a bit more on this part? I find your post quite insightful and well thought out as a whole (though my sarcasm detectors may be a bit off especially when it comes to the above sentence), but in any case, I'm not sure why you wrote "that's not the point" when everything you say seems to support exactly that point.
If you think of moderation as a tool to shape the flow of discussion in a certain pre-approved way (without, say "malicious" intent, though that can always become debatable from someone's point of view), when does moderation become censorship, or more specifically - at which point are the users allowed to think that the moderation actually became censorship? I mean, who sets the criteria? The moderator?
"Censorship is the suppression of speech, public communication, or other information that may be considered objectionable, harmful, sensitive, politically incorrect or inconvenient as determined by governments, media outlets, authorities or other groups or institutions"
How about:
"Curation by Ministry of Culture of the People's Republic of China"
That said, I think your post was well written and right on spot - but the first sentence is a so obvious trigger that there are always going to be people that won't even bother reading past it. After all, there's so much to moderate and --- "Oh, hey! There's another post that looks dangerous! I've just noticed some words!"
Oh not at all, this is good news that there is still some activity wrt 54GL (pun intended). Having alternatives to fall back to is always a good thing. I've been on DD-WRT originally since about 2007 and went through many, many years of digging through forum threads, tracking and collecting all the reasonably stable revisions, kept comparing results with nightlies with other GL owners, had some good long stable runs even with a few broken features here and there and a good number of near-brickings saved only by a handy TFTP bootstrap...
I've only dropped my last DD-WRT install roughly some two years ago when I discovered Shibby and replaced all the other alternatives with it (i.e. the other very good VicTek's RAF firmware is not usable in all deployments as it can't fit even IPv6 support into the 4MB build that the 54GL is limited with, making your options limited) and I stopped keeping much track on DD-WRT since. Some other current DD-WRT people I know weren't very happy still, even though some stay with DD-WRT for own obscure reasons.
But by the way, the forum threads you linked to don't paint the situation in the best light with regard to stability:
> My WRT54GL is running since ages on the mini-generic 14929 build, you can find it here:
> ftp://ftp.dd-wrt.com/betas/2010/...
> Together with a daily scheduled reboot I tend to forget were the thing is located in our house
"2010 firmware...""daily scheduled reboot..."
Or:
> I just upgraded to:
> ftp://ftp.dd-wrt.com/betas/2016/...
> I've tried a few different bin's and while I did get the standard version to work, it seemed a bit unstable.
"a bit unstable" is pretty much as good as simply "unstable".Now with Shibby I currently run GL with average half a year uptimes (usually ended by a forced powerplant cycle in the location, never had a crash or a spontaneous reboot on it as far as I remember). Still, as long as recent versions of DD-WRT build and run on 54GL, there's some chance at a good revision that can possibly squeeze few more years out of the hardware, depending on what features will work. Will keep an eye on it, it may still become handy if something bad happens with Shibby's work, which at this point and the age of the hardware wouldn't be that surprising.
Disclaimer: I'm by no means affiliated, but run WRT54GL hardware actively and at times I'm still regularly amazed at what Shibby can squeeze out of the mere 4MB of flash space and a hardware that wouldn't properly run a smartwatch alarm applet in 2016.
--
[1] - http://www.dd-wrt.com/wiki/index.php/Linksys_WRT54GL
[2] - http://www.dd-wrt.com/phpBB2/viewtopic.php?t=51486
[3] - http://www.dd-wrt.com/phpBB2/viewtopic.php?t=288371
If you're lucky, you may also end up with gems like this:
> Malachi - DD-WRT Guru
> Your router was made in the 1800's. Why do you need firmware made yesterday.
[4] - https://wiki.openwrt.org/toh/linksys/wrt54g[5] - http://tomato.groov.pl/
You live with your choice.
> and I can't get
You try to look harder for other options.
While the laptop situation is indeed pretty bad (the X200 is probably as best as you can get here), for people looking for a modern workstation, AMD's current FX processor lineup is still free from this trash. Past the 2013 designs (Family 16h [1]) AMD includes their own equivalent of Intel's ME called PSP [2], so presumably the upcoming Zen is going to be heavily backdoored too.
Now, you can still buy an 8-core/4 GHz+ AMD Vishera [3] generation (which is the "current" FX), add a motherboard with ECC support (in a stark contrast to Intel, all AMD FX processors fully support ECC memory and for example ASUS sells a number of AMD motherboards with ECC support) and build yourself a workstation that will easily last for another decade, possibly longer (you can always buy a motherboard or two of your favourite model as a backup for the times when they finally disappear from the market). All FX processors are factory unlocked [4] and can be pushed much farther past their design specs with decent cooling, adding another bit to their possible usefulness over the long term.
Some more (random) reading on the subject of avoiding AMD PSP and Intel ME:
http://hollaforums.com/thread/557954/technology/uncorrectabl...
-
[1] - https://en.wikipedia.org/wiki/List_of_AMD_CPU_microarchitect...
[2] - https://libreboot.org/faq/#amd
[3] - https://en.wikipedia.org/wiki/List_of_AMD_FX_microprocessors...
[4] - http://www.techpowerup.com/153445/amd-unlocked-fx-processors...
While nowadays most of my contacts are on private XMPP servers, I remember few having some reasonably solid experiences with https://jabber.at/ (can be also found at https://xmpp.zone/ for a better sounding domain name, which I guess matters to people who hate the now obsolete "Jabber" term). Can't from my personal experience vouch for a "good for a long period of time", but if someone is looking for at least a well established server, this should be as good start as any. Also, the news page shows they're quite serious about server updates and transparent, which is a big thumb up in my eyes.
Edit: typos
https://en.wikipedia.org/wiki/Intel_Active_Management_Techno...
A nice overview of what AMT and ME is capable of (and has been for the past decade) can be found in libreboot FAQ:
# Why is the latest AMD hardware unsupported in libreboot?
It is extremely unlikely that any post-2013 AMD hardware will ever be supported in libreboot, due to severe security and freedom issues; so severe, that the libreboot project recommends avoiding all modern AMD hardware. If you have an AMD based system affected by the problems described below, then you should get rid of it as soon as possible. The main issues are as follows:
# AMD Platform Security Processor (PSP)
This is basically AMD's own version of the Intel Management Engine. It has all of the same basic security and freedom issues, although the implementation is wildly different.
But that sometimes makes for really bizarre experiences watching other people browse the same websites, cursing at how slow, bloated or broken they are, seeing that until now I didn't even know that the particular website that I've been visiting for years can do THAT.
The Bloomberg site is a really good example of it - for the first time I've turned the JavaScript on for it and... WHOA.
It's like every single piece of that 'extra' JavaScript functionality serves just one single purpose - to make your time spent on the site reading the articles as much miserable as possible.
I probably don't even want to know what I'm missing elsewhere...