threads   6559

« earlier    

Epic twitter thread from @colmmacc explaining why client certs and mutual-auth TLS are TERRIBAD
Ok. tweet thread time! Too long ago I promised to write a screed explaining how much I hated mutual-auth TLS and why. I got distracted, and I wasn't happy with the writing, so here it is in tweet thread form instead! But basically: Client certs and Mutual-Auth TLS is TERRIBAD.
When I say TERRIBAD, I mean that unless you've got the resources of a big security dept and folks who comb threat models for a living, using clients certs and mutual auth probably materially lessens your security. That's NUTS!

(source: )
terribad  rants  twitter  threads  tls  ssl  authentication  mtls  security 
16 days ago by jm
RT : "The image speaks and, in doing so, demands a reaction." Horst Bredekamp refers to actual language here.

history  threads  theory  from twitter
18 days ago by RosenJ
RT : A thought: Having grown up in New York City, where almost all my friends were Jewish, and many of my teachers and t…
threads  from twitter
18 days ago by RosenJ
Excellent Twitter thread from colmmacc on how s2n avoids protocol-state errors
using a linearized set of state transitions, and Cryptol and SAW to perform verification of the TLS state machine
cryptol  saw  formal-verification  twitter  threads  colmmacc  security  s2n 
27 days ago by jm
GitHub - real-logic/agrona: High Performance data structures and utility methods for Java
Agrona provides a library of data structures and utility methods that are a common need when building high-performance applications in Java. Many of these utilities are used in the Aeron efficient reliable UDP unicast, multicast, and IPC message transport and provides high-performance buffer implementations to support the Simple Binary Encoding Message Codec.
java  performance  datastructures  threads 
28 days ago by slowbyte
Why archiving old threads is a bigger problem than we've realized : TheoryOfReddit
I was doing some research on Reddit into a murky tax topic, and found some very valuable threads, but which also had some incorrect comments. The information later got legally clarified after the thread started, and now there are reputable sources, but there wasn't enough time for redditors to come back to the thread and point out the current state of affairs. After a couple months, the threads were archived.

Now, anyone who reads the threads will be misinformed. In this case, this misinformation may have serious consequences (inadvertent tax evasion/fraud, penalties etc.). Of course, nobody should rely *solely* on Reddit as the source of truth for tax matters, but the problem still stands, and I've landed from Google onto many other threads with unchallenged outdated comments:

**Why do we make threads read-only, making it impossible for users to correct outdated or inaccurate information?**

I happened to have reliable sources on that topic, and would've been more than happy to drop some links in some comments. But I couldn't. I couldn't even downvote the incorrect comments. This was frustrating.

I went on to look for the rationale as to why threads are archived. Here are the top arguments I've found:

# Arguments for archiving (debunked below)

## Technical limitations ([storage space](

Perhaps this was a technical reason back in the day, but I find it hard to believe it's a serious concern in this day and age of elastic computing and cloud storage. Reddit threads are *plain text*, not videos or even images.

