MichaelJ

Building the library of Alexandria

Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

NIP-05 Address

Profile Code

nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpzpmhxue69uhkummnw3ezuamfdejszxnhwden5te0w35x2en0wfjhxapwdehhxarjxyhxxmmdalsa2k

Publishing to

Author Public Key

npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn

Show more details

Last Notes

2025-03-18 15:34:46 GMT

- reply

Good point. Ngit can already handle a good deal of the collaboration, and our team will build more collaboration tools as we work more on git stuff. We just need a place to stash code that's not GitHub and that doesn't require reinventing git in the form of Nostr events.

2025-03-18 14:12:51 GMT

- reply

We can already do code collaboration via Nostr using ngit, but ngit still requires you to use a git server, and most people use GitHub.

2025-03-18 14:11:23 GMT

We host Alexandria and our other projects on a private git server using OneDev.
Would other #nostrdevs be interested if we began providing a public git server as a (probably paid) service for others to host their projects?
Our goal is to break dependency on GitHub, and this would be a step in that direction.
#nevent1q…cch8

2025-03-04 18:04:33 GMT

- reply

How much damage will it do to their economy to keep throwing bodies at the front lines, though?

2025-03-04 17:46:27 GMT

- reply

We'll see if the stalemate breaks in Russia's favor soon as Ukraine begins to exhaust their weapons supplies.
This next period will probably tell us a lot about the state of the Russian military.

2025-03-03 22:29:59 GMT

- reply

Because noe centrael entitie caen dictayte youre fpellinge.

2025-03-03 21:32:57 GMT

Fourgete all caps, I'm poastinge lieke ye Middel English.
#nevent1q…ndm5

2025-03-03 18:45:55 GMT

- reply

Spele liek ye olden dayes—houwever the fuckk yeu wantt

2025-03-02 01:52:11 GMT

- reply

Fair enough. I guess sometimes I find giving part of my brain music to focus on frees the rest to concentrate.

2025-02-27 14:01:30 GMT

- reply

The tradeoff is that the day job slows down Nostr development 🤷‍♂️

2025-02-26 16:42:17 GMT

- reply

Works for me!

2025-02-26 15:40:41 GMT

- reply

I like the idea of using a single-letter tag for indexing. I'd suggest just using @nprofile…ehxa's original suggestion, but breaking it up across the tag, so `["w", "BTC", "bitcoin", "address"]`.
A client could assemble the values into the form the user needs for various purposes.

2025-02-26 13:24:50 GMT

- reply

I'm not mean to it, but it's not a person. 🤷‍♂️

2025-02-25 16:49:30 GMT

- reply

We have a OneDev instance on which we host our repos and track tickets. Using it requires creating a login, so GitWorkshop is better as a public-facing tracking tool.

2025-02-25 04:10:18 GMT

- reply

It's kinda funny to me how short the timescales are that Anthropic is working on.
For instance, on their site I read, "since June of 2024, Claude has been the leading LLM for coding." June of 2024 was basically yesterday.
Anthropic wants Claude to provide "breakthrough solutions" by 2027. I wonder if we won't become myopic, with everything happening on such short timescales.

2025-02-25 04:06:09 GMT

Wake up babe, new Claude just dropped.
https://www.anthropic.com/news/claude-3-7-sonnet

2025-02-24 22:21:11 GMT

- reply

Item 4 is already in our backlog—we plan to add anonymous publishing.
As to the others, we can create tickets for those.

2025-02-24 21:32:53 GMT

Anyone have recommendations for a good Japanese whiskey?
#asknostr

2025-02-22 22:31:29 GMT

- reply

Yup, we have work tickets on our backlog for fixing the table of contents. We'll get to it after we polish up the publications reading some more, particularly on the performance front.

2025-02-22 18:02:44 GMT

- reply

VS Code for its extension support. More recently Cursor, which is a fork of VS Code with first-class LLM integrations.
I think @nprofile…ddwx may have some good recommendations though.

2025-02-22 04:45:38 GMT

