venatiodecorus

/* HTML5 ✰ Boilerplate
 * ==|== normalize ==========================================================
 */

article, aside, details, figcaption, figure, footer, header, hgroup, nav, section { display: block; }
audio, canvas, video { display: inline-block; *display: inline; *zoom: 1; }
audio:not([controls]) { display: none; }
[hidden] { display: none; }

html { font-size: 100%; -webkit-text-size-adjust: 100%; -ms-text-size-adjust: 100%; }

venatiodecorus

Keybase proof

I hereby claim:

• I am venatiodecorus on github.
• I am venatiodecorus (https://keybase.io/venatiodecorus) on keybase.
• I have a public key ASBHvpyOlNbjKSNuqCdjoSEQDa9cLG7sUM7REjJaBLLmugo

To claim this, I am signing this object:

venatiodecorus

Running your own encrypted chat service with Matrix and Riot

Workshop Instructor:

• Lilly Ryan @attacus_au

This workshop is distributed under a CC BY-SA 4.0 license.

What are we doing here?

The goal of this workshop is to teach you how to configure and run your own Matrix/Riot service. By the end of the workshop, you should be able to log into secure chat rooms and invite others to the same server.

venatiodecorus

#!/usr/bin/perl


######
# hueg.pl PRO MODE
# modded by ma0 and others
# respekts 2 jakk and others
######
use Irssi;
use vars qw($VERSION %IRSSI);

venatiodecorus

You need at least WeeChat 3.1-dev

Enable mouse

/mouse enable

venatiodecorus

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

package.json

venatiodecorus

Yes, using a file with JSON objects representing both success and error cases from a third-party API, and then mocking `fetch` to return these responses in your tests, is a sensible and common testing pattern. This approach has several advantages:

1. **Realistic Test Data**: By using actual response data from the API, your tests can more accurately simulate real-world scenarios.

2. **Consistency**: Having predefined JSON responses ensures that your tests are consistent and repeatable, as they don't rely on live API data which might change.

3. **Offline Testing**: Mocking responses allows you to run tests without needing an active network connection or access to the third-party API.

4. **Rate Limiting and Costs**: It avoids issues related to rate limiting or costs associated with making frequent API calls during testing.