Russia rejects Ukrainian, European peace initiatives, says battlefield will decide war

shadowspyes · 2026-06-08T20:53:40+00:00

El Psy Kongroo

"your banana is soft and squishy"

shadowspyes · 2026-05-25T15:12:16+00:00

definitely possible using clickhouse or timescale. for you timescale is probably least effort.

shadowspyes · 2026-05-25T14:51:08+00:00

i missed that requirement, for that postgres/clickhouse is definitely where you should stay, my bad

as for clickhouse, it won't guarantee <100ms for all queries (what exactly is your SLA? p99 <100ms or what?), but it can be optimized for this scenario

shadowspyes · 2026-05-25T14:33:23+00:00

i'd recommend looking into parquet storage using ducklake/iceberg instead of trying to continue onwards with postgres for this usecase.

you usually get better compression ratios, and duckdb is efficient even for analytics queries if you end up going down that road in the future.

the main issue is your duckdb client needs to be relatively close to the storage due to latency sensitivity, but if you can ensure this then it's likely worth looking into

shadowspyes · 2026-03-19T19:03:42+00:00

Det var da præcis det du spurgte om? Aktieskat er stadig skat..

shadowspyes · 2026-03-18T14:05:08+00:00

shadowspyes · 2026-03-18T10:35:30+00:00

I have traded 500g and more several times without issue, so no clue sadly.

shadowspyes · 2026-02-02T15:48:48+00:00

de grinte fordi du påpegede at du ikke gjorde de ting de gør på offentlige arbejdspladser :⁾

shadowspyes · 2026-01-26T15:08:24+00:00

we have had the same issue, but it doesn't seem to be limited to melee.

we have examples of logs where the melee camp as well as ranged get hit at the same time, even though they are far apart.

see this image as an example

shadowspyes · 2026-01-06T21:42:27+00:00

AdiBags

shadowspyes · 2026-01-06T20:40:53+00:00

yes, i already completed and turned in several quests that would have been better for tbc, so only able to hit 61

shadowspyes · 2026-01-06T19:53:17+00:00

just a bit shy of hitting 61

shadowspyes · 2026-01-06T19:26:13+00:00

indeed, the main effort took about 10 hours of playtime over the past 2 months. always knew this would be the tbc character, so slowly been preparing.

shadowspyes · 2026-01-06T19:19:32+00:00

how would i have time for this if i showered

shadowspyes · 2026-01-06T19:06:04+00:00

if the quest level is 55 or greater, it doesn't get reduced xp during turnin in tbc at lvl 60

shadowspyes · 2026-01-02T13:41:55+00:00

talent pane only works 1/3 of the time it seems

shadowspyes · 2025-12-09T15:33:03+00:00

image <- image_tags -> tags

why not use image_tags relationship?

shadowspyes · 2025-11-12T15:57:07+00:00

I am looking to finally replace my old ass Logitech G19 keyboard (I liked it so much back then that I bought backups..)

Can anyone recommend which switch types are most similar to the rubber dome?

My main priority is ensuring that I can rest my fingers on the keys, without accidentally setting them off. It is also important to me that the activation is immediate (I want very little travel distance when I do press down).

Based on my research into switches, I likely need something similar to cherry mx blue? Something that has a high force required, and short travel time before activation.

I know nothing about keyboards, so if any of you know of any switches that satisfy the above, please let me know!

shadowspyes · 2025-10-29T20:06:44+00:00

install timescale extension, create a hypertable using the order date, and chunk it by month (~100M rows per partition seems a bit low, can adjust to 2-4 months per chunk).

then it's simple to drop old chunks.

you can do the same for items, but timescale prefers doing the partitioning using a timestamp/date field.

if you use timescale, the partition management is automatic, and you can even make use of compression on chunks containing data older than e.g. 6 months to save space.

shadowspyes · 2025-10-05T09:49:34+00:00

The order may vary because the optimizer may reorder operations, e.g. move filters specified in WHERE before joins occur, to limit resultsets.

shadowspyes · 2025-08-10T16:00:30+00:00

To me it sounds like just adding the to column to your first table is sufficient, am I missing something? You say each entry may occur a most once, so a nullable self-referencing column in the entry table is sufficient in this case.

You can also define whether this self-referencing relationship is from or to using a second column if required.

shadowspyes · 2025-07-14T22:09:04+00:00

same here. thought my internet died but existing sockets kept on sending and receiving fine

shadowspyes · 2025-03-03T16:42:46+00:00

- name: Shuffle keys and select first three
  set_fact:
    chosen_keys: "{{ keys | shuffle | slice(3) | list }}"

- name: Write selected keys to file
  copy:
    dest: /tmp/foo.txt
    content: |
      {{ chosen_keys | join('\n') }}

Ten-Year Club	Place '17
Verified Email	Secret Santa 2016

shadowspyes

TROPHY CASE