SilberWitch

Well, it's a wiki, so almost everyone using it won't be logging in, as they're usually just reading.
What needs to be worked on is making the entries more visible to search machines like google. People will use it, if they think their entries will be read.

2024-05-23 20:53:27

- reply

okay. just sounds like a composite scanner.

2024-05-23 20:20:14

- reply

Just finished at revamp. Took weeks. 😬

2024-05-23 20:18:51

- reply

I do my best.

2024-05-23 13:35:44

- reply

Yeah, the guys think I too nice to be a convincing witch. 😂

2024-05-23 11:26:43

Check this out.
This is basically an uncurated list of kinds.
#note18wa…8k2h

2024-05-23 11:24:44

- reply

Oh, that's useful input, thanks! Bookmarked it.

2024-05-23 11:11:15

- reply

What do you mean?

2024-05-23 08:04:43

- reply

The numbers aren't assigned sequentially, so some are missing.
You can see the full list here:
https://wikifreedia.xyz/nip-event-register/dd664d5e4016433a8c

2024-05-23 08:00:19

- reply

I might start by adding some sort of status in my event register table.
Obsolete, deprecated, draft, final or something.

2024-05-23 07:58:37

💯
#note1pvx…3yer

2024-05-23 06:27:35

- reply

That worked! ☺️ Thank you!

2024-05-22 23:05:07

- reply

Ah, okay nice!
Looks like it would work well, to me.

2024-05-22 23:00:32

#Freerse does a nice job displaying the ngit events.

2024-05-22 22:58:27

- reply

Okay, cool.
Do you know how an end user could grab a wiki eventID for njump?

2024-05-22 21:26:14

- reply

@npub1wqf…qsyn

2024-05-22 09:22:22

- reply

I'm proposing this. Just remove the event kind list from the NIP repo and put it in a wiki page and basta.
https://wikifreedia.xyz/nip-event-register
#nevent1q…6vtq

2024-05-22 07:15:24

- reply

This is an attack nobody noticed and most people can't even see because they avoid crappy, spammy relays. 🤷‍♀️

2024-05-16 22:50:02

- reply

Holy moly. That turnaround time, tho. 👀

2024-05-16 21:01:04

I'm just going to create forks to GitHub repos I'm not a collaborator on, and use them as the feeder for my ngit proposals.

2024-05-16 17:14:18

- reply

Origin issue:
#nevent1q…v4gu

2024-05-16 16:51:54

I guess this PfP is way too sexy for this account. 😅 Oh well.
Everyone complained about the witchy handle, so I'm all angel-y now.

2024-05-16 16:47:37

- reply

Does he even use ngit? He hasn't responded to anything, so far.
Also, I'm thinking maintainers will usually be under gitignore, right? @npub15qy…yejr what do you think? Do you think maintainers should be under change control? Seems more like an input file for the public event.

2024-05-16 16:38:04

- reply

Better?

2024-05-16 16:08:47

- reply

😇

2024-05-16 16:04:27

- reply

If someone wants to pull this, it'll fix the relays used when you send a proposal.

2024-05-16 16:01:02

- reply

Ah, okay.

2024-05-16 15:58:20

- reply

Okay, I think this one should work.

2024-05-16 15:54:13

- reply

Yeah, I've never worked with any of this stuff before. Confusing.

2024-05-16 15:23:54

- reply

@npub1896…x5ge You removed the ".md" from "README.md" filename. That's why I can ngit pull, but I get an error.
I thought I was going nuts. 😅

2024-05-16 15:09:47

- reply

I deleted the repo and cloned again, and then tried ngit pull and it failed. Says the patch doesn't work.

2024-05-16 14:51:13

- reply

Four, including einundzwanzig.
https://image.nostr.build/05e1c43331bfccc20ac50a46182ad86b7ade58122bc04a5f8c48f9372897154d.jpg

2024-05-16 14:48:17

- reply

What workflow should I have used, as it's now a big mess?
Here's what I did
1) make a branch
2) commit to branch
3) ngit send
4) merge branch to master
5) ngit pull
6) 😭 nothing works

2024-05-16 14:44:10

- reply

I can't figure out how to pull the changes. I see
finding proposals...
✔ 3 events wss://relay.damus.io/
✘ error wss://relay.nostr.ai/ connection timeout
✔ 0 events wss://relay.snort.social/
✔ 0 events wss://nostr.einundzwanzig.space/ ? all proposals ›
Edited maintainers file
2024.05.16-10.17.43
Burning an npub
But when I try to do ngit pull, I get
finding proposal root event...
✔ 3 events wss://relay.damus.io/
✘ error wss://relay.nostr.ai/ connection timeout
✘ error wss://relay.snort.social/ connection timeout
✔ 0 events wss://nostr.einundzwanzig.space/
Error: cannot find a proposal root event associated with the checked out branch name
The branch is master.

2024-05-16 14:22:46

