https://code-boxx.com/php-live-chat-websocket/
composer require cboden/ratchet.1-chat-server.php in the command line.2a-chat-client.html in the web browser.Copyright by Code Boxx
The database can make use of a more expressive type system. Specifically to enforce invariants on data integrity at the schema level. But also understanding databases from a type theoretic point of view can lead to better, safer and more expressive type systems.
You do not want to keep writing database validation code in your application boundary. That is tiring. Instead let your database do that work. After all, it is where the data is stored. It is where the data is migrated. So shouldn't it also maintain the integrity and the constraints of the data?
| //============================================================================================================================== | |
| // An optimized AMD FSR's EASU implementation for Mobiles | |
| // Based on https://github.com/GPUOpen-Effects/FidelityFX-FSR/blob/master/ffx-fsr/ffx_fsr1.h | |
| // Details can be found: https://atyuwen.github.io/posts/optimizing-fsr/ | |
| // Distributed under the MIT License. Copyright (c) 2021 atyuwen. | |
| // -- FsrEasuSampleH should be implemented by calling shader, like following: | |
| // AH3 FsrEasuSampleH(AF2 p) { return MyTex.SampleLevel(LinearSampler, p, 0).xyz; } | |
| //============================================================================================================================== | |
| void FsrEasuL( | |
| out AH3 pix, |
Ever since I wrote It's Time For Furries to Stop Using Telegram, I've had a few folks ask me about my opinion on Matrix.
(I've also had a few people evangelize Matrix in my mentions. That's annoying.)
My stance on Matrix has been the same for years: I don't trust the Matrix developers to produce a secure protocol, and until they abandon Olm / Megolm in favor of something like MLS, I'm adamant about refusing to trust their team's designs.
To understand why I feel so strongly about this, you need to understand that practically exploitable vulnerabilities were found in Matrix in 2022.
It isn't enough that there were vulnerabilities found to be alarming. Vulnerabilities happen. You aren't writing software if you don't occasionally fuck up.
| import_if_available(Ecto.Query) | |
| # alias MyApp.Repo | |
| defmodule R do | |
| # Old habits die hard. Take a random of something. You don't care which. | |
| # > R.take(SomeSchema) | |
| def take(schema_or_query) do | |
| schema_or_query | |
| |> limit(1) | |
| |> Repo.one() |
| # Split a repository into batches to avoid `pack exceeds maximum allowed size` on git push | |
| REMOTE=origin | |
| BRANCH=$(git rev-parse --abbrev-ref HEAD) | |
| BATCH_SIZE=500 | |
| # check if the branch exists on the remote | |
| if git show-ref --quiet --verify refs/remotes/$REMOTE/$BRANCH; then | |
| # if so, only push the commits that are not on the remote already | |
| range=$REMOTE/$BRANCH..HEAD |
| /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --app="http://www.google.de" |
