Missing scheme for flickr?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
Research direction
Use the Flickr scheme list and the two oEmbed examples in the issue as the starting point. Add support for https://flickr.com/photos/* without www.flickr.com, then verify that non-www Flickr photo and gallery URLs are recognized.
Written by the indexing model from the issue text.
Description
Flickr contains the following scemes at the moment:
- http://*.flickr.com/photos/*
- http://flic.kr/p/*
- http://flic.kr/s/*
- https://*.flickr.com/photos/*
- https://flic.kr/p/*
- https://flic.kr/s/*
- https://*.*.flickr.com/*/*
- http://*.*.flickr.com/*/*
Shouldn't we add: https://flickr.com/photos/* (without www.)
The flickr oembed endpoint seems to support non-www URLs:
- Dominant language
- PHP
- Stars
- 1.4k
- Forks
- 773
- Avg merge
- 11h 21m
- Merged PRs (30d)
- 14
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from iamcal/oembed
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
iamcal/oembed#843 · 2 comments ·
Maintainers usually reply within 1 day
-
stale
Difficulty 1/5 Under an hour Newbie friendliness 72/100
iamcal/oembed#801 · 1 comment ·
Maintainers usually reply within 1 day
-
stale
Difficulty 5/5 Over a week Newbie friendliness 35/100
iamcal/oembed#686 · 4 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
stale
Difficulty 5/5 Over a week Newbie friendliness 25/100
iamcal/oembed#676 · 9 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
stale
Difficulty 5/5 Over a week Newbie friendliness 20/100
iamcal/oembed#614 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
UX
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ProfessionalWiki/NeoWiki#1573 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day