I like that standard because it's easier to backup .config folder instead of whole home exluding things you don't want to.
#realy installation is simple
install go 1.23 and git
git clone https://github.com/mleku/realy.git
cd realy
for the simplest but not as performant
export CGO_ENABLED=0
cd cmd/realy
go build .
this produces the binary in the current directory, then move the binary `realy` where you want, eg /usr/local/bin
realy env
spits out the default configuration (and when customised, the current configuration)
mkdir ~/.realy
realy env > ~/.realy/.env
these are the expected default locations for the data directory and configuration file
use your editor (nano i guess would be most people, maybe vi/vim for some) to edit, it's just a set of key/value pairs in standard env style
you can move it to another directory if you must, but you have to invoke it with the data directory environment variable set in the command, eg:
ROOT_DIR=/path/to/where/you/want/it PROFILE=.profileFolderNameCanBeAnyValidDirectoryName realy
this will then make realy look in that place to load the .env file (it's always called .env though, sorry #notsorry
for more information, see https://realy.lol it will explain how to disable CGO as well as, from the main readme.md, direct you to the instructions on how to build the bitcoin/secp256k1 signature library to get much better event signature verification performance
#realy uses an event store based on fiatjaf's eventstore/badger but much less resource hungry, and using the fastest #golang binary event encoder i am aware of, there is no extra configuration, no docker, no environment, #nobullshit
it is, in my 8 years experience at Go development a reasonably well written, maybe could be better documented codebase, and it should not be difficult, if you have the will, to learn Go and to modify this relay to do whatever you like, and please do ping me if you create featurse for it, i am happy to integrate them into the mainline with a suitable, consistent interface for configuring to use it (such as how it currently is a no-auth open public relay by default currently, but if you set AUTH_REQUIRED it requires nip-42 auth, and if you put your npub in OWNERS it will allow everyone on your follow list, once it's published to the relay, to publish notes to your relay and use it as an outbox
May I suggest to use XDG based .config/relay instead of home "pollution" 🙏🏻
MMA is stupid.
Yes, look at the steps. You take unconfirmed tx output and spend it.
I did that on many occasions.
Or I don't understand your goal 🤷🏻♂️
komunistů není nikdy málo.
I like the idea of streaming sats/s you listen. It makes you think.
#photography
Trees are amazing.
moving utxos can be fucking costly.
can ruin your coinjoin efforts.
be careful
I think you actually get the most data from the exterior.
serial numbers (potentially figure out when and where they bought it)
company inventory numbers (if it's for work), where they work, etc.
stickers (are you into bitcoin, games, ...)
steal it and return it, gain trust and start phishing...
Isn't that called a package manager? do we really need yet another one?
alternative.me is down
Check out who writes this article, they are Microsoft guys.
Read this article, inside it there is a link to yours.
https://unixdigest.com/articles/the-real-motivation-behind-systemd.html
I don't think they are wrong about this attack vector tho...
(Btw. I'm not advocating for or against systemd. Users will decide what's best for them. E.g. for my line of work things like systemd-growfs/makefs are very valuable. It doesn't mean I have to have them on my laptop.)
I found interesting the part about modifying the initrd image. I've done that in the past to save data from a broken system.
Just somehow never occured to me, that you can do malicious things like altering the system after the user decrypts the data.
This is also very interesting
https://0pointer.net/blog/authenticated-boot-and-disk-encryption-on-linux.html