<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for Roman2K</title><link>http://disqus.com/by/Roman2K/</link><description></description><atom:link href="http://disqus.com/Roman2K/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 16 Jan 2021 10:42:12 -0000</lastBuildDate><item><title>Re: Brighteon</title><link>https://www.brighteon.com/aea0f04a-b58f-478f-95dd-37701724e8ef#comment-5229667497</link><description>&lt;p&gt;And they will.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Sat, 16 Jan 2021 10:42:12 -0000</pubDate></item><item><title>Re: Not Disclosing One&amp;#8217;s Bitcoin May Become a Crime in the US</title><link>https://nulltx.com/not-disclosing-ones-bitcoin-may-become-a-crime-in-the-us/#comment-3652857198</link><description>&lt;p&gt;Bitcoin transactions are easily traceable back to a physical person, regardless of their state's privacy laws because the transaction history is public and clear-text. Even cross-blockchains transactions are traceable via the exchange that keep records of which addresses funds come from and go to. For more anonymity, there's Dash with its optional PrivateSend.&lt;/p&gt;&lt;p&gt;For actual, full anonymity, there's only Monero as far as I know. It's got all the advantages of Bitcoin plus better scalability and end-to-end untraceability. Even more so soon with the upcoming Tor-like Kovri to hide IPs when connecting to the blockchain's P2P network.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Fri, 08 Dec 2017 11:51:18 -0000</pubDate></item><item><title>Re: Blow Bitcoin, Don’t Destabilize Government: AD Newspaper</title><link>https://cointelegraph.com/embed/disqus/14198#comment-3647692393</link><description>&lt;p&gt;These all sound to me like reasons to buy and HODL, definitely not sell. Decentralization is the whole point. Fear from governments is further confirmation that current cryptocurrencies are successful at it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Tue, 05 Dec 2017 10:50:31 -0000</pubDate></item><item><title>Re: What&amp;#8217;s a Feature From Your Device That You Wish Every Phone Had?</title><link>https://www.xda-developers.com/whats-a-feature-from-your-device-that-you-wish-every-phone-had/#comment-3543000891</link><description>&lt;p&gt;Second that! Even the iPhone has it. I don't understand how other manufacturers (save for OnePlus) don't copy that instead of half-baked gimmicks (dual camera, force touch, facial recognition, etc.).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Fri, 29 Sep 2017 18:01:19 -0000</pubDate></item><item><title>Re: Every Android owner should check out the OnePlus Bullets V2 in-ear headphones</title><link>http://mobilesyrup.com/2016/12/29/dont-dodge-the-one-plus-bullets-v2/#comment-3131722500</link><description>&lt;p&gt;Thanks for the recommendation. OnePlus is definitely one company to follow closely for their quality products (love the OP3). As for fully-Android compatible earphones, a good, cheap pair is Samsung EG920BW. Decent sound quality, working microphone, volume and play/pause controls,flat cable, seem water resistant, no fraying so far. For less than 10€.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Wed, 01 Feb 2017 04:07:04 -0000</pubDate></item><item><title>Re: Weekly update: 2016 week #52</title><link>http://blog.dynalist.io/2016-week-52-update/#comment-3081890383</link><description>&lt;p&gt;Love what you're doing, changelog included 😉 I'm using Dynalist daily, appreciating the numerous features, polish and robustness. Super happy customer! Keep up the good work! 👌&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Tue, 03 Jan 2017 20:35:35 -0000</pubDate></item><item><title>Re: Galaxy S7 Bootloader Lock Explained: You Might Not Get AOSP After All</title><link>http://www.xda-developers.com/galaxy-s7-bootloader-lock-explained-you-might-not-get-aosp-after-all/#comment-2580035513</link><description>&lt;p&gt;Nice summary of the state of S7 rooting. I appreciate the separation of objectivity from opinions left for last.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Sun, 20 Mar 2016 15:13:12 -0000</pubDate></item><item><title>Re: Project Maelstrom: The Internet We Build Next</title><link>http://blog.bittorrent.com/2014/12/10/project-maelstrom-the-internet-we-build-next/#comment-1965654958</link><description>&lt;p&gt;No offense but I'm not sure you understand Atwas911's point: it's all about transparency. Of course there's a chance the company's closed source app is free of exploits, and maybe they communicate openly about flaws and fix them quickly with honesty and humility. Maybe not. Very unlikely, in fact. That's the point: closed source means we don't have a clue if we can trust them. If you're fine with letting your personal info flow through a black box on the off chance the company that made it is straight, go ahead. People who have learned from past events know better and expect the source for code review and installs from unadulterated source.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Mon, 13 Apr 2015 16:41:56 -0000</pubDate></item><item><title>Re: Project Maelstrom: The Internet We Build Next</title><link>http://blog.bittorrent.com/2014/12/10/project-maelstrom-the-internet-we-build-next/#comment-1958999677</link><description>&lt;p&gt;I see what you mean. I didn't know they forked Chromium at the time of this article. I thouht they would just re-use a rendering engine and build a new UI around it. Of course people wouldn't want to install a proxy separate from the browser. I was thinking of a browser extension that would include the proxy, hide away all the technical details, and be OS-agnostic by definition.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Sat, 11 Apr 2015 10:46:04 -0000</pubDate></item><item><title>Re: Project Maelstrom: The Internet We Build Next</title><link>http://blog.bittorrent.com/2014/12/10/project-maelstrom-the-internet-we-build-next/#comment-1737399472</link><description>&lt;p&gt;Haha! You actually made me laugh :-) Not that I disagree. It's just that I tend to lean more toward a UNIX philosophy where each component should do one thing and do it well. So my point is to decouple the UI from this new decentralized transport. If today's browsers could be improved / overhauled, why not (good luck though), but prefer modularity over building one big monolithic mammoth to enable flexibility whenever possible, which is the case here.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Thu, 11 Dec 2014 15:06:34 -0000</pubDate></item><item><title>Re: Project Maelstrom: The Internet We Build Next</title><link>http://blog.bittorrent.com/2014/12/10/project-maelstrom-the-internet-we-build-next/#comment-1736751704</link><description>&lt;p&gt;I like the concept, very interesting and noble initiative. However, if I understand correctly, you're building yet another browser, a.k.a. reinventing the wheel. Including page rendering and whatever surrounds the network layer; which is not warranted by your cause. I'd rather you architected Maelstrom as a local HTTP proxy which any browser (including Linux compatible ones, in this case) can connect to and take advantage of both the P2P nature and the hard work from dedicated browser developers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Thu, 11 Dec 2014 09:13:40 -0000</pubDate></item><item><title>Re: crontab: temp file must be edited in place</title><link>http://drawohara.com/post/6344279#comment-1704755752</link><description>&lt;p&gt;A more elegant solution, IMO: &lt;a href="http://calebthompson.io/crontab-and-vim-sitting-in-a-tree/" rel="nofollow noopener" target="_blank" title="http://calebthompson.io/crontab-and-vim-sitting-in-a-tree/"&gt;http://calebthompson.io/cro...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Fri, 21 Nov 2014 03:20:58 -0000</pubDate></item><item><title>Re: Windows Phone sales up year on year and the unchallenged third ecosystem</title><link>http://allaboutwindowsphone.com/flow/item/19914_Windows_Phone_sales_up_year_on.php#comment-1463430993</link><description>&lt;p&gt;You got fooled by the charts. Actually, if you do the math, you'll see the exact opposite: WP is the fastest growing of the three. YoY: Android = +2.73%, iOS = +10.11%, WP = +15.19%&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Tue, 01 Jul 2014 10:49:46 -0000</pubDate></item><item><title>Re: Roccat Pyra Wireless Mouse Review</title><link>http://www.techinferno.com/2011/04/12/roccat-pyra-wireless-mouse-review/#comment-874314252</link><description>&lt;p&gt;Stellar review. Definitely helped me make a choice (in favor of the Pyra). Thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Wed, 24 Apr 2013 10:37:57 -0000</pubDate></item><item><title>Re: BlackBerry Z10 Review | TechnoBuffalo</title><link>http://www.technobuffalo.com/reviews/blackberry-z10-review/#comment-800273822</link><description>&lt;p&gt;"no it isn't" ... "the only [review] that said the battery life was good".&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Fri, 15 Feb 2013 08:44:40 -0000</pubDate></item><item><title>Re: Hewlett-Packard Company (HPQ): Will 2013 Be Any Better?</title><link>http://www.insidermonkey.com/blog/?p=47874&amp;preview=true#comment-782516721</link><description>&lt;p&gt;Thanks for the obvious but you conveniently forgot about servers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Tue, 29 Jan 2013 18:12:57 -0000</pubDate></item><item><title>Re: yield-gotcha every Ruby developer should be aware of</title><link>https://railsware.com/blog/2012/11/20/yield-gotcha-in-ruby-blocks/#comment-718721938</link><description>&lt;p&gt;I didn't say it's not valid Ruby, obviously it is, that's not my point.&lt;/p&gt;&lt;p&gt;If you read my gist code, the implicit "begin" block (via "def") is too wide. "f" should be initialised outside, otherwise "f" may be nil in the ensure block. That's why "ensure" is misplaced.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Sun, 25 Nov 2012 08:54:50 -0000</pubDate></item><item><title>Re: yield-gotcha every Ruby developer should be aware of</title><link>https://railsware.com/blog/2012/11/20/yield-gotcha-in-ruby-blocks/#comment-717853390</link><description>&lt;p&gt;Misplaced "ensure" statement in your #ensured_with_file. Correct version:&lt;br&gt;&lt;a href="https://gist.github.com/4137772" rel="nofollow noopener" target="_blank" title="https://gist.github.com/4137772"&gt;https://gist.github.com/413...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Fri, 23 Nov 2012 19:06:24 -0000</pubDate></item><item><title>Re: uTorrent 3.22 released, officially supports Windows 8 and now displays ads in-client</title><link>http://thenextweb.com/insider/2012/11/09/utorrent-3-22-released-officially-supports-windows-8-and-now-displays-ads-in-client/#comment-708318467</link><description>&lt;p&gt;I wouldn't use (let alone trust) a BitTorrent client with ads and toolbar crapware. I recommend rtorrent (+ ruTorrent) or Transmission. Both open-source, clean, safe, headless w/ optional GUI.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Mon, 12 Nov 2012 11:42:53 -0000</pubDate></item><item><title>Re: CyanogenMod 10 :: M2</title><link>http://www.cyanogenmod.org/blog/cyanogenmod-10-m2#comment-685121821</link><description>&lt;p&gt;Thanks for your work. Are you planning on making CM compatible with the Galaxy Note II? I already love this device as-is, but your CM on it would be fantastic.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Wed, 17 Oct 2012 08:15:11 -0000</pubDate></item><item><title>Re: Between a rock and a hard place - our decision to abandon the Mac App Store</title><link>http://atlassian.staging.wpengine.com/2012/02/between-a-rock-and-a-hard-place-our-decision-to-abandon-the-mac-app-store/#comment-914305135</link><description>&lt;p&gt;FWIW, I would be more likely to use your app knowing it's running safely within the constraint of a tight container, implying that I configure it manually, than if I had to trust it with my $HOME.&lt;/p&gt;&lt;p&gt;Besides, regardless of filesystem access restrictions, I also much prefer manual configuration (failsafe, no surprises) vs. automatic (trying to be clever, clunky, endless hours of debug). The very reason I use rbenv rather than rvm.&lt;/p&gt;&lt;p&gt;That's just me, though surely I can't be alone.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Tue, 14 Aug 2012 13:04:26 -0000</pubDate></item><item><title>Re: AMD Counter-Attacks GeForce GTX 670, Questions NVIDIA's Kepler Availability - Bright Side Of News*</title><link>http://www.brightsideofnews.com/news/2012/5/9/amd-counter-attacks-geforce-gtx-6702c-questions-nvidias-kepler-availability.aspx#comment-525384013</link><description>&lt;p&gt;Says you with your narrow use of your GPU (games only?). Do you even know what GCN is?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Thu, 10 May 2012 08:46:35 -0000</pubDate></item><item><title>Re: Putting people first</title><link>http://conversations.nokia.com/2012/04/11/putting-people-first/#comment-495251757</link><description>&lt;p&gt;I wasn't planning on buying a Nokia phone any time soon, but seeing such a prompt acknowledgement of an issue, a fix and even compensation, has made me reconsider.&lt;/p&gt;&lt;p&gt;This is remarkable handling of the situation. Congratulations!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Thu, 12 Apr 2012 03:49:36 -0000</pubDate></item><item><title>Re: Path uploads your entire iPhone address book to it's servers</title><link>http://mclov.in/2012/02/08/path-uploads-your-entire-address-book-to-their-servers.html#comment-432357038</link><description>&lt;p&gt;Good job calling them out on this. But that's what careless users / consumers get for trusting closed-source apps.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Tue, 07 Feb 2012 17:12:38 -0000</pubDate></item><item><title>Re: Mike Pack Development</title><link>http://mikepackdev.com/blog_posts/24-the-right-way-to-code-dci-in-ruby#comment-422132207</link><description>&lt;p&gt;To me, AddToCartContext.execute should be kept more generic by taking user and book instances as arguments, rather than IDs. It's up to the caller (in this case, a controller) to deal with IDs to find the corresponding instances.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roman2K</dc:creator><pubDate>Fri, 27 Jan 2012 04:46:41 -0000</pubDate></item></channel></rss>