Avatar
vincenzzo
7e68f253dfe2f7937a40df76ac7ebae59966c6067fc70372d4aae995892b7432
When you look around and all you see is darkness - perhaps you are the light.

The drop off will catch up as the day unfolds I guess but seems a slow growth upward over last 6 months

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshsqgzwhzp3p445ak2ud4n289dn6084txu9ltkg7a53mt75qk5jup2ad5zhv5js - I wonder if you have some wisdom for an aquiantance of mine...

He used to work for security for Microsoft. Not exactly sure in what security field specifically.

He wants to go freelance in security space and travel.

Any advice to get security work for someone like this?

@asknostr @security #microsoft #freelance // Scheduled post from Nostr Growth Client

A good mother nurtures and raises you but has the wisdom not to smother and boot you out to let the world mould you as it will. Good mother:)

very interesting... I remember Jordan Petersen saying something similar. Any sources to learn more for me and others?

Id recommend spending some time thinking about real world scenarios as well...

eg https://www.freecodecamp.org/news/how-to-use-git-and-github-in-a-team-like-a-pro/

Also,

- If you fuck up a Git repository its one of the worst things to go through as a dev learning GIT in my experience. Its so annoying.

- Go slow, understand the commands you are using and if its really important (client work for eg) and you aren't sure make a quick copy. Even though that contradicts the reason why you'd use GIT in the first place! I did it while I was learning Git and it saved me some time.

- I found using Git on command line to be useful in the beginning but moving to a program is popular even though I still like using the command line tbh.

Happy coding:)

agreed... it is hard though... such is being a human

Lex is likely a psyop imo. See his involvement with Effective Alturism and MaCaskill who is was also mentor of SBF. Podcasting got popular so they found Jujitsu guy from MIT and got him to make a podcast. Whitney Webb has more info on MaCaskill and Effective Alturism. Beware. I was fooled for a few years before I realised.

#psyop

Disconnecting from Tor fixed it thank you... so vant use Tor?

So weird to see... head fake or legit she being told to lighten up on BTC.? Blackrock owning is a big diff politically.

What happens to Nostr in the bull run? More users who come for Zaps? Less for some reason?

#asknostr #nostr // Scheduled post from Nostr Growth Client

What's wrong with my Amethyst? Can't connect to anything or see notes....

#amethyst #asknostr

Can't connect to Relays or see notes. Nada. I reinstalled. Readded all the Relays. Nada.

// Scheduled post from Nostr Growth Client

Nostr is a giant shit show. The fact that our software interoperates at all is a miracle and probably just a temporary anomaly. Given enough time, the relentless breaking changes being made to published NIPs will eventually break everything.

Linux succeeded because "WE DO NOT BREAK USERSPACE". For nostr to succeed, changes must "NOT BREAK EXISTING IMPLEMENTATIONS". There shouldn't be any exceptions to that EVEN IF THE IMPLEMENTATION WAS NON-COMPLIANT.

Pay close attention to Linus right here:

> Are you saying that pulseaudio is entering on some weird loop if the

> returned value is not -EINVAL? That seems a bug at pulseaudio.

Mauro, SHUT THE FUCK UP!

It's a bug alright - in the kernel. How long have you been a

maintainer? And you *still* haven't learnt the first rule of kernel

maintenance?

If a change results in user programs breaking, it's a bug in the

kernel. We never EVER blame the user programs. How hard can this be to

understand?

Linus doesn't want to break pulseaudio EVEN THOUGH pulseaudio was doing the wrong thing.

It seems like every week I find a NIP that I've coded for has changed. This last week I think it happened three times already. Sometimes it's a small change and I quickly update my code. But I can't read all the PRs, and I'm afraid dozens of small changes have slipped past my notice. Gossip is probably now incompatible with multiple other implementations which happen to have implemented different versions of the same NIPs (some older, some newer).

Even if we didn't have any breaking changes, the simple fact that different software implements different optional NIPs itself presents to end users like broken software. Why does it work in Damus but not Amethyst? Why does it work in Amethyst but not Coracle? That is an even harder problem to solve.

But let's at least solve the easier problem and stop changing NIPs. If you don't like a NIP make a new one, don't break the current one. Even if you think the current one sucks balls and should have never happened. Even if you think there aren't many implementations out there.

Is this why my #amethyst stopped working for no good reason?

Feel free to shout out if you want some imput