Chess.com has huge potential. Want to vibe it together?

My RSS app. Put what I subscribe to into my nostr feed.

Oh but technically that’s not foss. So technically Lichess is the answer, since it’s FOSS.

Wait… you had this already started before I commented??

have you seen the rss to nostr repos on github?

polybar ..a module to quick-post to nostr and check for notifications

GitHub

GitHub - polybar/polybar: A fast and easy-to-use status bar

A fast and easy-to-use status bar. Contribute to polybar/polybar development by creating an account on GitHub.

Owncast (10k GH stars) It's the most popular self hosted RTMP streaming server with chat integrated. You set it up to host your own stream with chat. Different chat protocols are supported, including Mastodon, but not Nostr. A Nostr integration would 1. Create a Nostr kind 30311 event on live stream starts, and update it as the stream runs/ends 2. Pick up kind 1311 events for the chat feed It would be a very good trojan horse to Nostr. The moment existing Owncast get defaulted into publishing 30311's, Zap Stream etc will be full of content. See owncast.online and

GitHub

GitHub - owncast/owncast: Take control over your live stream video by running it yourself. Streaming + chat out of the box.

Take control over your live stream video by running it yourself. Streaming + chat out of the box. - owncast/owncast

quick-post to nostr - do you expect polybar to keep a copy of your nsec? to pass on a request to an external signer? to open your default nostr app?

how does this sound @Kieran

I saw one a year or so ago.

basically the idea of ​​Oni

GitHub

GitHub - TekkadanPlays/oni: owncast + nostr

owncast + nostr. Contribute to TekkadanPlays/oni development by creating an account on GitHub.

on

Jumble

Jumble - Imwald Edition 🌲

A user-friendly Nostr client focused on relay feed browsing and relay discovery. The Imwald edition focuses on publications and articles.

a fork of jumble.social there is an RSS feed reader, it is a separate tab not in the same feed

Brave browser, with a wallet that supports NWC and WebLN and a NIP-07 signer built in

the new brave is shugur

GitHub

GitHub - Shugur-Network/nw-extention: Browser extension for accessing decentralized websites on Nostr - Chrome & Firefox support

Browser extension for accessing decentralized websites on Nostr - Chrome & Firefox support - Shugur-Network/nw-extention

I did not know of this. Yes exactly this. And submit it back up stream so every HLS URL ends up on Nostr. Tekkadan must be on Nostr? I haven't spotted him/this before now.

Ah wait, I follow you! Hi @Tekkadan, ゲロゲロ! 🐸

nothing for now

somehting that didnot workout well with email login /kyc but useful

Hello! I am considering an implementation of IRC with nostr authentication for the integrated Owncast chat. I think it could be interesting to combine them in this way, as it would provide a bit more permanence to the integrated chat. When live, a new ephemeral chat can become active for the current session, while other channels could persists across streams. I don't intend to integrate nostr relay based chats but anyone is welcome to do so. I am mostly interested in the few functions listed in the oni repo. Live broadcast events, then authentication with IRC, and NWC + zaps for both users and the admin. Potentially from there NIP-25 reactions could also be worked into the IRC client (looking at Ergo) @cloud fodder has an instance running with nostr auth at noirc.net I'm usually hanging out in there as well if anyone wants to chat with us!

I may work om such thing with @Awiteb. The issue is NIP-64 is not well defined and missed a lot of stuff. It's several months we are talking about it and some ideas are there.

What is this? Can Nostr integrate into Lichess?

exactly, Lichess is great

I love 960 on lichess. Far more fun than classical

well, yes and no. Classical has and will always have a great appeal, given that it made history, and the history of the game is all classical. However, the opening theory makes chess less fun because it's about memory, but at non professional levels it's not really an issue imo, because you can do very good in the first 8-10 moves not by memory, but by learning the spirit of that opening, the motives and the typical moves and plans.

I was never a chess player as a youngster, so I find that 960 evens the playing field, as I don't know any classical chess openings. I suppose I just find the 960 version 960 times more interesting with 960 possible starting positions. I play it for hours every night, but I still have a low rating! For me, 960 is a more interesting game.

nsec could be saved in the polybar [associated] configs, and for posting a small/floating terminal (cli) window could open to compose posts

Can you tell me exactly what is wrong with nip-64?

I’ll start tinkering with this on the weekend. I have a very specific vision for it. I want individual moves to be zappable. So that players and viewers when they replay the game, they can zap epic moves. For some reason I’m convinced that’s fun. 😁

We already have cli nak by @npub180cv...h6w6. What is different here?

Interesting. I was thinking there might be a friendly p2p wager e.g. 1,000 sats

emacs

I have heard this sequence of letters but I dont know what it means. What does it mean? What jobs do emacs help you get done? Where do you see nostr fitting in?

mushroomobserver.org The how seems pretty obvious in anything where crowd sourced data is collected & discussed like this... unless you mean the technical how, of which I have no idea 😅

