This document discusses the common strategy of Indico for filtering objects from the DB. We can either go:
- Implicit
- Explicit
Ferhat came up with a helper+decorator to standardize the way we filter objects:
@staticmethod
@utils.filtered
# Blindstore | |
> ![](http://i.imgur.com/Yj5qUjm.png) | |
> | |
> Blindstore is the first stone for a secure communication protocol. | |
## Motivation | |
Snowden's leaks last year disclosed the fragile condition of the privacy on the Internet, having been threatened not only by private companies but also by governments' intelligence agencies. | |
Since then, quite a few developments have been done in order to mitigate the eavesdropping of private communications. I'd like to talk breafly about two services: Lavabit and Protonmail. |
{ | |
"folders": | |
[ | |
{ | |
"path": "indico/src", | |
"file_exclude_patterns": ["*.min.js", | |
"*.min.css", | |
"lib/*", | |
"src/ext_modules/*/*", | |
"src/indico/htdocs/js/ckeditor/lang/*", |
// Use Gists to store code you would like to remember later on | |
console.log(window); // log the "window" object to the console |
#Indico client-side MVC It's time to go full MVC in Indico!
We all want our architecture to be simple, yet beautiful.
When developing applications using just jQuery, the piece missing is a way to structure and organize your code. It’s very easy to create a JavaScript app that ends up a tangled mess of jQuery selectors and callbacks, all desperately trying to keep data in sync between the HTML for your UI, the logic in your JavaScript, and calls to your API for data.
A number of modern JavaScript frameworks provide developers an easy path to organizing their code using variations of a pattern known as MVC (Model-View-Controller). MVC separates the concerns in an application into three parts:
function GinkgoGames::SinglePlayerLevel::onQuit() { | |
// Achievement check begins | |
rbx = *(rdi + 0x70); // rbx = ID of current scenario | |
rax = GIN::Symbolize("sp_forst_destructor"); // rax = representation of scenario "sp_forst_destructor" | |
if (rbx == rax) { // check if we are in scenario "sp_forst_destructor" | |
rax = GIN::Node::getPropertyValue( | |
GIN::Node::find(GIN::Symbolize("destructionDirector")), // destructionDirector is the unavoidable mechanism | |
"Capacitor", // that starts once all 8 shards are plugged in | |
"killCounter", | |
"charge", |
<head> | |
<title>502 Bad Gateway</title> | |
</head> | |
<body> | |
<body bgcolor="white"> | |
<center><h1>502 Bad Gateway</h1></center> | |
<hr><center>nginx</center> | |
<script> | |
function tryRefresh() { | |
var xhr = new XMLHttpRequest(); |
I hereby claim:
To claim this, I am signing this object:
# Solves: | |
# error: Couldn't set refs/heads/branchName | |
# To X:xxx.git | |
# ! [remote rejected] branchName -> branchName (failed to write) | |
# error: failed to push some refs to 'X:xxx.git' | |
git fsck --unreachable | |
git reflog expire --expire=0 --all | |
git repack -a -d -l | |
git prune |
Wire doesn't support exporting chat history (wireapp/wire#116). It is, however, possible to access the decrypted messages in the local storage of a browser. This guide will help you produce a text export once you are logged in https://app.wire.com. All from the browser console.
Open a connection to your browser local storage:
var db
var request = indexedDB.open("wire@production@4278eafb-b21c-4d7a-aad4-2be4fa3a9fa0@permanent")
request.onerror = function(event) {
console.log("Why didn't you allow my web app to use IndexedDB?!")
}