On behalf of the @npub1s3h…75wz team, I want to give a big shout-out to @npub1636…qpl4, who stepped in with his TailwindCSS expertise and spruced up the UI in #Alexandria for NIP-62 publications. You can see his work below.
I'm particularly grateful for his attention to detail on the light mode variants. I dare say Alexandria now has one of the most elegant light mode UIs in the Nostr space.
Take a look at these latest developments at next-alexandria.gitcitadel.eu, and let us know what you think!
https://image.nostr.build/6d1701569819d2c31853a2d5ca7d44850110ce90ead6e2305ba88338ab9d62ac.png
https://image.nostr.build/b3d44ba3c5db2698d43bfcf09c0fb97799494a1cb49ca765fdbc5db821ef183c.png
https://image.nostr.build/4607546d89d98d2cb54634535293ad46dea8e75239b081f4086a5d87efbda9d0.png
https://image.nostr.build/39f7b26322ed9e06a359ad74fbf7a7fa3e733e8cf42fe7b28e9d6cac51dddb92.png

2025-02-21 14:08:13 GMT

- reply

One of my favorite resources lately has been https://refactoring.guru. It's a great place to survey code organization and design patterns to understand what is available to help solve the problem at hand.

2025-02-20 21:58:53 GMT

- reply

We have a Matrix chat with @nprofile…u7te, @nprofile…nggv, and @nprofile…aqk5.
We've mostly been focusing on the needs of the #Alexandria project, but it's a cool spot for talking about relay concerns.

2025-02-20 14:50:19 GMT

Help us make #Alexandria robust and stable on all platforms! Comment your Nostr browsing setup below 👇
#nevent1q…wnch

2025-02-18 15:26:39 GMT

- reply

Yeah I agree it's outside scope. But if we wanted to add versioning, I think metadata would be the way to do it.

2025-02-18 15:05:00 GMT

- reply

Potentially. Just throw a bunch of tags on there.
Though that wouldn't work if we wanted to tie metadata to each level of the file tree.

2025-02-18 14:07:45 GMT

- reply

Versioning could be handled by the metadata event @npub1ecd…s735 suggested 🤔

2025-02-18 14:05:08 GMT

- reply

What kind of information would it be useful to have on this distributed filesystem concept? It doesn't need to exactly mirror Unix. Should we have a metadata event that contains relay hints, for instance?

2025-02-18 05:48:25 GMT

- reply

I suppose, for symlinks, a client could discover them by requesting kind 30044 events containing an `a` tag pointing to the drive's root 30043 event.
I wonder if this kind of lookup by tag value is faster, slower, or the same speed as a lookup from a known event to one of its children? The relay devs would likely know.

2025-02-18 05:45:21 GMT

- reply

