MagiCircles / MagiCircles/SchoolIdolAPI
The Twitter needs a retool
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 151
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
- There are too many people running the Twitter OR you have no communication whatsoever. People need to pull out or you need to start lowering the staff. Several times, especially for birthdays, there's always 3 posts for the same thing because no one bothers to check to see if someone had already posted about it. Either you need to cut down on staff or you need to figure out a better way of organizing who posts what.
-There have been several instances lately where you have passed off old news as current news because you didn't even check.
-Several typos and obvious copy paste mistakes. Deleting them might look bad to you but if it was to fix a simple typo or a bad string of words there would be better reception to the tweet overall.
-Do you have to use emojis every time? If getting the news out quickly is important to you, it would save time. Your icon and Twitter name alone will get enough attention.
- You have NO actual translator. This is my biggest complaint. Right now you're using the Bing translator provided by Twitter which is FAR inferior than Google Translate which will usually get most of the text right or close to understandable. Using Google Translate would be better than Bing if you can't get anyone to actually translate for you. For example, this tweet is absolutely embarrassing. How did you mess up something so simple as "Congratulations/Happy Birthday Shuka!?" https://twitter.com/schoolidolu/status/897837356304093185
I'm sorry if I sound harsh, but I know for sure people have brought these up before and you've responded to them on Twitter in the past, but I've seen very few changes. I need to see more of an improvement because I'm losing my trust in you when it comes to getting the best news for SIF.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. The issue describes broad Twitter staffing, copy-editing, fact-checking, emoji, and translation concerns rather than a scoped repository change, so a contributor cannot identify a start point or a verifiable done condition.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100