gotosocial VS bips

Honestly if a server allows free login, then it shouldn't matter how the donations are spent, the admins are probably at a loss anyway. I've seen large phpBB forums run on donations for a long time, so maybe federated socials can work too. One unfortunate thing I've noticed from running a single-user GoToSocial instance is that it consumes a lot of storage, I'm getting 8Gb just from myself and the instances I follow. This could be brought down with more agressive cache settings, but it still shows that people using these new social media still have habits from Twitter or Reddit, where bandwidth and storage is paid for by advertisers, and don't realize how many gigabytes they're casually moving around. I really hope this won't be the downfall of the Fediverse.

I'll be starting my own instance of the fediverse, something for myself and family only. I'll start with gotosocial, and add a reddit like alternative too, but haven't decided between kbin or lemmy yet. Maybe I'll add pixelfed down the line.

gotosocial is easy to install and easy to use, but you need 3rd party apps on your phone or computers to use it properly. Another option is snac2, you need to compile it manually but it is easy to use once compiled. Its web interface is kinda outdated, but it is usable as it is. Both are very light on resources, and can be installed on $4 vps.

[2] https://github.com/superseriousbusiness/gotosocial

GotoSocial would be another option (also in Go with SQLite backend.) Although you'll need a front-end because it doesn't ship with one.

https://github.com/superseriousbusiness/gotosocial

Not sure if you only want Mastodon. If not, I am running https://github.com/superseriousbusiness/gotosocial on a CPX11 Hetzner instance which costs 5.18 euros/month. Am hosting a few other things, but CX11 instance for 4.51 euros/month will also do well.

The main one is how they handle keys[1] which broke federation with Pleroma for a while. There's also some weirdness with their HTTP signing which breaks Honk follow requests but I'm still tracking that down.

[1] https://github.com/superseriousbusiness/gotosocial/issues/11...

Compare mastodon, pleroma, misskey, friendica, gotosocial, pixelfed, peertube (https://github.com/superseriousbusiness/gotosocial) and their main forks.

As u/riffic mentioned, Mastodon is quite heavy. But since mastodon follows (mostly) standard protocols, you can host an alternative. I’m really interested in Gotosocial, which is written in Go so it can run on a cheaper VPS. But it doesn’t seem to support all features (which will be a common thing with alternatives).

Modern bitcoin addresses use a base-32 character set that leaves out some of the most ambiguous pairs and also permutes the address ordering so that the most visually similar remaining characters produce single bit errors which are better handled by the addresses error detecting (and potentially correcting) code.

https://github.com/bitcoin/bips/blob/master/bip-0173.mediawi...

Context: Bitcoin miners have just adopted a 50% pay cut for themselves. This pay cut was baked into Bitcoin protocol at the launch of the network (mostly, see "BIP 42" [1]). The OP link gives information about the block in which this pay cut was made.

I get that HN comments tend to dismiss Bitcoin. But the fact that for the fourth time this pay cut has happened without a hitch speaks volumes to what makes Bitcoin interesting: It's a rare combination of economic incentives and technology that keeps chugging. Nobody can stop it. And it's extremely resistant to change. It requires no governmental approval. All attempts at subversion or interference have failed. There aren't many things that come close to that kind of record.

[1] https://github.com/bitcoin/bips/blob/master/bip-0042.mediawi...

Bitcoin transactions involve locking funds in scripts, which can only be spent if those locking conditions are met. The part of the script that expresses these locking conditions are called ScriptPubKeys. On the other hand, the part that provides unlocking scripts to satisfy the locking conditions is referred to as ScriptSig for legacy transactions, and ScriptWitness for SegWit Transactions. These scripts are evaluated by a stack-based language called Script. This article will mainly focus on ScriptPubKeys.

Here’s the reference https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

There are 5 271 537 971 301 488 476 000 309 317 528 177 868 800 possible permutations of the bip39 wordlist found here: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt when using 12 word seeds. You probably have better change to win the lottery every week for the rest of your life than cracking a 12 word seed in correct order

No one controls Bitcoin, because it's a protocol. Bitcoin Core is the reference implementation, but there are others, and anyone can create new implementations if they wish. Also, the Bitcoin Core maintainers can't just change something on a whim, because users would then switch to another fork. Maintainers (or miners or other groups) can't force their changes on users, because everyone can decide on their own which version they want to use.

The protocol development happens through BIPs (Bitcoin improvement proposals): https://github.com/bitcoin/bips

BIPs are discussed for years, before (and if) they are implemented, and basically everyone needs to agree on them, because no one wants to fork the blockchain, which could be devastating.

All the seeds generated from the CoolWallet (Number / Word) adhere to the BIP-39 protocol.