From the article:
"The `a` tags MUST be an unordered list of root 30040 index events."
A couple of notes:
1. The diagram shows a symlink connected to the drive event. How do we make symlinks discoverable for a client trying to browse a drive? It might be better for the drive to reference the symlink, and then the symlink references a "leaf" event in the filetree.
2. This specification says "unordered" list. Does this mean the client can render the child events in any order it desires? That differs from the behavior defined for 30040 events, so we should make sure the expectation is perfectly clear.
3. To use the Drive analogy, a typical drive would only have one root (e.g., `/` on Linux, or `C:\` on Windows). Is the 30043 considered to be the root of the filetree, or is it the flag that identifies the root? If that's the case, the root is the 30040, and each drive should have only one root.

2025-02-17 22:47:24 GMT

- reply

Maybe the most idiomatic way to implement this pattern with modals in Svelte 5 is to use snapshots. That may suffice to capture the variables the closure needs into a persisted context.
https://svelte.dev/docs/kit/snapshots

2025-02-17 19:06:33 GMT

- reply

Could we use 30040s to index blossom files? I don't see why not.

2025-02-15 03:08:44 GMT

- reply

If a struct is like the blueprints of a car, then the blueprints would say it needs to have an engine, and they might specify a few kinds of engine it might have. Maybe the car designer isn't an engine designer. He'll tell the engine designer "Go make an engine for this car," and trust the engine designer to do his job.
We'd say the lead designer's blueprint, in this case, is like the struct and its traits—they say that there has to _be_ and engine. The impl is like the engineer who actually designs the engine and makes it fit the vehicle.

2025-02-15 02:17:08 GMT

- reply

That chocolate looks so good! And elderberry? Amazing 😋

2025-02-14 19:26:04 GMT

- reply

Lemme just switch everything to Clojure rq.

2025-02-14 19:00:56 GMT

Everyday I weep at the slow, inexorable enshittification of software.

2025-02-11 18:47:00 GMT

- reply

Yeah and with all that privacy there's no paper trail when your ecash mint decides to walk off with your sats. 🤷‍♂️

2025-02-11 18:39:20 GMT

It seems that the problem with ecash is that it requires you to trust a 3rd party like you would a bank, but without any of the insurance or legal protections for your assets that exist with a real bank.
#nevent1q…fz3g

2025-02-08 15:14:45 GMT

- reply

I totally understand! We're an open source project, so if you ever want to contribute some code here or there, let us know and we can assign you a ticket!

2025-02-08 15:08:39 GMT

For anyone who wants serious buy-in to the future of project #Alexandria, this is your chance.
#nevent1q…xf00

2025-02-07 23:42:48 GMT

- reply

Haven't heard of it, till now! Thanks for the heads-up!

2025-02-07 14:10:08 GMT

- reply

Exactly. It takes a clear intention, first, which requires a basic understanding of programming techniques. Learning how to apply techniques in this or that language is where LLMs comes in handy.

2025-02-07 04:23:42 GMT

- reply

I would suggest doing it the other way around, actually. Ask the LLMs and the Internet as many questions as you want, but write the code by hand. That will cement the concepts better.

2025-02-05 19:11:39 GMT

- reply

There's already a client being developed for that by @nprofile…vd7t, we call it #Alexandria.
@nprofile…0yl9 was inspired by Obsidian when he came up with the idea.

2025-02-05 16:50:08 GMT

- reply

Everyone starting a business works for little or no pay while they're getting the business off the ground.

2025-02-02 15:46:19 GMT

- reply

Beave has been on top of the bug reporting for us!

2025-01-31 14:56:36 GMT

AI is going to either make design and planning the most critical phase of the software development lifecycle, or eliminate planning altogether in favor of rapid turnaround.

2025-01-31 14:54:36 GMT

- reply

I'd like to hear more of this thought.

2025-01-25 14:50:24 GMT

I want to emphasize that we're building a product on Nostr because we believe in Nostr's mission of protecting freedom of speech. Thus, our product, #Alexadria, focuses on the uniqueness of Nostr as such, and we are using its momentum to give back to the protocol.
Our core concept of open publications has already made its way into a NIP proposal, which others have begun to adopt. This will make Nostr a haven for independent writers, publishers, and scientists.
Our work on publications illustrated the need for a Nostr citation format, and the recently-proposed NIP-A4 addresses that, providing a means of citing physical and digital works, as well as LLM-generated content.
The Euler edition of Alexandria will utilize our in-development C++ SDK for Nostr, which we intend to support the needs of all clients developers, not just the needs of our project.
Your support of Alexandria lets us contribute to fortifying and growing Nostr as a whole. Thank you for all the ways you support this effort.
#naddr1qq…dna7

2025-01-22 18:12:32 GMT

#breadstr
#nevent1q…jdvy

2025-01-21 17:48:28 GMT

- reply

Totally! Title suggestions are welcome!

2025-01-21 17:17:42 GMT

- reply

Yep we'll keep pushing updates there as we make progress!
Our goal is to be the Nostr client for readers, and we want to enable not just reading books, but interacting with the material, sharing quotes and passages, and discussing with other readers.
We're simultaneously building the app and publishing public-domain works as collections of Nostr events. We've also started publishing books by other Nostriches (with permission).

2025-01-21 04:29:48 GMT

- reply

Agree on all counts. There's no absolute need for America to be dependent on foreign countries for any of its economic necessities.

2025-01-16 17:41:45 GMT

More #sourdough #breadstr fresh out of the oven.
The last one turned out so well, I wanted to make sure I could do it consistently. So I tried to repeat the process as closely as possible.
Still, I experimented a bit. Did half bread flour, half whole wheat, and increased the water by 25g because whole wheat absorbs more.
In the presentation, I made a curving, diagonal score to produce that crisp ear, and I experimented with some decorative scoring on the opposite side.
https://image.nostr.build/f3b3203ab7a6a66088a3c5a39637ebb3231823139de8c63745d7e565819d84cb.jpg

2025-01-14 16:23:50 GMT

- reply

How do you get by on so little sleep?

2025-01-12 16:37:51 GMT

Few yet understand this, but #Alexandria, in principle, makes every publication following the NIP-62 format uniquely addressable online.
If I provide you the Alexandria URL for a publication, you can verify its authenticity by confirming that the publication's Nostr event was signed by the entity that has the rights to publish it. This cryptographic identity cannot be faked. If changes are introduced, such as by the publication of a new edition, this too can be verified using Nostr identities.
It's like every possible publication that could be created has a street address, and you can go knock on the door and see for yourself that the person who is supposed to live there is indeed the person who answers the door.
We've not yet scratched the surface of the impact this new reality will have.

2025-01-09 21:02:35 GMT

- reply

Yes! STEM doesn't answer the "why" questions; only the liberal arts can do that.

2025-01-09 19:06:01 GMT

- reply

Lots of literature (mostly classic up through the mid-20th century), history (ancient, medieval, early modern, American), mathematics, science, grammar, and a small handful of other things.
We learned to spell, then write cursive, then we studied vocabulary, then we just wrote.
My mom was an English major and taught me almost everything I know about formal writing. I sailed through my first year of college from the momentum she gave me in that regard.
We also pretty consistently had some sort of exposure to music. I took two years of piano lessons, but I spent much longer signing Gregorian Chant with our church choir.

2025-01-09 18:54:16 GMT

- reply

Having an education in the liberal arts gives you more tools to appreciate, understand, and discuss our shared heritage, but it's also possible (though harder) to develop those tools on your own.
Also, you don't need to be skilled in analysis of the classics to be conversant in them on a more casual level. Both are good.

2025-01-07 20:05:28 GMT

If the outbox model is implemented correctly, every user will typically only read from one relay, and will write to a small handful.
Of course, reads/writes will change depending on the event the user is interacting with.

2025-01-02 23:07:29 GMT

- reply

I think it's the long-term future of Nostr. Nostr is a communication protocol, not a storage protocol.
While it's still small, we can use the relays as DBs. As it grows, we'll need to think bigger.

2025-01-02 23:06:18 GMT

- reply

To add to what @nprofile…qlr4 said, Aedile is intended to be a fast, efficient, and stable set of code that other developers can use to bootstrap Nostr apps.
There are a few things every Nostr clients needs to do, like connect to relays, handle user login, sign events, publish them, and search. We aim to make Aedile the best at all of those so it can be a firm foundation for future Nostr apps.

2024-12-31 22:02:50 GMT

- reply

Being the chilli oil dilution sipper must be an interesting job

2024-12-31 18:43:32 GMT

- reply

Dang you go way back.
I have an older coworker who had to work with punch cards in college.
Meanwhile the "worst" I had to do is write a C++ project in vim.

2024-12-30 13:03:39 GMT

- reply

Here's how we break out of the cage:
#nevent1q…wtur

2024-12-30 13:02:20 GMT

Imagine a relay like a library and an event like a book. When you want to find a book from the library, you can do one of two things:
1. You can put a hold on the book in the library system. The librarians will find the book for you and have it delivered to your local branch, where you can pick it up as soon as it is available.
2. You can go find the book yourself. If it's not at your local branch, you can go to another branch and look for it there. It may take longer to find the book, but perhaps you'll stumble across something else you wouldn't have encountered otherwise.
So far, most Nostr clients can only place holds. You'll get the books you're looking for from your favorite authors, but what you won't get is the opportunity for serendipity among the shelves. There's room, I think, for clients that take you to different libraries and help you explore.

2024-12-30 03:00:34 GMT

- reply

I'm not sure our developers are treating relays as first-class entities.
Earlier today, as I was Jira mapping our Aedile dev kit project, I was thinking about how to structure the code. What are the first-class entities, and how should they be represented by the class structure?
I've come up with four first-class entities on Nostr, from the client's perspective:
1. Events
2. Relays
3. Users (npubs)
4. Subscriptions (event filters)
A well-designed client library should give all of these equal importance.
What does this mean?
Well, for example, I should be able do both event.send(myRelays) and relay.send(myEvent). It's up to me as the client developer to figure out which method best supports the kind of user experience I'm trying to create.
A social client might use the first method; the important thing is to create events and push them out over the network. What relays the events live on is less important than being able to chat with other npubs.
A relay-centric client, on the other hand, would use the second method. The priority here is to be able to view and interact with only the relays the user chooses, perhaps because each relay is a community, or different relays specialize in different event kinds.
Clients seem to focus on events, first; I have yet to see much development work on relay-centric UX. While this state of affairs persists, relays will remain underappreciated.

2024-12-27 04:00:47 GMT

- reply

C++ is more fundamental.

2024-12-27 03:06:42 GMT

Nerdy Christmas gift 🤓 https://image.nostr.build/0d7f0187a3de7b61d0d39309936cbdd6b6fa2a8af10a23e369d41e530c7e49e5.jpg

2024-12-20 03:30:50 GMT

- reply

Half my posts are about programming, but I do occasionally post about faith and such.
Welcome to Nostr @nprofile…u025! I'll keep you in my prayers!

2024-12-15 19:11:47 GMT

- reply

Yah we have two projects, accessible on GitHub, that implement the NIP.

2024-12-14 18:38:06 GMT

- reply

Jesus was born in December.
We know this because, when he was conceived in Mary's womb, Elizabeth was six months pregnant with John the Baptist.
John's birth was announced to Zachariah when he went to burn incense in the Temple. Zachariah's course of priestly service fell around the feast of Atonement, which falls around October. Counting six months forward from that places the conception of Christ near Passover, in March, and his birth in December.
This March date for the conception of Jesus agrees with many ancient traditions. The Jews believed the world was created in the month of Nisan on the Jewish calendar, which corresponds to March. Thus creation was renewed in Nisan by Christ's incarnation. It was also believed that a man was conceived and died on the same date. Given that Jesus died on the eve of Passover, this would place his conception likewise around Passover, in the month of Nisan/March. This dating agrees with ancient Christian sources, including the early Church Fathers to within two centuries of the time of Christ. This dating was not challenged until relatively recently.
Thus, the combined weight of Scriptural evidence and ancient Christian tradition supports the celebration of Christ's birth on December 25th, and it has nothing to do with any Pagan holidays.

2024-11-29 21:15:36 GMT

- reply

How one would even attempt to restart Mars' magnetic field, though, I have no idea.

2024-11-29 19:57:47 GMT

Say it louder for the people in the back.
If your trying to make a point in an internet discussion, dropping a link to a YouTube video without further explanation instantly kills the discussion. No one realistically has time to go watch a video, analyze its points, and formulate a response. We have lives and responsibilities.
#nevent1q…hxnt

2024-11-29 14:44:50 GMT

- reply

Nostr doesn't have the equivalent of a text editor "base app" that extensions could be popped into. Until such a thing exists, I think the best way to keep apps small and focused is to develop good practices for transferring the user's workflow between apps smoothly without losing context.

2024-11-29 13:36:20 GMT

- reply

I would just think in terms of micro-apps.
Maybe your Nostr app says "You want to do DMs? There's this great app, Simplex, over here that's perfect for that. Here, I'll help you get connected with this other guy via Simplex."
Once you've connected, you leave the Nostr app and DM on Simplex.

2024-11-28 05:02:01 GMT

- reply

It's never been tried! 🤣

2024-11-28 01:09:03 GMT

- reply

AAAAAAAAAAAAHHHHHBHHH

2024-11-21 17:20:08 GMT

In a training meeting for Microsoft Copilot, and they're suggesting saying "please" and "thank you" to help train it to write responses in a better tone.
Sorry, the LLM is a machine, not a person, I'm going to tell it what I want plainly and directly.

2024-11-20 07:26:22 GMT

- reply

Chachi has real polls (non-zap) in chats.

2024-11-19 22:31:45 GMT

The Cathedral of Ávila must be one of the most distinctively Gothic cathedrals in Europe.
https://image.nostr.build/114f5de7366ab2c3c894e56652a65435be629f73609b338ed587aa8b527599d6.jpg

2024-11-14 07:55:23 GMT

- reply

I'll give that a look! The performance benchmarks provided look promising, so the only thing left to find out is whether it is easy to use. The nlohmann/json library is pretty straightforward and idiomatic.
I'll put this on my to-do backlog, and make a branch in Aedile at some point to work on migrating it to this library.

2024-11-06 06:21:01 GMT

- reply

I've been mulling how I can leverage the side project working on Nostr to build up my resume. Could be big, given enough time.

2024-10-26 22:26:53 GMT

- reply

I've got some buddies in #GitCitadel working on .deb build processes so we can distribute our apps as Linux desktop apps.
The Age of the Desktop will return.

2024-10-16 15:40:55 GMT

- reply

A WASM VM sounds promising! It would isolate code for security, but still run on the browser, correct?

2024-10-15 21:11:56 GMT

- reply

Framework has a GPU option on their 16" model.

2024-10-15 19:26:03 GMT

- reply

I follow the "atomic commits" philosophy, where you check in reversible, isolated changes, insofar as possible, when those changes are ready.

2024-10-12 14:31:01 GMT

- reply

The change detection is interesting, since relays may delete old versions of replaceable events. In theory, then, if there is an `a` tag and an `e` tag for the same event, the `e` tag should be preferred, as it is more specific. If the client notices an update, it can offer to update the `e` tag on the publishing user's behalf so it is in sync with the version addressed by the `a` tag.
However, that seems to be more of a client implementation concern than an event specification concern. In general, the same event should not be indexed twice in the same kind 30040 event, though it's not the end of the world if it happens, since a client can naively display the same event twice just as the index event suggests.

2024-10-12 14:08:02 GMT

- reply

I think there are two use cases:
1. Use `a` tags in index events the exact same way we use `e` tags. Index events don't contain content, so we don't need to worry about wikilinks in that context. Instead, a client can use `a` tags in an index as an option for referencing replaceable events that still works even after the replaceable event has been updated.
2. Use `a` tags in zettel events as wikilink hints. When a client parses the zettel content and encounters a wikilink, it should search the zettel event's `wikilinks` and `a` tags for a matching ID. `wikilink` tags can be used to reference an event by ID; which means the wikilink won't update to the newest version when the content changes. `a` tags can be used to reference an event by its address, which means the wikilink will always refer to the most up-to-date version of the linked event. A publishing client should have UX to let the user choose what kind of reference to use for each wikilink.

2024-10-12 00:13:03 GMT

- reply

In theory it's pretty important information to the customers, and management is asking us to build it.
We're in a modernization effort, so everything in the old version of this webpage has to be ported to the new tech stack. It'll let us experiment and iterate faster going forward.
But this page has been accruing features for about 10 years. It's really important to customers as a whole, but there are a few features that are barely touched.

2024-10-12 00:02:38 GMT

- reply

And this was after I had _improved_ the feature to give it greater flexibility 🙃

2024-10-11 17:40:35 GMT

- reply

What tech is on the client end of this stack? Native apps? PWAs? WebAssembly?
#asknostr

2024-10-11 12:29:28 GMT

- reply

Well, unpopular in secular circles. It's quite familiar to me as a Catholic.
The whole message of the confessional is that God hates sin, but that he loves you so much that you can drop by any time, confess your sins, and be forgiven. He wants it to be easy for us.

2024-10-06 01:35:04 GMT

- reply

No awards were given one way or another 😆
Bummed you couldn't make it! Hopefully we'll catch you next time!

2024-10-05 23:39:18 GMT

We just had our first #GitCitadel quarterly project meeting this morning. It was great to hear each other's voices after text chatting about the project on and off Nostr every day for several months.
We've got some exciting things on the way, but the running theme of the meeting was Stability. Our project supporters want it, and we think Nostr desperately needs it. Reflecting that theme, our testing strategy for Alexandria and Aedile was our biggest point of discussion. FOSS code is cheap, but reliability is valuable, and reliability is what we'll deliver.
Our first priority for Q4 is to deliver an alpha version of Alexandria with basic writing and viewing functionality for people to begin to explore. Once y'all have a chance to try it out, we'll begin to collect feedback and determine what features to prioritize next.
As Alexandria begins to mature, we'll turn some of our attention back towards Aedile, our Nostr Development Kit. Aedile will be a fast and reliable product built by developers, for developers, and we're excited to give it some attention again.
Thanks to everyone who has supported us thus far, and stay tuned! I'm stoked to see what our team can create.

2024-10-05 04:54:04 GMT

Gyv-N5C8ghkdgUtDIk9aFkDCVbU0fPhBS4xyJnKIcEc

2024-10-04 13:43:11 GMT

- reply

My understanding is that the workers' pay is falling relative to inflation, and their employers are still posting record profits. The shipping industry isn't struggling, so the dockworkers are demanding a share of those profits.

2024-10-02 19:55:34 GMT

- reply

Yes, but you can't do that with Nostr keys.

2024-10-02 03:10:41 GMT

- reply

Three points:
1. I agree the timing is awful and more consideration ought to be given to the needs of the communities impacted by Hurricane Helene, as well as others who depend on imported goods.
2. Saying "find another job" is not an answer, and ignores the realities of their situation and our economy. A big part of the dock workers' complaint is that automation will take their jobs—perhaps they ought to negotiate for retraining and gradual technology upgrades rather than rejecting the automation outright.
3. Many of the reactions I've seen sound very much like first-world problems. As I've learned more about the situation, I've seen that there are legitimate reasons to be concerned about the impact of the strike, but we should focus on those rather than vague complaints of "supply chain disruption."

2024-10-02 01:20:16 GMT

- reply

Watch out or the Branch Nostr Church of Bitcoin will excommunicate you 🤣