어그로 끌어서 죄송합니다. (딥러닝 기반 유튜브 콘텐츠 필터링) - 서버
주제 : 딥러닝 기반 유튜브 콘텐츠 필터링
- 안드로이드 앱 [노그로]는 영상의 제목, 썸네일을 해당 영상의 내용과 비교, 분석
- 연관성이 떨어지는 어그로성 영상이라고 판단될 경우 필터링
- 어그로성 마케팅에 대비해 주제와 연관성이 높은 영상만을 추천
- 영상의 분석 결과 시각화 (워드클라우드 등)
- 조회수가 곧 수익으로 이어지는 유튜브 구조
- 자극적인 제목과 썸네일로 클릭을 유도하는 일이 빈번, 트렌드이자 논란
- 사용자가 원하는 영상을 찾기 위해 낭비하는 시간이 늘어나는 문제
본 프로젝트를 통해 어그로성 영상을 필터링하여 사용자의 혼란을 방지 자극적인 콘텐츠로부터 사용자 보호 및 건전한 유튜브 문화 생성 목표
- 딥러닝 기반 연관성 분석을 통해 검색어와 연관성(일치율)이 높은 유튜브 영상 제공
- 사용자의 취향 분석을 통한 영상 추천
- kotlin , 안드로이드 스튜디오, aws EC2, python, YouTube API
-
필요성
-
자극적인 콘텐츠로부터 시청자 보호
-
건전한 컨텐츠 문화 형성
-
원하는 콘텐츠를 찾기 용이하여 시간 절약
-
차별성
-
모바일 환경에서 구동되는 어플리케이션
-
수정수정 ~~~
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom!
- Create or upload files
- Add files using the command line or push an existing Git repository with the following command:
cd existing_repo
git remote add origin https://lab.hanium.or.kr/22_HG076/22_hg076_server.git
git branch -M main
git push -uf origin main
- Invite team members and collaborators
- Create a new merge request
- Automatically close issues from merge requests
- Enable merge request approvals
- Automatically merge when pipeline succeeds
Use the built-in continuous integration in GitLab.
- Get started with GitLab CI/CD
- Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)
- Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy
- Use pull-based deployments for improved Kubernetes management
- Set up protected environments
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to makeareadme.com for this template.
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
Choose a self-explaining name for your project.
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
If you have ideas for releases in the future, it is a good idea to list them in the README.
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Show your appreciation to those who have contributed to the project.
For open source projects, say how it is licensed.
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.