It works, strangely!
EDIT: Besides it not being updated correctly, maybe find a way to combine both @avi_shor's script and yours?
The "json from topic" block does a lot, which is the reason it is a custom reporter. I believe my method is the most efficient in terms of script size, but if @avi_shor wanted, they could do something like
(which would return the same thing.)
Yeah, that works, though an "item _ of _" block with the input "slug" needs to be added for the text itself.
EDIT: This one's slow for updates as well.
this probably isnt allowed
jens said dont access the snap api in a project
oh. i didnt know
why not
when snap got hacked, the thing that hacked it was a project accessing the snap API, jens made this rule to prevent future attacks
this doesnt return anything useful
hmm. interesting. are there any acceptations
i guess there isnt
oh ok
This topic is not about the Snap! API, it is about the Snap Forums API. They are two different things. Furthermore, the rule is not about the Snap! API; it is about accessing the Snap Cloud in a Snap! project.
Good point.
well
the forums might count, if avi shor gets banned, it might apply to the forums
wait hold up. why am i getting banned
the project did not access the snap! API. it abused the browser's Saved Passwords feature.
so cookies?
bruh, it also might have infected the snap website to install viruses
That was not what happened. Jens just doesn't like people talking about (and using) the (private) snap api, especially when it can be used maliciously.