creshal

185 ms·

1. 1771.▲
   by creshal 11y ago

   Sure, just let me grab a sack full of jobs off my jobs tree.
2. 1772.▲
   by creshal 11y ago

   France has had the most extensive surveillance system in continental Europe for over a decade and it has helped roundabout nothing.
3. 1773.▲
   by creshal 11y ago

   > It's been clear that something needs to be done for years And what? That "something" needs to be done was clear since the 80s, but so far constructive solutions have been rather sparse. Integration is too expensive to th
4. 1774.▲
   by creshal 11y ago

   Great , there's even two extensions on it! This is why nobody wants to touch XMPP with a ten-foot pole.
5. 1775.▲
   by creshal 11y ago

   https://twitter.com/JohnLaTwC/status/708309799738314752
6. 1776.▲
   by creshal 11y ago

   > Ye sit is stupid to request a package manager that uses unsecured packages with disabled SSL and curl and wget to download packages and manage them so that any hacker could install any package it wants with a simple script. That was no
7. 1777.▲
   by creshal 11y ago

   Claims made in the blog post: 1. There's two forks of RPM. According to Wikipedia, this seems to be correct: https://en.wikipedia.org/wiki/RPM_Package_Manager#Forks 2. Most of the complaints are about RPM's b
8. 1778.▲
   by creshal 11y ago

   Realistically, no, they always have been walking dead. Without special licenses, it always was illegal to drive radio hardware out of spec. It was just largely a grey area because of how incredibly hard it was to enforce compliance. While
9. 1779.▲
   by creshal 11y ago

   I'd guesstimate it involves shipping snapshots to a cold standby, since snapshotting/cloning is mentioned.
10. 1780.▲
    by creshal 11y ago

    Much more likely, it will only require firmware blobs on the actual wifi chips (not the general purpose CPU of the router/access point built around it) for compliance. Which is already the status quo for 90% of all wifi hardware.
11. 1781.▲
    by creshal 11y ago

    Even if they could get a source, I wouldn't trust TP-Link. Their entire business models revolves around making routers as shoddily as possible, of course they have a vested interest to block open source firmwares on cheaper models from
12. 1782.▲
    by creshal 11y ago

    Throwing something into a container does not magically make it have replication nor failover.
13. 1783.▲
    by creshal 11y ago

    > So you post a German blog post I'm sorry, I didn't know Germans weren't allowed to have opinions.
14. 1784.▲
    by creshal 11y ago

    wicd is pretty much obsoleted outside Slackware because of its atrociously slow development pace. connman beats it by far in terms of "easy networking without bloat", and NetworkManager doesn't have noticeable bloat if you ha
15. 1785.▲
    by creshal 11y ago

    RPM seems hell enough in current versions: https://blog.fefe.de/?ts=a81c11aa Disclaimer, I've never worked with it, I don't know how accurate the description is.
16. 1786.▲
    by creshal 11y ago

    There is an XMPP extension for it: http://xmpp.org/extensions/xep-0136.html The problem is, there are far too damn many XMPP extensions and too few of them see any kind of real adoption.
17. 1787.▲
    by creshal 11y ago

    Skype has a web-based API nowadays that's used by quite a few third-party clients.
18. 1788.▲
    by creshal 11y ago

    And AMD has given up on it, their next-gen Zen CPU will use a more hyperthreading-alike architecture. Only caches and memory/IO controllers are usually shared between cores.
19. 1789.▲
    by creshal 11y ago

    Recent Intel CPUs with Turbo Boost have a frequency range they can operate on, with a spread of over one GHz for some models. Thermal limits dictate how much of this buffer the CPU is able to use, so better thermals do lead to higher freque
20. 1790.▲
    by creshal 11y ago

    I've used both and moved on to prosody. Ejabberd is just too arcane to configure and debug; and openfire is a damn resource hog for no apparent reasons.
21. 1791.▲
    by creshal 11y ago

    All the servers available for it suck. All the clients available for it suck. I know, I'm using it daily too, but I don't see it gaining more traction that it already has ever again.
22. 1792.▲
    by creshal 11y ago

    > Vagrant, Docker, Chef, Ansible, Fabric, Puppet, Jenkins, Octopus, TeamCity, Sentry, SVN, Git, AWS, Azure... Fair point! Although I'm just as tired of the rat race there, too. Of all the things listed, we're only using Git. I&
23. 1793.▲
    by creshal 11y ago

    > Some sort of open protocol. XMPP seems to be rather dead, for various reasons, and no real contender for a replacement has sprung up. I guess there always is, and always will be IRC…
24. 1794.▲
    by creshal 11y ago

    > Sometimes it's just too hard to resist making a joke about the reliability of Gluster. I'm glad it's not just me. I've been eyeing it for years before finally deploying it in production, and so far it's been a
25. 1795.▲
    by creshal 11y ago

    So Gluster, just better documented? /s
26. 1796.▲
    by creshal 11y ago

    I sure wish there was such a thing, all that curl|sh-ing is getting on my nerves.
27. 1797.▲
    by creshal 11y ago

    I'd like to add 16.: For number recognition, you only need to care about locale-native phone numbers. My phone is running with English locale set because German translations of apps (and even Android itself) are more often than not use
28. 1798.▲
    by creshal 11y ago

    > These things are not like each other! It seems like you're just complaining about a bunch of things based on little more than what their name is. I only know the name, because they disappear faster from our tool chain than I (as s
29. 1799.▲
    The State of JavaScript Build Tools 2015(walkercoderanger.com)

    1 points by creshal 11y ago|0 comments
30. 1800.▲
    by creshal 11y ago

    > I get that there are a lot of tools available Grunt gulp bower less sass npm node yeoman brunch underscore moustache… Whenever our frontend devs insist they need whatever deployed on all our servers yesterday, I nod and smile and count