Maybe a small piece of personalised luggage for the holiday. Does she wear makeup? Maybe a nice makeup case with her initials on it.
If that’s not her thing, what about something for your home (assuming you live together)? My wife and I tend to buy ourselves the “bigger” things for Christmas, as our gift to each other - some furniture we’ve been wanting, or similar.
If that doesn’t sounds like you guys, there’s the tried and true jewelry option. Or maybe just cruise Etsy for the sorts of things she likes (does she like knick knacks, or ornamental stuff?) that might be customisable.
Failing that, have a think about what makes you special as a couple. Is there a shared interest or experience that got you together or you always talk about? Is there something in that?
Finally, I’ve been holding on to some ideas for future inspiration should I need them:
- Waveform art: record yourself saying you love her, have the waveform turned into a print, or a piece of jewelry, or similar
- Anamorphic art: a skewed picture that reveals itself when a specifically shaped mirror is put behind it
- A glass lamp base filled with something meaningful: I always thought of filling one with origami love hearts
- Ambigrams: maybe you can figure out an ambigram with both your names, and have it made into something - a print or a wood carving (this will probably take a lot longer than the time you have before Christmas)
- Birth stones, star signs, birth flowers, birth fruit: admittedly these are probably better suited to birthdays
Hmmm - interesting. I hadn’t bothered to check before now, but I’m seeing something similar on one of the two PBS CTs I run.
Comparing the output of
netstat -lantop
on both CTs, I can see that the one with more outbound traffic has more waiting connections from localhost on port 82, the port Proxmox Backup Servers provides its API over:tcp 0 0 127.0.0.1:51562 127.0.0.1:82 TIME_WAIT - timewait (40.38/0/0) tcp 0 0 127.0.0.1:56342 127.0.0.1:82 TIME_WAIT - timewait (29.92/0/0) tcp 0 0 127.0.0.1:44864 127.0.0.1:82 TIME_WAIT - timewait (58.94/0/0) tcp 0 0 127.0.0.1:45028 127.0.0.1:82 TIME_WAIT - timewait (11.88/0/0) tcp 0 0 127.0.0.1:44026 127.0.0.1:82 TIME_WAIT - timewait (48.66/0/0) tcp 0 0 127.0.0.1:44852 127.0.0.1:82 TIME_WAIT - timewait (58.80/0/0) tcp 0 0 127.0.0.1:59620 127.0.0.1:82 TIME_WAIT - timewait (0.00/0/0) tcp 0 0 127.0.0.1:56374 127.0.0.1:82 TIME_WAIT - timewait (30.98/0/0) tcp 0 0 127.0.0.1:51544 127.0.0.1:82 TIME_WAIT - timewait (39.98/0/0) tcp 0 0 127.0.0.1:59642 127.0.0.1:82 TIME_WAIT - timewait (0.00/0/0) tcp 0 0 127.0.0.1:45008 127.0.0.1:82 TIME_WAIT - timewait (10.92/0/0) tcp 0 0 127.0.0.1:45016 127.0.0.1:82 TIME_WAIT - timewait (11.76/0/0)
I’m wondering if the graph is pulling aggregated network data, including the loopback interface. If so, and it’s all just port 82 stuff on 127.0.0.1, then it’s probably nothing to worry about.
Edit: found this forum post that seems to indicate it’s aggregating all the byte values from
/proc/dev/net
, so this is probably nothing to worry about if yournetstat
output, like mine, only shows API conections to/from 127.0.0.1 on port 82.