- Fix UnBet
- Test Gametime management
- Errors management with
- Settings
- First public release
- Show Scores on Livesplit, replacing the splits with the scores for a few seconds (crazy idea, don't know if possible)
// Just before switching jobs: | |
// Add one of these. | |
// Preferably into the same commit where you do a large merge. | |
// | |
// This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
// and then it quickly escalated into more and more evil suggestions. | |
// I've tried to capture interesting suggestions here. | |
// | |
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
@if [%6]==[] goto error | |
@goto ok | |
:error | |
@echo USAGE: video2gif START_TIME DURATION WIDTH FRAME_RATE (DITHER_OPTIONS) (CROP_RECTANGLE width:height:x:y) INPUT OUTPUT | |
@goto end | |
:ok | |
@set PALETTE="%TEMP%\palette.png" |
www.iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea.com
is up the virus exits instead of infecting the host. (source: malwarebytes). This domain has been sinkholed, stopping the spread of the worm. Will not work if proxied (source).update: A minor variant of the viru
If Rotonde were to switch to WebDB and to Beaker's format, wouldn't that 1. restrict Rotonde to Beaker's format; 2. force services to run in Beaker (cutting already working tools off the network)? I welcome Ingest, but... letting the browser dictate where and how social networks should store their data sounds wrong IMO.
I agree.
Regarding the tooling working outside the browser, you can use ingest directly in node, and we even have a neatly-packaged module for that: https://github.com/beakerbrowser/beaker-profiles-api (it's a little out of date compared to the spec but it'll be kept up to date -- it's what we use inside beaker). So, that shouldn't be a concern.
Rotonde doesn't have to use WebDB. We want yall to use Ingest or the files API directly if you're not interested in WebDB's schemas. The idea with WebDB is to reduce the learning curve and do some things which are otherwise hard to do right now: giving fine-grained permissions, sharing data between apps, enforcing compatibility, and so on. Web