Moving to octodon.social Show more
Is there any proper (or established) way to manage/link accounts on different instances yet?
"A particularly haunting comment is posted by one Hackernews: a Haskell program that translates C to Rust, which gives us a brief peek into the grotesque Godless painscape where the Rust Evangelism Strike Force plans its webshit-brigading operations."
OH GOD.
People that run #Linux and care about #security must read this:
https://grsecurity.net/the_truth_about_linux_4_6.php
https://lwn.net/Articles/410674/
And the post by hansoku-make at https://www.reddit.com/r/linux/comments/64rsoh/openbsd_61_released_april_11_2017/?st=j1ezcq1u&sh=12316891
Phase 1: carefully curate mastodon.biz, make very brand/corp friendly. pre-populate it with several thousand markov scenebots that follow and boost brands
Phase 2: once brand critical mass is reached, sever any federation and cast it adrift
Phase 3: Periodically inject/tweak the markov bots so that the reaction metrics and data mining look consistent within the instance.
Phase 4: pray it doesn't return like V-ger.
Huh. That's interesting. If you reply to a toot that includes a content warning, you get an identical content warning wrapper around your reply?
Is there a way to disable that?
Hello! I'm an account created to get followed by followbots!
Please boost this post!
Boosting will cause this to appear in the timelines of instances with followbots, who will then follow me!
I shall post a list of all followbots who follow me, afterwards.
Thank you for participating! :heart::robot:
Hoping SO hard that "interviews don't work" becomes the next cargo cult among startups.
https://www.nytimes.com/2017/04/08/opinion/sunday/the-utter-uselessness-of-job-interviews.html
Disclosing "cellphone contacts and social-media passwords" goes beyond having "nothing to hide". It jeopardises other people that trust you.
I can tolerate the TSA pat-downs, but you can't ask me to make decisions with the rights of others.
. @redacted @Unprovable it is not inevitable as long as we shun that bs. A company here is hurting its image not helping it. If an #infosec company follows you, block that shit immediately and tell them to leave.
This is not a marketing tool.
TheZZAZZGlitch's awesome April Fools 2017 event (Game Boy reversing challenge) is now over. Here's my writeup: https://gist.github.com/Wack0/1a84651e7e7e0c6f7d5fb5888e361123
I was discussing autonomous vehicles with a Frenchman. Summing it up by: The Turing test for autonomous vehicles is to be able to cross the place de l'étoile (Paris) quickly & safely.
a really sweet article about reverse-engineering and exploiting the Broadcom WiFi firmware https://googleprojectzero.blogspot.com/2017/04/over-air-exploiting-broadcoms-wi-fi_4.html
Still trying to get my head beyond 140 chars, so for now I'll just ctrl+v each message 3 and a half times per toot.
"Thus, determining the correct rate
at which to refresh DRAM cells has become more difficult, as also
indicated by industry [45]. This is due to two major phenomena, both
of which get worse (i.e., become more prominent) with technology
scaling. First, Data Pattern Dependence (DPD): the retention time of a DRAM cell is heavily dependent on the data pattern stored in itself and in the neighboring cells [69]. " - worth reading: https://arxiv.org/pdf/1703.00626.pdf
Can someone recommend a XML-RPC tool/library that handles large responses (1MB+) well? The one provided by xmlrpc-c defaults to a 512kB limit.
Anyone into some hardcore #mathematics? tl;dr there's been a new development of an novel way to prove Riemann, and Linear Algebra/Hermitian and Hamiltonian operators is not my forte...
Specifically, looking to discuss the finer points of this; http://journals.aps.org/prl/pdf/10.1103/PhysRevLett.118.130201
I refuse to believe the terrible culture of the internet is just how things are now. We don't need a technical solution. We need a cultural solution.
Just be you. Don't try to be edgy or aloof or cool. Don't try to make money. Be real. Be nice. Connect with humans.
x86: broken check in memory_exchange() permits PV guest breakout
The XSA-29 fix introduced an insufficient check on XENMEM_exchange
input, allowing the caller to drive hypervisor memory accesses outside
of the guest provided input/output arrays.
IMPACT
======
A malicious or buggy 64-bit PV guest may be able to access all of
system memory, allowing for all of privilege escalation, host crashes,
and information leaks.
HOLY FUCK. NO BOTS FOLLOWING YOU FOR SAYING BITCOIN. I LOVE THIS PLACE.