We crossed the border to devour a smoked brisket putine. Worth it.

One thing I noticed in this trip is that many hotels block Tor and thus the connection to a outbox relays fails in our default setting. We may need to add a way to temporarily turn off and connect to random relays in the open web after a few tries. Currently, the only option is to add a list of relays to your Trusted Relay list so that they always connect without Tor.

👀 View quoted note →

The campgrounds at Grand Isle state park on Lake Champlain are awesome. This is a must go if you like camping.

Motion to rename TikTokers to Vidiots

GM

Every client sucks at managing Follow lists at the moment. Next Amethyst version will add several features to assemble and manage lists right in the app by @KotlinGeek. View quoted note →

Wen Nostr?

When you open that app that was brand new last year and it already looks old and outdated. Designs these days age faster than milk.

Fast. Very fast.

We should make a Car that is a Nostr relay and all driving functions require signed events via bluetooth from Amber running on your phone. View quoted note →

So, they can't buy Bitcoin, but they can buy 20 billion dollars worth of Argentine pesos...

"politically unviable proposal" Dude.. we make the damn politics.

How many WoT Scoring providers are out there?

Desktop Apps should not share the same UI as Web Pages, which should not share the same UI as Mobile Apps. With Kotlin Multiplatform for Web now stable, this is clearer than ever. Your background and some components can be the same between them, but the UI should be vastly different. For instance, Desktop apps are mini window managers by design and tend to use multiple layouts to display lots of information and actions at the same time because monitors are so large and the mouse is so precise. They use a large amount of dialogs and popups, and generally have tabs inside of them for different things loaded at the same time. Memory, CPU, and disk usage are virtually unlimited. Notifications don't really exist, and you need to develop your own update warning system. Users are in the mindset that the app is theirs to own and organize, which leads to long-term thinking. On the web, there are no windows. Dialogs are terrible, and any internal tabs should use the browser's own tabbing system. Routes must be addressable with readable links that the user can see (which is not a thing in the Desktop or mobile). Bottom navigation is in conflict with the browser's own navigation buttons, and everything is just one pull away from a full restart. Somewhat unlimited memory, but CPU, IO, and disk are severely constrained by the browser. Users are in the mindset that they are renting the app while they are there; they are in somebody else's house, which leads to short-term thinking. On mobile, everything is very large. Buttons are big, and space is extremely limited. Some popups work, others don't. Tabs don't exist (even though many phones try to make it happen). Something that is just a click away on the Desktop is 3 clicks down on mobile. Navigation requires links, but the user never sees them. Memory is hard-capped at 512MB per app, background processes generally don't work, and the OS may decide to kill half of your stuff at any moment. Around the globe, phones cannot be trusted and are generally treated as a disposable asset, like your app. Devs that try to optimize for all 3 of them at the same time end up just making the lowest common denominator, and users suffer with massive delays and lack of care.

Cream cheese and jelly > Peanut butter and jelly.

GM

I think gov shutdowns would be more exciting if none of the federal workers showed up in the day after.