what if you encode chinese text this way? does it compress as much?

yeah, I guess you can add your own dictionary and the llm will work with that, chinese is probably the most efficient for this case at the moment. it's funny that to westerners gibberish chinese is almost indistinguishable from normal if you don't read it but you can tell giberrish english easily. do chinese people not see when it's just giberish latin alphabet?

so this uses chinese chars to encode english? does the chars mean things or are they like chinese giberrish?

because it's a logo, and he's not beeing paid and doesn't want to be sued. maybe create the graphics without branding so it's more shareable and make the brand use it first so they have the credit. just my 2sats

oh, well yes, illustrator is a shitshow since forever. adobe should have kept freehand as the vector tool when they bought macromedia. much more intuitive with that sort of stuff.

of all the years I worked doing design, InDesign was my absolute favorite tool. very misunderstood. most people use it wrongly as if it was a sort of illustrator where in reality it is an automation beast. you're not supposed to go and fiddle with things directly, you need to use styles for everything. once you understand that concept and the power it gives, you'll find it all makes sense...

Then the relay should send the auth from the get go and not wait for a sub at the very least. retaining and resuming should be the new norm that all clients expect IMO, they don't because it wasn't a thing

nostr.land is as far as I've seen the only relay that resumes subs if sent before auth. the auth dance with most relays is just tiresome. this is how all relays should behave. you send the req, it asks for auth, you auth, the req resumes. <3 bravo

How so? The only downside i see is that it's not actually trivial to release events based on future timestamp. Do you see this as enough for ddos? Or what's the angle?

that could work but would require significant amount of updates on clients and relays, and relays could also be incentivised to rugpull. I just thought of this because it is very trivial and the fact that relays keep relaying events with future dates in all reqs is sort of a bug… this would also fix that behaviour.

the point is you wouldn't know they're scheduled

it should return by id, and you could send a delete request. if it's very private info, then your own server is always the best option