- reply

@npub15qy…yejr Why does it ask me for the naddr every time?

2024-05-16 13:57:38

- reply

Actually, I guess this is a solution for a problem that wouldn't exist, if we could "follow" repos or repo events, as we'd then see the changes in real-time, in any client, and we could have a newsfeed in the gitworkshop profile.

2024-05-16 13:51:40

- reply

No, on a separate branch. I've merged it to master locally, but not in the proposal.

2024-05-16 11:45:42

- reply

The fact that I'm tempted to believe it, just makes it funnier.

2024-05-16 10:56:24

- reply

Usually can't even see it, as it's in the gitignore.

2024-05-16 10:50:24

- reply

The problem is that lots of people who hang out in FOSS platforms think that government and politics don't matter because they're anon.
So, there is no will to fight, organize, politicize, etc. Everyone just goes deeper and deeper into hiding.
Other movements I've been involved in always went full-offense and created scenes in public, to make sure that the public realized that persecuting them would be a big PITA because it's like playing whack-a-mole with moles holding megaphones and marching downtown.

2024-05-16 10:44:44

- reply

Everything is an instant mute for you, tho. 😂

2024-05-16 10:42:18

- reply

Not on someone else's repo.

2024-05-16 08:56:31

- reply

I think a lot of your users are devs, we're moving our repos from GitHub to Nostr, and we're active npubs, so these events are going to be frequent.
Should at least display what sort of note it is.

2024-05-16 08:15:33

- reply

Jokes on us.
This is already the case. That's why cars are required to have speed limiters installed, they want to add mandatory intoxication-sensors, self-driving (with a backdoor), and remote-automobile identification over GPS.

2024-05-16 08:09:22

- reply

Ironically, we have Nostr to communicate over without censorship or KYC. 🤔
Looks like we might need it for ourselves.

2024-05-16 07:57:37

- reply

I have no problem with someone being nym. Allowing nyms to navigate the Internet effectively is part of why I'm here.
That said, I'm old-school enough to simply assume that doing anything new or radical might lead to getting arrested. It's a form low-key civil disobedience or protest, and carries inherent risk.
I'm actually sort okay with that. I've just accepted it.
The bigger issue for me is actually the draconian sentencing laws, that make writing code a bigger crime than rape or murder. Reminds me of the overzealous crack laws that were just thinly-disguised minority prosecution.

2024-05-16 07:48:36

- reply

This. 😂
How do you kill something that exists so long as one node survives?

2024-05-16 07:18:26

- reply

I like that. Might also make sense to allow redirection to a new npub only in case of retirement and to make the event-validation required higher on retirement, using the strategies defined in the other thread listed below.
Otherwise, someone could lock you out and your stuff gets deleted.

2024-05-16 06:45:43

- reply

They were discussing (in a separate dev hellthread) that we could add a layer of validation to a migration by using WoT and NIP-05, or even a linked key.
#nevent1q…rp8l

2024-05-16 06:38:16

- reply

Those are really cute! 😊

2024-05-15 21:54:36

- reply

😂

2024-05-15 21:49:26

- reply

Unfollowing would kind of counter the deescalation and they'd still be following you around in replies.

2024-05-15 20:04:11

- reply

it's sorta true

2024-05-15 20:03:47

How did this get in my follow list? 😂
https://image.nostr.build/0f39a789e55695e4634b9165f4f751ad0ce2bf36ab1129fca1ac2d9eccdc7b20.png

2024-05-15 19:30:26

- reply

Yes, they could. 🤔

2024-05-15 19:29:02

- reply

😂
Developer hellthreads are more like outer circles of purgatory threads.

2024-05-15 17:09:36

- reply

Are you defining
"locked" as "frozen, but don't delete anything, yet"
versus
"retired" as "already locked and events now ready for deletion"?
Or are you using locked as a different word for the second thing?

2024-05-15 15:28:42

I've submitted a patch to the event deletion NIP (09.md), adding the possibility to burn or retire an npub, rather than merely emptying it of events through deletion.
You can see the proposal and comment on it by opening the note below or by clicking https://gitworkshop.dev/repo/nips/proposal/23791a60b65c898b2eaa500323ef918e0c9d61b6a6dc16d7da42a3cc935075d7
#nevent1q…htlf

2024-05-14 11:05:51

- reply

It's one of the biggest relays in Germany, run by the #einundzwanzig guys. I'm using it as a mailbox for GitCitadel.

2024-05-14 11:02:19

- reply

Why does it update and recompile all 343 files every time? Can't seem to get it to only do specific ones.

2024-05-14 09:42:14

- reply

Can we see our starred stuff in our profile?

2024-05-14 09:37:51

- reply

Sorry. :-)
Just checking to see if replies refresh. Had to refresh the entire page, after the last note, but I think it was just slow.

2024-05-14 09:37:04

- reply

test

2024-05-14 09:17:34

- reply

