From notifications if you first scroll down the home feed, it takes you back to the top if from notifications you press the lower left home icon.
Unsure if related tho.
#[0] recommend
👮♂️ Please come with me sir. AI has flagged you as a potential future suspect.
#[0] run
I genuinely tried to help you here. Proceed however you wish - I’m no gate keeper.
If you are actually serious, my 4-5 suggestions in previous replies are a solid step forward in assisting your needs. We need a few key client app features to help allow greater identity and posting flexibility and control.
I think if you explore Nostr from a more technical side to understand it’s architecture better, you’ll appreciate how the first step is to run your own relay and promote it for whatever use case you want.
If people care, they will join and stay. If people don’t care, they don’t have to worry either. And if your relay shuts down and people have their data, they can just re-submit it to a replacing relay. There is no de-platforming or censorship.
Just keep in mind too that no relay operator wants to host content where they have to moderate or deal with potential legal issues or even server host content compliance. Explicit content is often unwanted heat. I don’t make those rules up.. it’s society.
Nostr is still built for smaller communities and groups to form. It’s early and today it’s mostly homogeneous - but in a year it will have already have themed relays and be far more broken into community and content types.
I’m guessing the approach will be a new new event kind. Kind 4 is still useful to have as an option. It just doesn’t provide the modern privacy we need.
This could work as an approach. TBD. https://simplex.chat/#how-simplex-works
It might be nice to understand if polls are a fix zap amount to vote, or a sum of zaps contribute to the distribution. The former was what I had seen before.
I think it will be confusing without clear UX - and people will feel betrayed or whatever if people can vote twice, etc.
And to clarify.. they can use kind 1 for general content (non-explicit profile picture, non-explicit banner, likely toned down profile, etc). But as soon as it becomes offensive and blasts unwanted content into general feeds - it will be a problem. We’ve had porn blasted in general feeds and people hated it… people even stopped using Nostr altogether.
Maybe they should have two accounts. One for general use posts, and one for explicit. Or just use one, but have toned down imagery. And only post explicit content to targeted relays. Problem mostly solved.
Nostr is a Protocol to support many use cases… not a dump everything in kind 1 because I think I need to. If people care enough, apps will add support for kind 69 or whatever you propose.
Sure. That’s my point. Kind1 is general use short message content. It’s not paywalls, galleries, long form movies, live video chat, a chat room, etc.
If you want to funnel specific use content, perhaps with paywalls and other aspects, use a different kind.
Or, as I suggested, host a purpose specific relay for the content. People opt-in then by enabling that relay - even for kind1.
They 99% of population do not want explicit and general content mixed. You can try, but I expect it will fail spectacularly and will result in endless reporting or user bans from relays.
Another idea you could suggest is a relay metadata flag for explicit content - then clients can know connecting to that relay is going to expose clients to that kind of content.
I’ve suggested a lot of ideas for you. All are valid for the network to support in the long term, and are solid an alternative to some formal content rating system.
I still don’t understand your proposed problem statement or desired outcome - except flood kind 1 today with mixed general and explicit content because you think it has to be in a single stream - and that makes no sense.
Nostr is organically building out its personality. #[0]
The kind problem is generic and applies to all notes.
Kind 1 will always sadly be a dumping ground for bots, automating, testing, random content, advertising, etc. Because it’s the easiest and widest audience.
If you want a dating app.. you don’t need kind 1. If you want only fans, you don’t need kind 1 - keep a non-explicit kind 1 account if you like - which is how Twitter is often used today in addition to an adult account elsewhere.
I’m not suggesting a single kind either. It depends on the use case.
Again. Separation at a relay level makes a lot of sense and makes almost all this simple and easy today without changes. Relays are dumb and easy to stand up - you are still censorship resistant with this approach. It’s not banishing the people or content. It’s just centralising the communities.
Another feature you may wish to push for is ability to select which relays to publish to. And multiple accounts in a single app. Both useful for this. This will come anyway.. but it’s valuable for what you want to achieve.
I’d love to understand the real world use cases or user stories you are looking to add or improve support for.
It is better searchability?
It is enabling more explicit content on Nostr without impacting the current/future user base negatively?
Is it for a specific application, like only fans, or an adult Nostr network that’s opt-in? Does it have to use kind 1 short notes - or can it be a new kind?
Is it how to support adult businesses on Nostr, and benefit from lightning or tipping?
Is it to improve the client app filtering capabilities? What problem exists today specifically? What does having labels that are longer than most short note content to begin solve? How does the UX even work - especially mobile?
Global feeds will effectively become “combination of my relays feed” soon as the network splinters and grows 100X. If you connect to relays with content you don’t like (media or just personalities), try another relay and disconnect from the undesirable one. If you want explicit content, start a relay that specialises in it and ask people to join.
I think a more targeted problem statement,and an outcome you’d like to work toward is a good next step.
Yeah. I considered that, but how to pick which capitalisation then to display. Ha. Maybe just lowercase it all. Or predefined matches like sentence case place names.
Yeah. I haven’t overhauled the logic since Nostr grew. So a single post with the same hashtag multiple times also skews data. When I have time. And the same user posting a hashtag a lot during a period.
Yep. Nostr data across 100 relays. Mild filtering - basically common spam.
Hashtags aren’t used a whole lot, so the numbers are typically smaller data sets - so it’s easier for hashtags to become popular.