Paul's latest activity

I'm launching a new Monthly Mailing List for MailPace, Awesome Email, filled with developer-focused content on email, as well as the latest mailpace product updates, sign up here: buttondown.email/mailpace/

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

I'm launching a new Monthly Mailing List for MailPace, Awesome Email, filled with developer-focused content on email, as well as the latest mailpace product updates, sign up here: buttondown.email/mailpace/

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

Just updated our templates to v2, github.com/mailpace/templates with Tailwind 3 and Maizzle 4!

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

Made some updates to the mailpace landing page mailpace.com

Not strictly necessary, but it was fun creating a mini-terminal simulation!

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

Now I want to order by ascending ok: ORDER BY ASC great

Now let's order by descending because as always I mix them up

ORDER BY DSC

ERROR: syntax error at or near "DSC"

kill me now

it's DESC btw

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

What's wrong with this query?
SELECT * FROM table ORDER_BY updated_at LIMIT 10;

...

ORDER_BY should be ORDER BY - wtf SQL why

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

Just completed a rolling upgrade to Redis 7 on Production (with no downtime of course).

Anyone else get a terrible sinking feeling every time they make big changes in Production?

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

@Franky47 two reasons: spam/phishing emails (sometimes we have to look back if to moderate senders appropriately), and for users to check what was sent in the dashboard recently

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

@pdenya @Franky47 this morning I started to refactor to pass the config as a variable, and for some modules the pattern works well (if I have an initialiser/constructor function), but for others the entire module is expected to be initialised at run time. So to avoid adding an init function to those modules, I’ll probably leave some as imports.

I’ll open source this product in a few weeks, hopefully!

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

@Franky47 yes, this makes the most sense, thanks!!

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

In Typescript, what's the best way to load a config across multiple modules? Should you do this in every module that needs the config:

`import config from ''./config.js"`

OR should you import the config once and pass the config as a variable to any functions that need it? e.g.

```
import config from ''./config.js"
startServiceA(config);
startServiceB(config);
...
```

4
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

Do I have any followers who play chess? Looking for correspondence players over at lichess

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin

Our identities are too closely coupled to the medium (your handle exists on your server, your handle exists only on pixelfed etc.).

We should separate identity into one of two options, a DNS based identity (e.g. like email, and how mastodon lets us bring our own domain), or a pub/private key (ala nostr.com/). The identity should be portable between services and allow apps to aggregate content into one interface, kind of like how OpenID was supposed to be...

0
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Replies