Nice! @[email protected] Another one to link on the hub
Nice! @[email protected] Another one to link on the hub
It’s currently linked on the /generators page at the top, alongside plugins + templates. But I agree that’s not ideal… Maybe I should add a drop-down menu type thing, so there can be more options without cluttering the header with too many buttons
I currently do pick a text color that contrasts with the background color, but that doesn’t work if a background image is specified. For that, I have a brightness and blur backdrop-filter
. But yeah, won’t be perfect - I can always adjust things later if needed, so there’s no harm in releasing this as-is for now, I think
Oh cool, then I guess I fixed another related bug
IIRC there was another bug report of yours where setting document.body.innerHTML = ""
would break error reporting. I can’t find that post, but just letting you know via this one that that bug should be solved now. Thanks!
hao return to minimized with just an icon after having touched it and expanded the bar
Fair point! Just added an ‘x’ button to close re-hide it.
hao choose minimized icon?
I did think about this, but I think (for now at least) I’ll hold off on this. My thinking here is that ideally it would be something distinctive and consistent across generators so it’s easy to find. A big part of how a lot of people got introduced to perchance was being curious about what that “edit” button means. They click it, and then everything is a blur for two weeks and suddenly they know how to code (a bit). I’ll keep the headers on my generators for this reason, but I think in that particular respect (i.e. helping newbies get introduced to the platform) it should still be fine to use minimal header mode, so long as there’s a distinctive icon that people notice a few times across separate perchance visits before finally getting curious enough to click it.
Ah, thanks! Fixed.
Hmm, I’m really not sure. You checked your spam folder, I assume? I just tested with an email address from temp-mail [dot] org and it worked fine for me.
I’m curious if you’re using e.g. gmail/hotmail/etc. or some other domain? Or e.g. a university/school domain? Shouldn’t make a difference at all, but if you are using something other than gmail/hotmail/etc. then that would be handy to know so I can triangulate on issues other people have had, and run some more tests.
I can’t replicate this. Can anyone else who happens to read this post try replicating? Maybe a ChromeOS thing? Can you double-check in guest mode, in case it’s e.g. dark mode extension or something?
The generator list API is cached for about a minute or something like that, so they probably deleted their generator a few seconds ago.
Well done! Really nicely and functionally designed. And along the way you’ve brought a lot of issues to my attention (several of which I’m still trying to think about how to best solve), so extra kudos!
Agreed, something like that would be handy. Something you can do in the meantime, which isn’t ideal, but may be useful is use a script tag with a type
set to something other than text/javascript
and module
, and then replace its outerHTML
with its innerHTML
:
<script id="foo" type="text/plain">
[foo]{1|2|3}<b>hi</b>
</script>
<script>foo.outerHTML = foo.innerHTML;</script>
https://perchance.org/wewmm37d60#edit
And here’s an example where we put markdown in the script:
<script id="markdownScript" type="text/plain">
# Hello
This is *markdown*. [Notice that](https://perchance.org/welcome) Perchance syntax is ignored in here. {1|2|3}
* That's because the perchance engine doesn't parse the text that's inside scripts.
* You just need to set the 'type' attribute to something like text/plain or text/markdown to indicate to the browser that it shouldn't be executed as javascript.
</script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/marked.min.js"></script>
<script>markdownScript.outerHTML = marked.parse(markdownScript.textContent)</script>
https://perchance.org/nw95zgceei#edit
@[email protected] @[email protected] I figure y’all might be interested in this technique. When I get around to cleaning up all the plugin pages, adding dark mode, etc. I’ll probably do something like this. Mostly better than defining plugin explanations in the lists panel, since that bloats the importer’s generator with that unused content. The downside is that you can’t use any Perchance syntax inside the script, so you may need to use multiple scripts with gaps in between, and use Perchance syntax within those gaps.
Better to use this than the jsdelivr script tag though: https://perchance.org/markedjs-plugin since that way it doesn’t require an extra request during page load, which your whole page would have to wait for. Example using the plugin: https://perchance.org/zf36rys0c6#edit (same as above code block, but with marked = {import:markedjs-plugin}
in the lists panel instead of the <script>)
Thanks for the suggestion! I’ve added a feature to the t2i-framework plugin so the comments have a little red notification icon thing when new messages come in. The one catch right now is that you have to have visited the channel at least once to start getting that ‘unread’ notification icon. I’ve also added the ability to add side modules if you’re on desktop/laptop (i.e. wide screen) so you can have multiple channels open+visible at once.
Thanks! This should be fixed now - let me know if not, or if there are any related / follow-on issues.
You might be looking for one of the following:
output
[p = person.selectMany(2).joinItems(", ")] // outputs two names with comma between, like "Jane, Bob"
[p = person.selectUnique(2).joinItems(", ")] // same as above, but ensures that the two selected names are unique
[p = person.selectUnique(2), ""] The first selected name is [p[0]] and the second is [p[1]]. // example of selecting two names, and then using them individually later on in the output
If not, let me know what specifically you’re trying to achieve and I or someone else here will try to help
I’m not sure who owns that generator, but I noticed that the error messages weren’t very helpful, so I’ve just added some code to fix a few bugs (main fix was that correct line numbers are now given for nodes that were cloned with myList.createClone
). Hopefully the generator owner will notice the error and fix them. If they have a feedback button anywhere you could use that to send them feedback.
I think it may have been swept up when I was trying to stop comment plugin spam. I was dealing with a DDoS at one point but IIRC that was not Tor-related. I’ve made an edit to the firewall rules now so Tor blocking should be targeted to just comment plugin message-sending requests. Thanks!
Thanks! Fixed.
Today I learned - thanks! I was thinking about how annoying all the internal/plugin logs were recently, but didn’t know about console.debug
(I was going to fix via a localStorage
flag). Let me know if there are any stray logs that I’ve missed in the engine, or commonly used plugins.
I’ve kept ai-text-plugin input logging for each generation request, since I use that all the time (to make sure I’ve not made any mistakes constructing my prompt), so I assume others will find it useful too.
Also, since I know you’re interested in this sort of thing: Today I also removed the
<div id="output-container"></div>
inside the body to bring things closer to being “just HTML+JS+CSS”. So everything in the HTML editor goes directly into the<body>
. For backwards compat, the<body>
element hasid="output-container"
, and beyond that there were only a few generators that had to be semi-manually fixed. Small improvement, but that was annoying me for a long time. The bigger and more painful task (in terms of ensuring backwards-compat) is that square block vs script tag escaping stuff 🥲