Sorry, submitted to wrong project. Should be gitdevworkshop. Opened a new issue there.

2024-05-14 08:54:42

- reply

Hey, cool.
I guess I'm back to nagging you all day, again. 😜
j/k It's been coming along nicely.

2024-05-14 08:36:48

- reply

He he. My SilberWitch broom emoji works. 🤣

2024-05-14 08:08:00

- reply

test write in thread after re-open of resolved issue.

2024-05-14 07:33:03

Nos2x-fox browser extension now allows me to switch profiles in the extension, which is so much more elegant than having to do that in each individual client. So, very nice, very useful.
Thanks, @npub168n…926e

2024-05-09 17:49:48

- reply

Congratulations Finrod, on your first release! 🥳

2024-05-01 21:38:22

- reply

Okay, next problem:
ModuleNotFoundError: No module named '_sqlite3'

2024-05-01 19:05:43

- reply

I think it just finally installed and now I'm sort of in shock and overwhelmed.

2024-05-01 12:06:54

- reply

You require spacy 3.7 and it doesn't support python 3.6.

2024-05-01 11:28:12

- reply

That at least failed really fast. 😅 Need setuptools.

2024-05-01 11:12:56

- reply

@npub1494…zmp0 this is what I am staring at, for 30 minutes.
$ pip install spacy
WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip.
Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue.
To avoid this problem you can invoke Python with '-m pip' instead of running pip directly.
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Defaulting to user installation because normal site-packages is not writeable
Collecting spacy
Using cached spacy-2.3.9.tar.gz (1.0 MB)
Installing build dependencies ... |

2024-05-01 09:05:23

- reply

I propose
Layer 1 = dumb relays that are event storage systems. Curation limited to basic spam/illegal filters
Layer 2 = programmable relays that are controllers (aggregators, filters, broadcasters, curators, walled gardens) and show you a refined set of events that interest you personally.
Analog to nostr.wine or nos.lol (Layer 1) and filter.nostr.wine or creator.wine or christpill.nostr1.com (Layer 2).

2024-05-01 09:04:53

- reply

This doesn't take into account that every user can have their own relay and probably soon will. Faster to do it on the personal relay level or for a subscription fee on a different relay, and then just display in the client.
Also means you can utilize the settings in any client you use. Doing it in the client locks users into a client by reducing portability.

2024-05-01 08:40:38

Doing some Nostr work, today.
Had to take a break, for a few days, and enjoy some sunshine and shitposting.

2024-05-01 08:38:11

- reply

Very nice.

2024-04-23 21:38:19

- reply

Yeah, I mean for git servers like gitea. Git always asks for an e-mail and a name, and the e-mail is actually the main identifier. Didn't we discussing using NIP-05 or similar, instead?

2024-04-23 20:40:02

We can do this on self-hosted git servers, right?
#note1puh…fnqq

2024-04-23 20:35:16

- reply

Don't think renaming proposals would help. It's a different workflow and a different mindset.

2024-04-23 20:34:19

- reply

I think I needed a diagram showing "typical GitHub workflows", with forking and PRs versus "typical GitWorkshop workflows", with local clones and proposals.

2024-04-23 13:40:19

Also probably interesting for my Silberwitch Crew.
#note1c5w…g5tw

2024-04-21 23:03:00

- reply

Seen, felt and heard. I ❤️ you, too.

2024-04-21 23:01:48

MfW a developer was gracious enough to leave me the option of logging in with nsec, even though it's regarded. https://image.nostr.build/3a8341e69fe17a707d5a0d9f90b4bdd2f2ce06f20b33bbdc04d37ce7aff159a7.gif

2024-04-21 22:35:33

- reply

The existential angst set in, when I realized that I have to program the damn thing and it's like OMG.
https://image.nostr.build/0b3b14f90e1f046ce222fcb128890667a02d58d6018d2f0dcf83d1ed1ae7050d.png

2024-04-21 22:34:32

- reply

I look like a kindergarten teacher.
Why am I fighting this?

2024-04-21 22:33:32

I just implemented a register machine simulation and programmed it to implement a power function and now I am wondering if I shouldn't become a kindergarden teacher.

2024-04-21 14:02:12

- reply

Ah, okay. Now I get how that patches stuff works. Neat.

2024-04-21 10:15:13

- reply

@npub15qy…yejr I've never used such a setup before, nor do I know anyone who has. We've only used PRs, so this is a whole different workflow.
As far as I can tell, it works like this
1) Source repo someplace reachable by remotes
2) Local clone of source by anyone with access
3) Local commits made.
4) Ngit proposal sent, with commits included.
5) If proposal not accepted: nothing happens except status change (Do I have to do this on gitworkshop, or can I do it in ngit?)
6) If proposal accepted: local maintainer pulls the proposal down and merges it in locally.
7) Maintainer pushes to source remote repo.
8) Everyone else pulls the change from the source.