krisseck / hashtag-wall-server Goto Github PK

Handled by setting the hashtag parameter in config.js

Hi

I was wondering if there is a detailed step by step installtion process available. I'm a bit of a newbie

Hi,

I noticed that the API returns null for the keys "userId" and "user".

{
"id":4876,
"link":"https://instagram.com/p/ByDwc_qJ6er",
"image":"https://instagram.fham2-1.fna.fbcdn.net/vp/4e11180a1b33ea72df775b795978b21b/5D931DFA/t51.2885-15/e35/60418334_349955962371961_906103412093607567_n.jpg?_nc_ht=instagram.fham2-1.fna.fbcdn.net",
"caption":"#ct_espartanos #bjj #bjjforlife #jiujiteiros #jiujitsulifestyle👊 #jiujitsuportoalegre #artemarcial #ArteSuave #jiujiteiros #jiujiteirosincero #muaythaiportoalegre #muaythailifestyle #Muaythai",
"type":1,
"source_id":"2054698953741936555",
"created_at":"2019-05-29T19:47:04.000Z",
"updated_at":"2019-05-29T19:47:19.000Z",
"userId":null,
"user":null
}

According to the screenshots, the api should return the username. So I checked the demo and it indeed does not show the username anymore.

Is it intended or did Instagram changed some policies?

Trying to test the demo, but API calls involving delete functionality are not working (loading forever and then failing).
Some URI tested:

• http://hashtag.polso.info:8080/admin/delete/27828
• http://hashtag.polso.info:8080/admin/deleted-posts

Looks like first commit was last month, so I'm assuming things are just not fully working!

Let me know if I can be of assistance. Would love to use this at my wedding in a few months. :)

EDIT: It also appears as tho I'm unable to scroll on the demo "client" web page.

Currently the promise chains in cron are broken by throwing errors. There is probably a better way to handle this.

Have a global setting in config where you have to first approve posts before they are displayed.

Now when you delete a post, in the next cron run it can be inputted again. Maybe make a new deleted_posts table that is checked on cron runs?

iot@iot:~/.pm2/logs$ ls -sh cron-out.log
14G cron-out.log

cron.js creates really large log-files (see above). It's not a fix, but if you start the cron job like this pm2 start cron.js -o "/dev/null" -e "/dev/null" no log files should be created and precious diskspace is saved.

Twitter integration does not include any images in the posts, maybe it is just a typo somewhere in the module?

The testing support currently is really simple, should update it to include inserting/deleting posts etc.

A function to ignore specified users

• Database table ignored_users
• Ignored users' new posts will not be inputted in to the db
• Admin interface where you can ignore new users and shows a list of existing users

Thanks for the project! Is it still up and running?

Implement pagination for admin interface, now the list can be pretty huge.