sickchill VS nostr

Sickchill updates date back only 4 days. https://github.com/SickChill/sickchill

Huh. Is that so? I guess Wikipedia is wrong. That's okay, I was told never to trust it when I was in school. Somebody may want to tell all of these different developers that their nifty software is redundant since serving is the same as managing.

I can see i'm on Version: v2022.07.20 and i get a pop-up at the top 'There is a newer version available — Update Now'. Clicking Update Now shuts down Sickchill, does something and then brings it back up with the same version. The link for 'newer version available' takes you to https://github.com/SickChill/SickChill/compare/v2022.07.20...v2022.09.14 but it doesn't appear to install it. Once it restarts you see the same 'Update now' message appear.

someserver:/opt/sickchill$ git remote set-url origin https://github.com/SickChill/SickChill.git someserver:/opt/sickchill$ git remote set-branches --add origin master media@k2:/opt/sickchill$ git remote update Fetching origin Fetching upstream someserver:/opt/sickchill$ git fetch origin someserver:/opt/sickchill$ someserver:/opt/sickchill$ git checkout master Already on 'master' Your branch is up to date with 'upstream/master'. someserver:/opt/sickchill$ git branch --set-upstream-to origin/master Branch 'master' set up to track remote branch 'master' from 'origin'. someserver:/opt/sickchill$ git reset --hard origin/master HEAD is now at a36953882 Release version 2022.8.15 someserver:/opt/sickchill$ git pull Already up to date. someserver:/opt/sickchill$ python /opt/sickchill/SickChill.py -d Traceback (most recent call last): File "/opt/sickchill/SickChill.py", line 14, in import sickchill.start File "/opt/sickchill/sickchill/__init__.py", line 1, in from sickchill.init_helpers import maybe_daemonize, poetry_install File "/opt/sickchill/sickchill/init_helpers.py", line 24 pid_file: Path = None ^ SyntaxError: invalid syntax

git remote add upstream https://github.com/SickChill/SickChill.git git fetch upstream git checkout master git branch -u upstream/master git reset --hard upstream/master git pull

Yes it's still active here: https://github.com/SickChill/SickChill/issues/7504

Some resources if you're interested in learning more: https://nostr.com/ https://ron.stoner.com/nostr_Security_and_Privacy https://github.com/nostr-protocol/nostr/ https://nostorg.github.io/clients/

I think your best bet here is Nostr (Notes and Other Stuff Transmitted by Relays): https://nostr.com https://github.com/nostr-protocol/nostr

Nostr isn't a federated platform like Mastodon or Lemmy, it's more similar to the AT protocol created by Bluesky, whilst being far simpler to understand and write apps using it. The nostr protocol is defined by a series of NIPs (Nostr implementation possibilites https://github.com/nostr-protocol/nips), the most basic of which can be implemented in a client or a relay in 50-100 lines of code in any modern programming language.

Each user runs a client, anyone can write a relay or run any of hundreds of existing implementations, both clients and relays can choose to support a number of NIPs. Users have a public-private keypair, and distribute notes to relays signed with their private key, which are verified by relays. Clients subscribe via websockets to any number of relays (I usually have 20-30), and receive notes from all users on those relays' databases, or filtered by the public keys of the users you're following. Relays for the most part don't communicate with each other. If you're ever blocked or banned from a relay, you'll still be able to have your notes seen as long as you have at least one relay in common with anyone who wants to see them. I run my own as well for extra resiliency.

At the moment there's ~50 standardised NIPs, which add features like likes, zaps (bitcoin tips for notes), user status, post expiration, mentions, search, DMs, and public chats. Nearly all of these are supported by popular clients and relays. While nostr is primarily used for social media at the moment, it's already possible to build upon as a protocol for pretty much any online service.

The total active user count on most public relays I'd estimate is somewhere around 500k to a million, though the nature of the protocol makes it impossible to estimate its true size. The perceived community on most relays before following anyone frankly can get pretty cancerous, mainly due to a lot of clients sorting notes by new by default, so I can only hope to high heaven it'll improve as it grows.

Though like any new non-centralised platform, it's more difficult to get started on for most non-technical users as they have to pick one of hundreds of clients to install, and requires caution to never leak your private key and be very wary of which clients you trust it with.

I hope this was not too technical and all over the place. If you are interested in knowing more please ask me or check out https://github.com/nostr-protocol/nostr or https://nostr.com/get-started

Without movement on this [1] I can't see adoption.

[1] https://github.com/nostr-protocol/nostr/issues/97

I think the next stage is decentralized social media. Something like nostr (1) where there’s no centralized entity determining the algorithm to boost. It’s up to the individual to follow users.

Perhaps the next challenge would be human verification, even with this protocol we’d need something to index public people by to handle discovery.

Even before LLM’s became as mainstream as they are, most social media platforms were riddled with spam: affiliate marketing, drop shipping crap, and people who are running some sort of con.

1 - https://github.com/nostr-protocol/nostr already has 8k stars on github

Considering that Reddit might not be able to negotiate better pricing for API usage, it's worth considering a different approach. The future of social media seems to be moving towards protocols rather than specific platforms. This means that instead of relying on a single platform like Reddit, Apollo should focus on using a protocol called NOSTR (you can find more information at https://github.com/nostr-protocol/nostr).

Holding me back from posting updates of what I had for breakfast is the problem of private key sharing with services that I can use in order to post updates of what I had for breakfast.

A client or service will inevitably be compromised. And with it, the private keys of all using it whether stored by the service or logged on entry by a compromised system.

Private keys should be chained, master->subkey, with subkey the public key of the service __or a solution like that or that ends in the same result. When (not if) a service or key is compromised, the key can be blacklisted and/or any key co-signed by a compromised service blacklisted.

I'm confused by the oversight. It's also been raised here https://github.com/nostr-protocol/nostr/issues/97

Until then, I'll have to keep my updates of what I had for breakfast to myself.