VirtualTam's bookmarks
23 bookmarks found
-
Test feed:
- feed reader score project
- A sysadmin's rant about feed readers and crawlers
- Feeds, updates, 200s, 304s, and now 429s
- So many feed readers, so many bizarre behaviors
- The feed reader score service is now online
RFCs:
- RFC 1945 - Hypertext Transfer Protocol - HTTP/1.0 - If-Modified-Since
- RFC 7232 - Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests - Entity Tag (ETag)
- RFC 9110 - HTTP Semantics
Related:
- Bret Simmons - NetNewsWire and Conditional GET Issues
- John Brayton - Feed Polling for Unread Cloud
- Jeff Kaufman - Looking at RSS User-Agents
- Chris Siebenmann - The case of the very old If-Modified-Since HTTP header
- ETag and HTTP caching
- HTTP Conditional Requests Explained
- Caching - What takes precedence: the ETag or Last-Modified HTTP header?
-
NullDeref | Writing A Plugin System in Rust
2024-10-23 - The Technologies - A more in-depth look at Rust plugin systems
- Getting Started - First steps trying to implement the plugin system
- Diving into Dynamic Loading - A closer look at dynamic loading in Rust
- Reducing the Pain with Dependencies - Taking a look at the state of dynamic loading in the Rust ecosystem
- Getting our Hands Dirty - Finally implementing the plugin system!
- Wrapping Up - The last finishing touches and ideas
-
- Mathematics Meta Stack Exchange - Why do people use blackboard bold here and elsewhere in print?
- LaTeX Stack Exchange - Looking for a blackboard bold (\mathbb) math font that is thicker than Latin Modern or Computer Modern
- The LaTeX Font Catalogue - Fonts with math support
- CTAN - bbold – Sans serif blackboard bold
- CTAN - amsfonts – TeX fonts from the American Mathematical Society
-
Home Assistant Config - War Safety
2024-05-29 This is what war in the 21st century looks like: you can practically monitor a missile or a drone that is trying to kill you right from your phone. This is like a Black Mirror episode in real life.
-
- Blocking TCP port 53 traffic leads to very strange failures. Don't.
- The source you're looking at is not the code running in production.
- "Prod" is just another name for "staging".
-
EHX Bass MicroSynth
2018-11-24 - https://www.talkbass.com/threads/post-your-ehx-bass-micro-synthesizer-settings.298804/
- https://www.talkbass.com/threads/post-your-ehx-bass-micro-synthesizer-settings.298804/page-2
- https://www.talkbass.com/threads/post-your-ehx-bass-micro-synthesizer-settings.298804/page-3
- https://www.talkbass.com/threads/im-looking-for-a-certain-synth-bass-sound.861603/
- https://www.ehx.com/blog/ed-friedland-bass-micro-synthesizer-and-bass-blogger-reviews
-
History of the Drum Kit
2018-05-28 - https://en.wikipedia.org/wiki/Drum_kit
- https://culturalhistoryofthedrumset.wordpress.com/
- http://marcdedouvan.com/en/modern_drumset_history.php
- http://nationaljazzworkshop.org/freematerials/fidyk/Steve_Fidyk_History_Drum_Set.pdf
- https://www.moderndrummer.com/article/january-2013-the-evolution-of-the-drumset/
- https://www.moderndrummer.com/article/january-2016-40-years-of-innovation-a-look-at-drum-gear-then-and-now/
- https://scholars.unh.edu/cgi/viewcontent.cgi?article=1211&context=honors
Georges Paczynski - Rythme et Geste:
Nolan Pettersen - 150 Years of Drum Set Evolution in 40 Minutes:
-
Tokenizer - Lexer - Parser
2017-09-18 - https://stackoverflow.com/questions/380455/looking-for-a-clear-definition-of-what-a-tokenizer-parser-and-lexers-are
- https://stackoverflow.com/questions/2842809/lexers-vs-parsers
- https://en.wikipedia.org/wiki/Compilers:_Principles,_Techniques,_and_Tools
- https://meta.stackexchange.com/questions/25840/can-we-stop-recommending-the-dragon-book-please
- https://www.cs.princeton.edu/~appel/modern/
- https://www.amazon.com/dp/155860698X/?tag=stackoverfl08-20
-
Postfix / Dovecot / ClamAV / Spamassassin
2016-12-12 A whole buncha' links with contradictory information on how to properly set up a mail server ;-)
Disclaimer - My primary goal is to add proper Spamassassin (SA) filtering to an existing Postfix / Dovecot / roundcube installation, i.e.:
- use SA as a milter (mail filter) to attribute a spam score to incoming mail
- keep SA up-to-date
- train SA with spam/ham from the users' virtual mailboxes
- train SA according to user decisions (actual user or trained mail client with automatic/trained spam detection)
Here we go!
Most useful links; I stumbled upon them as soon as I knew what to look for:
- https://workaround.org/ispmail/jessie/spamassassin
- https://lelutin.ca/posts/installing_postfix_-_clamav_-_spamassassin_-_dovecot_-_postfixadmin_on_debian_squeeze/
Official:
- https://spamassassin.apache.org
- https://spamassassin.apache.org/gtube/
- https://wiki.apache.org/spamassassin/FrequentlyAskedQuestions
Debian:
- https://wiki.debian.org/DebianSpamAssassin
- http://www.stefan-seelmann.de/wiki/mailserver-postfix-dovecot (wheezy)
- https://www.christianroessler.net/tech/2015/spamassassin-dovecot-postfix.html
- https://www.digitalocean.com/community/tutorials/how-to-configure-a-mail-server-using-postfix-dovecot-mysql-and-spamassassin
CentOS:
- https://www.rosehosting.com/blog/how-to-install-and-integrate-spamassassin-with-postfix-on-a-centos-6-vps/
- https://www.rosehosting.com/blog/how-to-set-up-server-side-email-filtering-with-dovecot-sieve-and-roundcube-on-a-centos-6-vps/
- http://shisaa.jp/postset/mailserver-1.html - a bit outdated but plenty of useful information regarding how components interact with each other
- http://wiki2.dovecot.org/HowTo
RHEL:
- https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Mail_Servers.html
- https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/s1-email-mta.html
- https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/s1-email-mda.html
-
Worst. Gift. Ever. - Fowl Language Comics
2016-09-19 "Any way you look at it, a drum solo is a shitty gift for a newborn!"
-
Python unit testing frameworks: Nose, Pytest
2015-02-13 Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)
I'm currently looking for more dev-friendly solutions, the key points being:
- writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
- parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
- complete feature set!
- we don't want to just run tests...
- coverage reports (find dead/weak/untested code sections)
- output formatting (JUnit-XML seems to be quite a common format out there)
There seem to be 3 solutions in Python:
- stock unittest + project-dependent customizations / test helpers
- nosetests
- py.test
And 2 ways of gettings things done:
- keeping things stock: no external dependency, project-specific implementation...
- using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)
Some links:
-
Framadate
2014-11-29 Studs => OpenSondage => Framadate
A doodle-like event scheduler.
Though it seemed a bit crippled when I attempted to fork it early '14, it looks like it has gained in maturity, thanks to Framasoft's efforts ;-)
-
KDE Look | Ember theme
2014-11-04 -
Shaarli - AlbinoMouse
2014-10-08 Good-looking Shaarli fork ;-)