@Giorgio-Chiodi said:
We noticed that using the browser's notifications has its limit, since they only work when the app is open on the mobile device. Which kind of beats having the notifications altogether.
This is where pushbullet itself would come in. Currently talking to someone at pushbullet over this, but it's lower priority at the moment, as it is not on our immediate roadmap.
@frissdiegurke said:
so it's best practice in my mind to make a single plugin for each markdown-extension instead
I completely agree with this assessment.
@frissdiegurke The whole drafts feature as-is at the moment is to combat losing your progress in the event of a browser crash or errant keystroke.
Re: @psychobunny's comment, I'd definitely be in favour of re-opening composers (minimized) of any open drafts...
@erich At present, the honey pot module I made is for other node application to take advantage of it. So it's more like an intermediary to help other plugin writers get plugins out the door.
The one that I do know is in development is @bentael's spam be gone plugin
it would be awesome if there would be a some thing like show all users * or show all that are not in this group ^
some kind of regexp / wildcard search thing
just a thought
[image: CMPVHky.png]
@psychobunny Certain pages tell you to click to refresh (unread for example). So would be nicer if rather than that, a little tooltip at the very top similar to facebooks iOS app said new replies, you pull to refresh the list and they appear. Think there's somewhere else too, but I don't remember.
It's good for seeing all past notifications, but it could be extended in the future to include "notable topics" maybe stickies or "promoted topics", things like that. I'm not sure how many the drop down shows at any one time, so if you're mr popular, you might miss a few because it only shows the last 10 for example.
Hello @igbuend, welcome on board
+1 for SVG support.
For now if you want to get SVGs working, add 'image/svg+xml' into the array within src/controllers/admin/uploads.js:48
EDIT: created pull-request...
@planner like I said, there are specific reasons the client wants the IP to be associated with each post. I can see either argument, but I can't agree it doesn't make sense. I do think it's valuable to have as much information tied to the post level as possible for forensic reasons.