any bar with “on-click” capabilities can spawn a ‘post to nostr’ shell script using nak in a popup terminal

Excalidraw. Save the excaladraw as an event content. Collaborativly draw together on nostr. Also, Not foss but a super simple app that's needed is a wishlist app. New list kind. Image, description, url, price. I currently use wishlist.com but would be nice if that data was on nostr instead.

Gnostream already does this.

But chat doesn't work yet. And I didn't have a release candidate yet...

There is already a nip for open chess.

You can run one of my bots for each of your feeds. Gonostrss

GitHub

GitHub - 0ceanSlim/go-nostrss: Turn any RSS Feed into a nostr Profile

Turn any RSS Feed into a nostr Profile. Contribute to 0ceanSlim/go-nostrss development by creating an account on GitHub.

why do we need login for excalidraw? it already "just works" without any login

Yup. It’s being discussed an another comment tree under this post somewhere. I think this goes beyond the nip. Imo It’s about how you offer the nostr chess experience.

#YESTR

We will get it working nicely.

was thinking about showing notifications on the bar, but dunst could handle that ..just thinking out loud here 🤪

was thinking about showing notifications on the bar, but dunst could handle that i guess

the technical implementation aside, can you color why you want a bar with "post to nostr"? What's the user story, job-to-be-done?

was thinking less friction to post

came here to say lichess 💜♟️

what exactly do you see nostr changing about mushroomobserver? what job is nostr helping with, that mushroomobserver current setup does not accomplish for the mushroomobserver enjoyer? how do you pitch your proposed update(s) to the mushroomobserver maintainer?

The live collaboration already works without nostr login. To me this is the strength of excalidraw - no crap email/other log in experience. It just works once you load it in the browser. What are you thinking for saving drawings: 1) Events with excalidraw URLs are posted to relays, or 2) Raw excalidraw files could be uploaded to blossom servers

I suppose either would work. Blossom is probably more reliable since the excalidraw file can be pretty big. But the file is also pan text so you could potentially store the whole thing in an event. Most relays would likely reject it for size though. You could of course build a relay that just handled these events though.

I just test saved a simple excalidraw file. Size of 2MB is way too big for relay storage for nostr general relays

Right. That's why I said you'd have to have a relay just for it or use blossom. Blossom makes way more sense.

I just forked a blossom server and added a whole frontend. I think I can pretty easily add a link from .excalidraw files that just opens excalidraw with that data loaded. Work in progress, a lot of stuff is broken so I haven't shared yet:

Gallery - Blossom Gallery

The blossom parts all work because they did before I forked it. I just added the frontend. Before it was just a blossom server.

No clear description if how to actually use it. No instructions on how to calculate users rating. We can't put anyone on a match with a grand master randomly! No tag or identifier to distinguish each game from other games. By doing this we won't need to send the whole PGN back an forth I believe. And a lot of stuff like tournaments, puzzles and votes chess is missing that can be defined. We can define a profile field for user to put their FIDE rating/title with propf.

Already possible, each move have a different event now, you can like it, zap it, comment on it, mention it somewhere, qoute it and more. Clients should support it. I may support it on my client.

Seems fun, so I assume Lichess is supporting some kind of extension.

But nothing work well like chess.com. Perfect design, nice features, huge community and...

Well for starters, contributions to their catalog are currently collected in two ways, via the website and a simple mobile app. Adding Nostr identities & changing entries to Nostr events would open the door for social clients to implement the functionality of their app and open up their forums to more easily accessible mobile discussion, as well as all the nostr desktop/web ways to access conversation. They could increase their activity and contributor base with little effort. This would all benefit current nostr/shoomers, and introduce mushroomobserver users to the portable identity and interoperability thay we all enjoy. Then, there is the relay part, which would help to keep the data redundant and available, reducing dependency on their servers, which I believe have been struggling with AI scraping recently, making their mission to keep data free and widely accessible more difficult. Anyone who wanted to operate a mycology oriented relay could manage entries and discussions in whatever way they see fit, whether that be professional, amateur, location based, by foraging group, etc. The need to moderate would be distributed to the relay operators. There would be no reason why their system couldn't still collect and maintain a huge database of entries... or they could simply serve everything on their site as connections from a set of chosen relays. Accessing that data from the user side would make it easier to navigate and reduce chances of the site disappearing along with all entries. Their goal keeping community collected data available to the community would be distributed amongst the community. I think it's a perfect fit. As far as pitching this... that probably would be my pitch, but somebody who could look over their codebase & see if Nostr does actually solve some of their problems and/or make their lives easier, would really need to tack on some technical understanding.

DMd you with coop/nip-17

Replied

Careful 😂

bullish on owncast +nostrIRc

im starting to wonder if elsat asks questions just to passive aggressively disagree with the answers 😂🤓

🤣 🤓

Lmao Just seeking the truth 😘

I follow abt half of what you're saying but I might stumble in!