TheOdinProject
Ruby on Rails: Replace Flickr API Project
Checks
- [X] This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
- [X] I have thoroughly read and understand The Odin Project Contributing Guide
- [ ] Would you like to work on this issue?
Describe your suggestion
Problem
Many users have reported encountering issues with the Flickr API project within TheOdinProject curriculum. Specifically, problems include difficulties with signing in, logging in, and frequent "Account creation failed" errors.
Issues with Flickr
- Account Creation and Login Problems: Users often face errors when attempting to create accounts or log in to Flickr.
- Outdated Platform: Flickr is considered somewhat outdated, which may affect the learning experience and the relevance of skills acquired.
Solution
I suggest that we can use some other API, for example Imgur's API. Its modern, user-friendly, and more widely used.
Path
Ruby / Rails
Lesson Url
https://www.theodinproject.com/lessons/ruby-on-rails-flickr-api
(Optional) Discord Name
tornado_77
(Optional) Additional Comments
I will see if I can help depending on where this issue goes.
Yeah I agree, it is alot of work. But I think it will be worth it. I myself am stuck on that project.
I will try to do some research on how we could change the lesson (or if we even should) to Imgur API. I am also stuck on this project right now.
This issue is stale because it has had no activity for the last 30 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I didn't really look into it much. But I have seen more and more people having issues with Flickr on the discord server.
I'm not on the project yet - if the inspiration is still there we can circle back to it. Might take me a bit to get there. Let me know if you want help on it at any point, I can help. I just don't have the capacity to the task on fully at the moment.
@weeezik Sure. I am currently not working on this at all. But yeah the problem still persists. So any help on this would be great.
This issue is stale because it has had no activity for the last 30 days.
New issue that bumps this in priority a lot: Flickr now requires users to be subscribed to a Flickr PRO premium account in order to generate API keys. As opposed to the mysterious account creation issue that only effected some users, this will affect all users.
Link to discord discussion: https://discordapp.com/channels/505093832157691914/514204607770001411/1351113608364560404
Hmm yeah, that does make this issue much more prevalent then. It basically means that one of the projects in the curriculum is now locked behind a user being on a paid subscription to a third-party application.
Hello there. I have done some research for a replacement. The best I came up with is Pexels.
Features free account creation and free API key generation, with a limit of 20.000 requests per month, plenty for the curriculum's needs. Should I go ahead and write some instructions for setting up an account, API key acquisition etc?, in the style of the current lesson instructions for Flickr?
Here are the Pexel API docs.
There is also a gem that simplifies the API calls, it's the pexels-ruby gem.
I have re-written the lesson with instructions to use Pexel instead of Flickr. On my curiculum fork I deleted the old project_flickr_api.md and added a new file, project_pexel_api.md.
However now I am unsure on how to proceed. Should I just go ahead and do a PR? I couldn't figure out how the md files are pulled by the main TheOdinProject app to be rendered as content. Does it expect the old file name or will it render the apis folder contents?
@CouchofTomato
@NikEmman Thank you for your interest in contributing on this.
Don't delete the old file. Instead, move it to archive/. To actually get the new project on the site, you'll need a PR to the main site repo that removes the old lesson from the Rails course lesson fixtures and adds the new one. But you don't have to worry about that just yet. Assuming you have some content that's ready to go, you can go ahead and PR that. Once it's reviewed and approved, then we can talk more about the process for getting it to actually be on the site.
Thanks @JoshDevHub . I picked the issue because it was flagged as stale, thus assumed no-one was on it. You are absolutely right, should have waited for the assignment. Hopefully I didn't waste anyone's time.
Oh you didn't waste anyone's time. I edited my post after noticing the above conversation with timato. You did everything fine 😃
This issue is stale because it has had no activity for the last 30 days.
The API key is now only available for pro users - you have to pay to complete this element of the course.
This issue is stale because it has had no activity for the last 30 days.