The one on the bluetooth headphone vulnerabilities was quite fun: https://media.ccc.de/v/39c3-bluetooth-headphone-jacking-a-ke...
I have a Fossil Neutra Smartwatch. On the upside it is a decent watch, that I can wear in any context. On the downside the display is really bad and won't actually display anything at this point anymore, the watch is…
Seems like the hug of death already reached the site. It returns a "Error establishing a database connection" message right now.
Having multiple TTLs in the same record set is deprecated. [1] If you would rather put them in your cache, instead of not allowing to request them through your server, you are probably best off, by taking the lower TTL…
Especially when you look at the category this has been posted to > youre-going-to-wish-you-killed-me Yeah that seems totally reasonable.
Interesting project! Thanks for sharing. How does this compare to other community efforts, e.g. Zalandos Patroni project, aside from supporting more databases than just postgres?
The one on the bluetooth headphone vulnerabilities was quite fun: https://media.ccc.de/v/39c3-bluetooth-headphone-jacking-a-ke...
I have a Fossil Neutra Smartwatch. On the upside it is a decent watch, that I can wear in any context. On the downside the display is really bad and won't actually display anything at this point anymore, the watch is…
Seems like the hug of death already reached the site. It returns a "Error establishing a database connection" message right now.
Having multiple TTLs in the same record set is deprecated. [1] If you would rather put them in your cache, instead of not allowing to request them through your server, you are probably best off, by taking the lower TTL…
Especially when you look at the category this has been posted to > youre-going-to-wish-you-killed-me Yeah that seems totally reasonable.
Interesting project! Thanks for sharing. How does this compare to other community efforts, e.g. Zalandos Patroni project, aside from supporting more databases than just postgres?