Furthermore, [apparently](

> the admins have said [archiving is] fairly arbitrary and doesn't affect server load that much.

## Necroposting

> Think about it, wouldn't it be annoying if people started re-commenting on a thread you made six years ago?

No, I would be happy to learn of a change or new perspective to something I wrote. If someone bothers to comment on an old thread, they probably have something useful to say. If it's not useful, we already have [that problem with open threads, and it has targeted solutions](

## Surfacing old content

> Furthermore, with the current system of reddit how is a new person going to find these threads,

From search engines, links, IMs etc. The same way other content is found on the Internet.

> how would new posters be noticed on these threads

The same way they get noticed one month before the thread gets archived.

> and why would anyone even want to comment on them?

Because the information has become outdated or inaccurate. Because a new perspective can be shared. Because something new and related came to light. And so on. Why do we still discuss the works of ancient Greek philosophers?

> Not sure about why you can't vote, but I'm sure it's for similar reasons - who's going to benefit on you up-voting a six year old thread?

* Myself - I use upvoting to "bookmark" threads I've found useful, which I can later find under `<username>/upvoted`;
* or others who are curious about the user and want to see what they've been upvoting. I get a lot of interesting content from the upvotes of several friends I follow.

## 99% of conversations [have died anyway](

> 99.999% of all conversations have died already

Then let them die, and the storage space problem is moot if conversations die anyway.

> and the tiny percentage that haven't can be accomplished through a pm

This solution is rather myopic - only the recipient of the PM will learn of the new comment/PM; nobody else. In the tax example above, the point is to help new users who are researching the topic *now*, rather than someone who's already spread outdated information and moved on.

## [Irrelevance](

> I think the purpose is for relevance. Comments being made to posts over 6 months old would likely not be relevant.

Really? Who is to judge that? Why doesn't YouTube ban comments on videos older than 6 months?

## [Prevent SEO spam](

> It also helps prevent SEO link spam

Maybe I haven't hung out in the dark corners of Reddit, but the amount of link spam I've seen in 10+ years has been very, very minimal. Anyway, spam is a different problem, and again, has targeted solutions (the "Report" link). Banning comments altogether is a weak blanket solution with the unintended consequences I've highlighted above. Let's recap them.

# Arguments against archiving

* [Let the dialogue continue](!
* Let users correct outdated information! Super useful in any subreddits about rapidly-changing topics, such as any type of software. Often a new version comes out with a settings that solves the problem, but there's no way to inform users that the thread in question got solved.
* Archiving causes the same topic to be rehashed over and over, because new users can't revive old threads. Case in point, many links in this post are to other threads asking the very same question, "Why do we archive?". I did my research, I didn't want to rehash the topic, but responding inline to the arguments I've found was impossible.
* *Seeing a page archived is as sad to me as [seeing something die]( I know that nothing new or important can ever come to this page again.*
* *Real life seems to be a dynamic and ongoing discussion of old and new events. The voting mechanism of reddit is effective for finding the best content throughout the history of the site. However, neither of these things can continue after a post has reached an artificial date of expiration.*
* *I've never seen another site that blocks interaction with old content merely because it's old. If a page fills up with spam, that's understandable, but why should I consider last year's reddit as totally dead and irrelevant?*
* *The aggregate of reddit over time should be as important as the reddit of today.*

1. Have I missed anything? Are there *good* arguments for intentionally killing conversations?
2. What can be done to change the thread archival policy?
Dascalescu  advocacy  Reddit  against  archiving  threads 
29 days ago by dandv
Iva Cheung on Twitter: "[*Rubs temples. Deep breath in. Deep breath out.*] A'ight, folks? This issue keeps coming up every couple months. Please spread this here word so more people understand: Indexing is not easy. Indexing is not easy. Indexing is not e
(This is a pretty decent thread from Iva on indexing.)
“[_Rubs temples. Deep breath in. Deep breath out._]
“A’ight, folks? This issue keeps coming up every couple months. Please spread this here word so more people understand:

“Indexing is not easy.
“Indexing is not easy.
“Indexing is not easy.

“Please stop assuming indexing is easy. 1/”
indexing  index  indexers  2018  twitter  threads  IvaCheung 
4 weeks ago by handcoding

« earlier    

related tags

2018  _sagesharp_  aaronleitch  abuse  advice  advocacy  against  amazon  amc  amphibians  analysis  analyzer  api  append-only  architecture  archiving  arduino  async  authentication  autism  autismpolitics  await  backgroundworker  bestpractices  blockchain  blocking  bounds  brunei-tweets  bugs  c#  c++  c  cad  callback  callbacks  campaign  canonical  cat:experiences  chloedykstra  chrishardwick  citizenship  cli  clip  code  colmmacc  commonlanguageinfrastructure  compliance  concurrency  concurrentprogramming  context-switch  context  conversation  cop4600  cores  coroutines  cpu  cpus  cryptol  csp  dascalescu  databases  datastructures  deadlock  debugging  design  destiny2  development  dialog  doctorwho  done  drops  dv  education  email  engineering  escalation-protocol  eso  eu  event-sourcing  evented  example  family  feminism  fibers  fiction  fiona  food  formal-verification  forums  fs  fuckno  gaming  gaolnaofa  gdal  gdpr  geography  geojson  geotiff  gif  go  golang  goroutine  gretchenamcc  gui  gvl  hardware  hardwick  hariraya  heap  history  iis  immigration  index  indexers  indexing  infosec  insults  interesting  internals  into  ipa  ivacheung  java  javascript  js  jvm  kafka  kernel  kinesis  label:try_out  law  library  linux  lock  logs  lowlevel  mach  mapping  mask  mastodon  mechanics  memory  microcontrollers  misfeatures  motion  motionsmoothing  mtls  names  naziapologists  new  newsletter  nmsanchez  node.js  node  nodejs  numpy  occultcommunity  openscad  optimization  oracle  osdev  pagancommunity  parallel-computing  parallel  parameters  perf  performance  phishing  phonetics  politics  pool  proc.sys  proc  process  processes  processing  procfs  procs  profiling  programming  promise  pronunciation  protothreads  ps  puma  python  queue  racism  racket  rails  ram  rants  raster  reddit  reference  repository  ruby  rust  s2n  sample  saw  says  scheduler  scheduling  science  scottish  search  security  seekerbeware  shapefile  sheffield  smoothing  soda  software-development  spiders  ssl  stack  stacktrace  stancarey  startups  steam  storage  streaming  switching  synapsids  tags  task  terribad  tgm  thediscource  thefrosts  theory  thread-pools  thread.dumps  thread  threaddump  threading  title  tkinter  tls  tma  tool  top  toshare  transformations  trie  trump  tuning  tutorial  tvaziri  twitter  ubd  unicorn  ursnif  vector  vines  vs  walkthroughs  warp  webassembly  webs  wheaton  wifi  wilwheaton  women  work  writing  wtf 

Copy this bookmark: