Avatar
Thorwegian πŸ‡³πŸ‡΄
c708943ea349519dcf56b2a5c138fd9ed064ad65ddecae6394eabd87a62f1770
1983 vintage. Lives in Oslo, Norway. Interested in tech, cooking, history, music, art and travel.

i've got the brains to make a client that Just Works(TM) but i'm feeling a bit lazy. it's a big job. i want money and sex in return. i don't think that'll be happening.

tfw you wake up every morning and you wonder if the world is just an elaborate hoax

on some days i'm thinking y'all just NPCs

i have a few dollars after some pretty intensive posting. didn't do it for the dollars but they came in. i regard the zaps as symbolic for the most part. they won't help pay rent. you still gotta work for the man for that.

i think what you've got on Nostr and maybe much of the Bitcoin ecosystem is about 1% who got a lot of money and they ain't giving, and then you've got the remaining 99% who can't afford to part with much. as usual.

it doesn't currently collect data on anything that the users actually do (posts, likes, reposts, zaps) but i've been thinking about maybe at least cumulating figures on those things. i don't want to keep a copy of all of Nostr.

help, i uploaded a long image to iris.to and now i can't scroll to continue typing the post. #[0]

i think relay.current.fyi might be a shit relay. the moment i added it, this happened...

why am i suspecting that something was lost in translation here...

it's both frustrating and funny that i need to use 2-3 different clients to have a good Nostr experience. iris.to, snort.social and Damus added together manage to do what i need, but just using one would drive me crazy.

*shakes fist* don't make me come out here and code a better client

can we track down and kill the guy behind the cyber cat bot?

i think snort.social's image server has some kind of origin policy on it, because when i repost stuff to Mastodon via mostr.pub, those images refuse to load.

global feed is now being spammed up by the cyber-cat bot i complained about earlier. #[0] you have to do something about this for filter.nostr.wine. as far as i can see, it's the *only* bot that is causing trouble. i'm actually tempted to add specific code to my crawler just to get rid of that one bot...