sam152

To make matters worse for Drupal security records, the vulnerability is being actively exploited hours after the patch was released by the Drupal core team.

This is true for Drupal 7, but not for Drupal 8. Nothing in wild has surfaced regarding SA-CORE-2018-004 for D8 yet.

I started looking at trying to write an implementation of the protocol documented here: https://ssbc.github.io/scuttlebutt-protocol-guide/. I was surprised just how little information exists on the handshake and message exchange protocols. The reference implementations of both seem quite immature.

Was there no existing protocol for sending P2P messages between clients this could have been built on top of?

Further to that point they can take as long as they like to render a single frame.

Why did you decide to use a custom video player and not an established service like YouTube or Vimeo? I think a lot of people forget how much time these services spend optimising their video players and delivery. Plus, these services are another avenue of content discovery.

Can't see any reasons against using one of these services.

Sounds like an interesting concept. Few thoughts:

- You would need a large user base to get enough momentum for all of the voting and rounds.

- Wouldn't the user-voted platform have the potential to produce a candidate that appealed to an individual equally or even less than existing candidates?

- I don't know if this is the kind of thing which people would put money into on Kickstarter.

Would be interested to hear other peoples thoughts.

Seems like a lot of extra work rather than just clicking a checkbox.

Great project. For anyone interested in serving up static resources seamlessly, you can use something like the following in an Apache config:

  <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{HTTP_USER_AGENT} !^CoralWebPrx
    RewriteRule "\.(png|jpg|css|js)$" http://%{HTTP_HOST}.nyud.net%{REQUEST_URI} [L]
  </IfModule>

I had a play and it seems really neat, congratulations. I ran "watch -n0.2 cleaver presentation.md" to preview changes, but there is probably a better way to do it with some sort of filesystem watcher.

Looks a lot to me like a rebranded Ducky Shine (http://www.tankguys.com/media/catalog/product/cache/1/image/...).

This is really neat. I have added it to alias.sh for easy inclusion: http://alias.sh/filesystem-markers-jump

Since their stored in '~/.lolcommits', I don't think this could really impact any production projects. I think it could be pretty funny, especially for non-side projects.

Speed is definitely a huge benefit of git. When you use it heavily every day, you become thankful that cloning, merging, branching etc is very fast. If it were a couple of seconds slower for each of these tasks, I think it would make a big difference.

The desktop app is great. I was up and running on my mac in < 30 seconds. Definitely easier than the taking screenshot => photoshop => email workflow I've been rolling with.

While I am in favor of keeping things dead simple, is 6 character URLs too few? Could someone guess confidential work-related screenshots based on that size?

Also is hot-linking/embedding directly to the final image allowed or discouraged?

Can someone examine the cookies that they set and tell if there is any sensitive information (passwords?) that are hashed in there? Should we consider this a password breach?

Good catch, fixed.

This is a great site. I might post a few on alias.sh. A lot of them however are just cool commands you can run, not commands that are packaged into an alias.