I tried making this myself with magazine styles, but it didn't work. As a native feature, it doesn't exist yet.
this post was submitted on 02 Jul 2023
5 points (100.0% liked)
/kbin meta
639 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
The problem with using a magazine style is also that it would only work for people viewing the content in the browser, on the same instance.
Lemmy has its own spoiler syntax. Hopefully Kbin will support that at some point so that spoilers just work regardless of where you're reading from.
If you see a spoiler here...
You're either from the future or a Lemmy user
May I suggest something ancient like ROT13? Bookmarklets are easily made to be able to decypher such content, or at a pinch it can be copy-pasted to a tool elsewhere. e.g. Spoiler for some film or another; ROT13: Arb jnf n cbgngb gur jubyr gvzr.
Advantages: Still looks like text. Reasonably identifiable as some kind of letter cypher, which will allow the reader to guess that it might plausibly be something like ROT13 even if unlabelled.
Disadvantages: Old enough to confuse new people. Eventually someone will learn to read it without tools and get spoiled anyway.
Edit: Also not ideal for International users, but I assume there are other cyphers where ROT13 won't work.
Base64 works as well, there are easy encoders/decoders like this one which can work in a pinch.
You can have something like Base64 spoiler: Sm9obiBkaWVkIGluIHNlYXNvbiAyLg== which would decode to John died in season 2..
view more: next ›