Avatar
pleblee
69a0a0910b49a1dbfbc4e4f10df22b5806af5403a228267638f2e908c968228d
You should not need an account on a corporate server in order to use software.

It was a reckless success!

```

$ vulkaninfo | grep -i "deviceName\|driverID"

WARNING: NVK is not a conformant Vulkan implementation, testing use only.

deviceName = TU102

driverID = DRIVER_ID_MESA_NVK

$ doas inxi -G

Graphics: Device-1: Intel Raptor Lake-S GT1 [UHD Graphics 770] driver: i915 v: kernel

Device-2: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] driver: nouveau v: kernel

Display: server: X.org 1.21.1.11 driver: loaded: nouveau note: n/a (using device driver)

resolution:

Message: Advanced graphics data unavailable for root.

```

One of my better looking ☕ roasts

GM

Gonna try running the new open source vulkan driver for an RTX 2080 card on NixOS today.

https://discourse.nixos.org/t/nvidia-vulkan-driver-nvk-documentation/42900

TIL if I just rebuild vim-huge in nix, I'll get vim with clipboard support enabled. Upstream defaults ftw. Every distro ships vim without clipboard enabled, nixos included. But this is nixos, so I can just set it in configuration.nix and forget it.

Try it out if you want:

```

nix-shell -p 'vim_configurable.overrideAttrs (oldAttrs: { features = "huge"; })'

```

Boom. You can yank to the system primary clipboard using key chorn `"+y`

Supposedly you're supposed to be able have the normal yank chords do this to by setting `set clipboard+=unnamedplus`, but that didn't work in my environement for some reason. So I just did the reckless thing and remapped them directly:

```

" -- Buffers: yank to system primary clipboard. yay!

nnoremap y "+y

nnoremap yy "+yy

noremap y "+y

```

AT LAST. YES!

Most don't care about decentralization.

They don't build anything without VC money.

They don't have a real community or any real culture.

Even if something shows up I doubt it'll last long.

Took a few seconds to go through, but it worked!

A side effect of shaming devs into doing this is not only will users bitch about high bandwidth consumption, now they'll also bitch about terrible battery life.

Do we all really need every shitpost we download from our home relay to be cryptographically verified?

pep8: Only use underscores in your package names, no hyphens

PyPi: Only use hyphens in your package names, no underscores

Yeah relays are the attack surface. Does the app do much without relays?

"I would never join a platform like Nostr if there's no way notes can be deleted"

"Why is that?"

"Depending what kind of platform it wants to be, if you have content creators like on tiktok or Instagram and someone disagrees with what they say, on these platforms people go as far as finding out addresses and phone numbers and post them in the comments. Mods remove such things. If notes can't be deleted, such information stands there forever. It's dangerous and a no go"

Had a talk this morning following yesterday's discussions about safety on Nostr. This reply is hard to argue with. If you're a nym it doesn't concern you much. If you create "social media content" like videos or images and people even know or recognize you, they might do the worst things for the worst reasons and there currently is no way to prevent or stop that.

Thinking about this a lot today. It's a fine line between censorship resistance and people feeling safe to use the protocol in a way they see fit.

If we want to always have a couple of Bitcoin anons, ignore what I said. If we want mass adoption it's a topic we need to address.

Can it be addressed tho? Yes, but we would need to shift from absolute censorship resistance to something compromised. Maybe some community based reporting mechanism that relays comply with in terms of deleting said notes. We would still not have a central instance but the community guiding such things.

Should it be done? Up for discussion. Especially now that we have a main focus on the outbox model and blastr, it would make it way harder to implement something like that as notes get spread out on many relays that all would need to comply to some mechanism like that. Almost impossible if it's not a standard part of the protocol.

I know this is not a popular topic. I'm interested what people think about it tho.

The problem is that if someone (client devs or relays or whoever) has the power to censor, they will eventually be manipulated into doing it.

My take on the question is that users who are sensitive to that should operate within their own cocoon of safety. Walled gardens can be built on nostr. Like apps that only connect to private relays.