Im not concerned with alternatives I want nostr to be concise and be the best option for all users. Just because blogs work as articles doesn't mean the job is done and we should leave it that way.

Reply to this note

Please Login to reply.

Discussion

Then I would get in touch with nostr:nprofile1qqsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsfqhde8 the creator of npub.pro, nsec.app & nostr.band. it's entirely possible a blog kind could be added if there is demand, then you just need an editor for them. Probably not that hard to modify current long form article editors, since the content is virtually identical.

Or even a change to the current nip to put a tag on the event that specifies the kind of long form content would achieve a similar effect, not break previous notes and allow old blog entries to be replaced with the new blog tag. That's the best way forward imo.

Should there be any different fields/tags in blog events (except for different kind number)? A different way to display them, different client UI?

Client UI for creation stories be relatively the same. A switch to pick between big and article would be great. (Adds a tag to the event, indicating a blog.) Then you can filter feed by all articles or just blogs.