Initial support for Custom Emojis has been added to Corny Chat!!
If you haven't already favorited some emoji packs through nostrudel or emojito.meme, go ahead and do that first. Within Corny Chat, access your personal settings, and expand the visual settings. Clear one of the sticky emojis to show the selector. The Custom Emojis will be populated by all those emoji packs you've favorited.
https://i.nostr.build/LhcRLp34PwhYijes.png
This is similar for establishing room reactions via the Room Settings if you are a room owner or moderator.
https://i.nostr.build/eSEYNUji3tweySl6.png
Have fun with existing emoji packs (several of which have animations), or if you are pixel-art inclined, go ahead and define your own for inclusion.
If you find bugs, please let me know.
#foss #cornychat #devstr #emoji #hat
This is the same Bitcoin Node that I use for my zaps. The screen is attached to a raspberry pi encased in a cryptocloaks lightning shell case. The images are generated from my Nodeyez project code.
https://i.nostr.build/5WOWF5AqiXWnQPt3.gif
#foss #nodeyez #bitcoin
A bit late, but here's the release notes for Corny Chat for October. If you're interested in running an instance feel free to hit me up here on Nostr or Github if you run into any blocking challenges. Will have another cool update coming this week
---
October 2024 release of Corny Chat
🌽 Corny Chat is an open source audio space built on Jam that integrates Nostr and Lightning. A publicly running instance of Corny Chat is accessible at https://cornychat.com/. The following enhancements were made during October 2024.
=== Web Application
🆕 Edit Profile!
- Users can now edit their kind 0 metadata if a nostr extension is available
- Ability to upload avatar and banner image or specify the URI
- Uploaded images get sent to nostr.build
- Any unsupported metadata fields are retained
Avatars
- More users have emoji symbols added or changed (The Bitcoin Painter, Pentographer, Noshole, Marie)
- Refactored assignment logic for stage and audience users
User Profiles
- Images in notes can now be rendered inline in place of the URI for the image
- Made fetching outbox relays, posts and badges faster
- All negative actions now have a red colored button
- Admins can now see user's device id value
Room Settings
- Owners can now upload logo and background image
Bugfixes
- Fixed crash bug that would happen if a user used a spoiler in chat
- Streamlined writing and publishing events to relays with delays to reduce throttling
- Fix error handling on avatar rendering
- Fix parsing of lightning address and nostr address
- Fix profile badge displays for anonymous users (they wont have badges)
- Fix recent posts display when no posts are presnt
- Fix file uploads in text chat
General
- Kind 3 support for follow/unfollow has been removed as obsolete
- To improve performance, user metadata is now being cached when entering the room
- When clicking the Start Room button, users can now specify the room id
=== Server Logic
Room Updates
- No longer force room to be private when changed by an anonymous user if there is at least one room owner connected who is a nostr user
=== Configuration
- Temporarily disabled ACL based relay access
=== Documentation
- No changes
Thank you for using Corny Chat. Please feel free to provide feedback as github issues, in chat, or on nostr
---
https://github.com/vicariousdrama/cornychat/releases/tag/v2024.10
#foss #devstr
A little less than 20% to go with race under caution at Phoenix.
Byron just pitted before caution taking fresh tires. Logano and Blaney will pit letting Byron move back to the lead
https://i.nostr.build/zuxo9WHL6xNiQfa0.jpg
This was a temporary art installation at the Party House for Nostrville 2.0. The use of negative space and the natural tears complete the look of this whimsically happy lamp.
https://i.nostr.build/R0DkOXL3k7BWaASx.jpg
#artstr
I had such a great time. My brain is still digesting how surreal it was to meet, hang out with, and talk to so many awesome people! The event with Ainsley Costello, Amber Sweeney, Luke Woods and Jo Corso was also an unexpected treat!
i just came back from the future...
lot of people upset about election results. ross is still behind bars. the lizardpeople still run stuff. bitcoin blocks keep being mined. people still enjoying each others company. families and babies bein made.
How is this client lockin? The ability to copy the id means the user can take that to their app of choice.
Suggesting primal is a convenience, sure, and some apps like njump have others, but that to begins a cat and mouse game for implementation options.
NIP-3 OTS attestations dont really solve this issue.
I no longer use kind 3 as a follow list because of these risks, and instead spread across NIP-51 follow sets (kind 30000). Its more flexible but can suffer similar fate just at a smaller scale.
Ive considered NIP 81 relationships hut this is bigger engineering challenge for clients to adopt fully (AFAIK, Corny Chat is the only client using for petname assignments)
This is a great idea and easy to understand abstraction from the deprecated follow list. A caveat though is that it externalizes to relay configuration. Additional features can be built for that for import/export for backups. Im curious of the extent of net reduction in network data consumed through this approach.
It should also pair nicely with any topical lists you've defined. Ive recently sorted everyone I was following into respective topical lists and dropped some in the process. Smaller lists makes for less data being sent to relays for requesting notes then a typical follow list.
Its about curation in layers. Being in control of your own feed takes effort, but is rewarding.
nostr:naddr1qqxnzdenxqmrjwfc8qcnvwp3qgs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgrqsqqqa282xugqg
Mostly in need of clarity on what configurable fields are, nostr requirements/dependencies that must be met before using and walkthrough flows. See my response to Dan on what is getting me tripped up
We'll get there. I want this for sure and its totally feasible. I know there are projects using it successfully today, I just want to make sure we get this as smooth as butter
Just seeing this now while vetting your pubkey. This is actually by design. Every link that is rendered in the chat provides either 1 or 2 clickable portions. If there is no querystring, then its one clickable link to the target. If the link contains a querystring, then everything before the demarcation is a link going to the resource without the querystring, and the second link is on the querystring portion for the entire url. There is a slight styling difference, which could be improved to make it more clear
Oddbean new post about login | logout
Notes by Vic | export