What type of PR is this? (check all applicable)

• [x] Feature

Description

This adds notifications for organizations! 🎉

Implementation details:

• Anyone who is a member of the organization can view the org's notifications.
• Any org member who views the org notifications will mark them as read.
• The routes are: /notifications/org/:org_id and /notifications/comments/:org_id. This keeps it flexible for people who belong to multiple orgs.
• There is no filter for posts because orgs can't follow people (and therefore cannot receive notifications for new posts).
• Orgs can receive new comment and reaction notifications on their org posts, as well as notifications for new followers.
• Org notifications are not counted in the bell icon.
• Notifications can belong to either a user or an organization. One or the other, not both. I could add a database constraint but that would require some custom SQL. Not sure if it's completely necessary.

One feature I forgot -- I remembered just now while writing is -- is the ability for orgs to send a new post notification to their followers. I can add this in if we want. Don't think it would take too much time. Just added this 👍

Related Tickets & Documents

Resolves #1222

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Mobile View

Desktop View

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Streak badges 🎉

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Adding "OP" badge similar to "ASK ME ANYTHING" in the comments for original poster

Related Tickets & Documents

#403

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Add base functionality for autosaving drafts

Related Tickets & Documents

https://github.com/thepracticaldev/dev.to/issues/442#issue-353140423

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

This feature gives users the ability to input their experience level in order to modestly affect what they see in their home page.

Currently if you are a very experienced developer (a self-described 9/10), the home page may not be as useful to you because a lot of the content can trend towards the more beginner stuff due to volume of readers. This provides some customization in order to have a slightly more relevant home screen.

Experience level for a post will be voted on by the crowds. Currently it is for mods, perhaps this could be expanded but we wouldn't want to fill the user experience with too many options for the casual user.

As we see how this goes, we could complement this functionality with inferential signals to help, but in general it's nice to give users the power over their experience.

Added to /mod

This is done by voting to produce an average via the wisdom of the crowds.

For the end user, it's a pretty silent PR, though we could ultimately do more things with the site's mechanics now that we will have a decent approximation of how advanced the content is.

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [x] Documentation Update

Description

I use Blogcast to generate audio versions of my articles, and as Dev.to doesn't allow raw embeds, I figured out I'd try to add it.

(DISCLAIMER: Blogcast is not a free product ($0.50/article), and I'm the creator. I'd totally understand if any of those things made you reject the contribution. Just wanted to contribute something, no hard feelings 😄)

Related Tickets & Documents

• N/A

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

• N/A

Added to documentation?

• [ ] docs.dev.to

• [ ] readme

• [ ] no documentation needed

• [x] liquid tags documentation page

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [x] Feature

Description

This PR adds milestone notifications! Milestones are achieved when your post reaches the following:

• 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144, 524288, or 1048576 total views
• 64, 128, 256, 512, 1024, 2048, 4096, or 8192 total reactions

This feature accounts for users and organization posts, and is flexible for any other sort of milestones we want to add.

Related Tickets & Documents

Resolves #1647

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

It appends new gifs to generate for milestone notifications

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

This is a concept feature which will live in private beta for a little while. It will help some users with specific needs and act as a test ground for general rollout features. This is the basic first cut just to get an idea into the universe.

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [ ] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this?

• [x] Feature

Description

This adds a few more success/celebration gifs to the random gif file!

Related Tickets & Documents

N/A

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [x] no documentation needed

What gif best describes this PR or how it makes you feel?

Here's all the ones I added. They all are a good representation!

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

For posts published within the day, indicate how many seconds, minutes, hours ago the post was made.

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

This PR does two main things:

• embeds a ISO 8601 timestamp in each comment-date tag
• displays such timestamp as a title (hence triggered by hover) with a string converted to the the user/browser's locale

It contains a few additional things:

• I've moved .eslintrc.js from the main folder to app/assets/javascripts and set the correct ECMA version. The reason is that my VS Code kept complaining the code wasn't ES2016, which it isn't, it's ECMA 5. The folder with the "modern" JavaScript is app/javascript and it already has its own ESLint configuration file.

• I've deleted app/assets/javascripts/utilities/getLocalTime.js because it wasn't used anywhere and it contained a duplicate function already contained inside initializeTimeFixer.js

A note: I couldn't test it with the "reading list -> comment activity" comments because I'm swamped by async jobs that are taking forever. If anybody has suggestions about what to do with those (beside delete them) please let me know. This is my current situation locally:

Related Tickets & Documents

Closes #406

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

This is how it looks if I set my browser to Italian for example:

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

This styling and markup change provides a useful link for keyboard only navigation users to jump right to the content of the site. More info and WC3 links in the issue!

If there are any concerns with the transition styling I'm happy to remove! In past experience we've found it draws attention for users who might not catch the UI change. Thanks!

Related Tickets & Documents

#1153

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Some users may want night mode for reading or sans-serif fonts for any number of reasons: personal preference, accessibility, etc.

This config gives that option 😄

Sans serif:

There's still work to be done to get night mode looking just right, but this PR should speed that up, as more folks will start using it. Thanks to @link2twenty for the great work on themes.

The implementation of the sans serif css could be done theme style but I wasn't sure, so I did it this way. We can change later.

What type of PR is this? (check all applicable)

• [x] Feature

Description

This PR adds open inbox to users that want to allow others to message without mutually following each other.

The column inbox_type is added to Users with "private" as the default value. The only other option right now is "open." This can be changed under settings/misc.

An inbox_type of "private" retains the previous (default) behavior of DEV Connect, where only users that mutually follow each other can send messages to one another. Now, if you view a user you follow and that follows you, a chat button will be displayed beside the following button.

An inbox_type of "open" displays a chat button on your profile and allows any user, whether you mutually follow each other or not, to open a chat with you on DEV Connect. This works by calling the open_chat method in users_controller and creating a chat channel (if none already exist between you and the user with an open inbox) and redirect you to dev.to/connect/@username.

To-do:

• [x] Add initial message (when a new channel is opened, the default message on top is "You and @mozellmrsprohaska are connected because...", but with an "open" inbox_type that message is false and needs to be changed for clarity)
• [x] Chats that are made inactive because of unfollows can be made active again if inbox_type is open
• [x] Rspec tests for follows_controller pass given changes in show

Related Tickets & Documents

resolves #1460

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Changing your inbox type in settings/misc

Follow Back button for users that follow you

Users that you follow and follow you have a chat button that redirects to the chat channel between you

Manually changing inbox type to "open" for testing in local environment

New chat for users with open inbox type

If you mutually follow someone who has an open inbox, it will prioritize redirecting straight to connect/@username

Added to documentation?

• [x] no documentation needed

What type of PR is this? (check all applicable)

• [x] Refactor

Description

Added username to author sticky nav and about the author sections.

Related Tickets & Documents

Resolves #265

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

About the author section at the end of the article doesn't show up for me in development, but I did make the changes in the file that handles it.

Added to documentation?

• [x] no documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [x] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Added the SEND_LOGS_TO_TIMBER environment variable with false/true default for dev/production modes.

This allows configuration disabling of TIMBER - in "production" mode.

PS : Im not a ruby dev - so someone should really double check before merging

Related Tickets & Documents

https://github.com/thepracticaldev/dev.to/pull/1844 - to streamline production mode for docker build

Added to documentation?

• [x] no documentation needed

[optional] What gif best describes how it makes you feel?

What type of PR is this? (check all applicable)

• [x] Feature

Description

Enabled delayed_job web interface for admins in production (and others) environment.

Related Tickets & Documents

#1857

What type of PR is this? (check all applicable)

• [x] Refactor
• [x] Bug Fix

Description

Fix Delayed::DeserializationError: ActiveRecord::RecordNotFound related to destroyed Follows .

• moved async methods to separate jobs
• added checks to ensure that a follow still exists
• added specs for the Follow model, (for the after_create/after_save callbacks behavior)
• I have also added gem delayed_job_web for the dev environment for debugging purposes

I kept the old methods #touch_user, #touch_user_followed_at and #create_chat_channel_without_delay, #send_email_notification_without_delay which were used before, in case there will be jobs, which were created but were not executed by the deploy time.

Related Tickets & Documents

#1621

What type of PR is this? (check all applicable)

• [x] Refactor

Description

In the current implementation, when an article is destroyed, all the "sibling" articles of the (destroyed) article organization are resaved. Resaving triggers several callbacks, which create a lot of delayed_jobs. That takes plenty of time and resources. There's no need to resave articles, it's enough to bust their cache.

What happens on article destroy after the refactoring:

• instead of resaving organization articles, their cache is busted
• user articles cache is busted asynchronously

Related Tickets & Documents

#1621 Not directly related to the ticket (not fixing errors), but contains refactoring for the related code.

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

Currently crossposted articles take a hit in the algorithm if the post was first published elsewhere. This fixes it.

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Add test for validation badge image

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

Fix Delayed::DeserializationError: ActiveRecord::RecordNotFound related to destroyed Reactions .

* moved async methods to separate jobs

* added checks to ensure that a record still exists

* added specs for the `Reaction` model, (for the `after_save` callbacks behavior)

I kept the old methods #touch_user_without_delay, #update_reactable_without_delay, #occasionally_sync_reaction_counts, #bust_reactable_cache_without_delay which were used before, in case there will be jobs, which were created but were not executed by the deploy time.

What type of PR is this? (check all applicable)

• [x] Bug Fix

Description

Spent a few minutes trying to figure out #1788 and saw Andy's comment after I'd scrolled down... so I inserted the line where he suggested. I suppose there will be a future PR that would intended behavior to send_new_comment_notifications for comments on podcast episodes.

There's some console errors that don't break anything in development that I attached in the screenshots below.

Related Tickets & Documents

resolves #1788

Mobile & Desktop Screenshots/Recordings

@Zhao-Andy comment on 1788

Console

Added to documentation?

• [x] no documentation needed

What type of PR is this? (check all applicable)

• [x] Bug Fix

Description

• Update "save(d)" button states after articles are loaded (in the reading list)
• Did several style fixes required by eslint, and still had to disable several cops for the initializeReadingListIcons.js file

Currently, the states of the buttons are updated several times on a page load which is not always needed in my opinion. But the logic is shared between the homepage, the reading list, and other article pages, so I decided to keep it as is.

Related Tickets & Documents

#1785 This probably fixes #1395, but ideally, I would recommend more research and code refactoring on this issue.

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

There's unneeded complexity in the logic of the feed method, this way what separates each path should be clearer.

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

I came across ArticlesController#feed and noticed that the ORM logic was a bit convoluted and repeated in each if/else clause. Since AR is a lazy and composable ORM, I decided to simplify the logic.

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

A bug was introduced in #1932, leading to unwanted articles in user/organization feeds. @articles scope was not being updated propperly depending on :username param.

Related Tickets & Documents

#1940

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

fix #1940

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

• URLs in the Link and GUID field in RSS have an extra slash. This PR removes stray / from lines 17 and 18.

Related Tickets & Documents

closes #1942

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [ ] Bug Fix
• [X] Documentation Update

Description

I just added GitDocs to "🔑 Key App tech/services" section of the documentation.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [X] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [x] Refactor

Description

• cached flare tag in a variable for the view
• refactored FlareTag
• moved FlareTag specs to its own file

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

I was going through the routes file and found some interesting pages. I also noticed that this page wasn't working correctly, 2 images were not being displayed correctly. 1 fixed the first one, the second one doesn't seem to exist anymore but looking at the url it seems to be a heart GIF. If anyone has a good replacement let me know and I will add it, for now I have hidden it so you don't see a broken image.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Before:

After:

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

Run clean_relative_path! for both a and img elements.

Related Tickets & Documents

Fixes #1976

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

NB: This is not a WIP per se; however, it should not be merged without verifying that it still addresses whatever (unspecified) security concerns motivated the original PR (#1808).

Description

Restore > character to sanitization string for runkit preamble, consequently re-allowing double quotes as a valid JS token.

Related Tickets & Documents

Closes #1937.

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

Rewrite the timeAgo function such that it never returns undefined. The new optional parameter allows the caller to specify what the cutoff is for including a time ago-string. The default value is extracted from the previous code

Related Tickets & Documents

Fixes Issue #1995

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

Yet another Mastodon instance. TBH, the whitelist seems weird. There are so many Mastodon instances

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

There was a typo in the surrogate key header in that it referred to the username parameter as "userame" which affects the usefulness of the key.

What type of PR is this? (check all applicable)

• [x] Refactor

Description

• Added index to articles path, since queries by path are popular when retrieving articles
• select only needed columns for tag colors
• Make fewer SQL queries on retrieving sticky article collection

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

The time ago label in latest page was getting rendered on every alternative posts.

Related Tickets & Documents

#2012

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

No Documentation required.

What type of PR is this? (check all applicable)

• [x] Bug Fix

Description

• added checks to ensure followable is a User or an Organization before sending a notification
• added specs

Related Tickets & Documents

#2041

What type of PR is this? (check all applicable)

• [ ] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Documentation Update

Description

Currently the Dashboard -> Following page tags allow inputing text instead of numbers. Since those are floating points they will be rejected after the submission of the page, using a HTML numerical input with step set to any any valid number (integer or float) is accepted.

This was inspired by @link2twenty's comment on #1346 (in the spirit of submitting smaller PRs eheh)

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Positive numbers

Negative numbers

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

What type of PR is this?

• [x] Bug Fix

Description

"Notificatins" ☹ "Notifications" 🙂

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Restyled the pro dashboard!

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [ ] Bug Fix
• [ ] Documentation Update

Description

Enabled Style/Alias from Rubocop.yml and fixed all the related issues with it.

• Style/Alias
• Style/Attr

Related Tickets & Documents

#2021

Added to documentation?

• [ ] docs.dev.to
• [ ] readme
• [x] no documentation needed

Is your feature request related to a problem? Please describe. The usability of the tags is not fully clear when searching for specific topics and/or subtopics.

Describe the solution you'd like I think the functionality of the tags could be more valuable if they could be organised and grouped in a drop-down list by main topics such as Tools, Programming Languages, Tips, etc; and these, in turn, have detailed subtopics. For example:

Additional context Actual view of My Tags

Is your feature request related to a problem? Please describe. Current account login methods aren't the most suitable for keeping our account access safe.

Using GitHub or Twitter it's ok, but we must remember that they are communities separated from dev.to, they have their own rules and guidelines to determine which accounts must be deleted or suspended.

Also, as they are tech giants it might be hard to contact their support for any issue regarding our account, so losing access to our account in one of those services could mean to lose access to our dev.to account too.

Describe the solution you'd like Adding the possibility to login using an email address, this way we can keep our account access safe and separated from possible issues with any third party OAuth provider.

Describe alternatives you've considered Adding another OAuth provider like Google, for example, a non community oriented service, it's more unusual to have your account suspended, deleted or lost. (This is being discussed in #1595)

Another solution could be to have the possibility to unlink my current Twitter/GitHub account and then linking a new one before logging out from dev.to. But it's not useful if you get your account suspended and can't login to do so.

Additional context I've been experiencing issues with my Twitter account, I have tried to reach out their support but got no response. The best solution I have found is to delete my account and start a new one.

It means that if I didn't change the Twitter account associated with my dev.to account I will lose access to dev.to's account too. (Emailing Dev team for this, since it's not possible from dashboard).

Is your feature request related to a problem? Please describe.

Markdown header tags now have anchor tags, so we can generate tables of contents for the articles.

this encourages more browsable longer form content on dev.to.

optionally, we can make the TOC float in a sidebar.

Describe the solution you'd like

possibly use a TOC generator like https://ecotrust-canada.github.io/markdown-toc/

Describe alternatives you've considered

not doing anything

Additional context

i last filed this request here https://github.com/thepracticaldev/dev.to/issues/183 at my old job's github account. a prerequesite was adding id's on every header, which was done in Nov. its time to revisit this idea!

The <mark> element is useful for highlighting certain words and phrases in text, which reduces the “wall of text” issue. Browsers already render this element using a yellow background.

I ask Dev.to to not strip the <mark> element from the HTML output of articles. Authors can use this element in Markdown normally.

An example of how <mark> improves the readability of content:

Describe the bug I crosspost all my blog posts from my personal blog and in the most recent particular post I used a lot of video tags that were not using YouTube or Vimeo.

To Reproduce Steps to reproduce the behavior:

1. Go to https://dev.to/new and create a new post.
2. In the Markdown, add ` video tag like the one below

<video controls style="max-width: 590px;">
  <source src="https://www.a11ywithlindsey.com/marcy-sutton-clapping-tweet-1fca86b197aff683ffd0a940e70e5737.mp4" type="video/mp4">
</video>

3. In the Front Matter, keep published: false, but add all necessary fields save the post so you can video the page.
4. Go to the post, and see the video. It extends past the blog post container.

Expected behavior A video should have a max-width of the container.

Screenshots

Desktop (please complete the following information):

• OS: Mac Mojave
• Browser: Chrome Version 72.0.3626.109
• Version: 10.14.3

I was thinking about the feature of tag the posts "level" (beginner, intermediate, pro and so on). I thought it could be confusing for the user to determine which "level" is his/her post.

Fortunately, Nowadays, we can use Machine Learning and last NLP methods to do that kind of tasks automatically.

On the other hand, we could use this techniques even for tag posts categories, not friendly comments and so on.

What we need? We would need a big dataset of labelled posts to start working on it.

Describe the bug Uploading a picture, getting an error.

To Reproduce Steps to reproduce the behavior:

1. Go to 'http://localhost:3000/new'
2. Click on '/images/Cover Image' upload image

Heads up:
main_image: is not a valid URL

Screenshots

A related post appears twice after post and comments

To Reproduce Have seen it on this post https://dev.to/psnebc/install-drupal-console-536g and the double post is the "101 Bash Commands and Tips for Beginners to Experts" that appears on 2 different place. Have a look at screenshot but perhaps you can see it visiting the URL

NOTE: both times I tried to visit the URL I got first a "500 Error" and then on the 2nd attempt I would get the actual content. Perhaps its coincidental though.

Expected behavior Perhaps this space should be given to another post

Screenshots

Please add scroll to top button . I read tech blogs daily from dev.to and some blogs are so lengthy so in the end we need to scroll to the top again so if there would be a scroll to top button it would be great for the readers to get to the top easily.

Thankyou

Describe the bug

There seems to be a concept of Teams on dev.to, where posts are written by a member of the team, but are listed under the team name. But the Follow button on such posts does not seem to do anything,

To Reproduce

Steps to reproduce the behavior:

1. Go to 'https://dev.to/vuevixens/hands-on-vuejs-for-beginners-part-6-5e7l';

   The author is Marina Mosti (marinamosti), but the post is filed under a Vue Vixens header, and the Follow button is for Vue Vixens (vuevixens):

2. Click on 'Follow';
3. Go to 'https://dev.to/dashboard/following';
4. You are following neither Vue Vixens, nor Marina Mosti;
5. Wait for Marina Mosti to publish a new awesome post;
6. You are not being notified of the post.

Expected behavior

1. Vue Vixens appears somewhere on your Following page;
2. You are notified whenever any member of the Vue Vixens team publishes a new post.

Unless I misunderstood the whole team thing, that is. ;-)

Desktop (please complete the following information):

• OS: Mac OS 10.14
• Browser Safari 12

When I look at a post, in the many places that we can, I'd like to be able to click on the tags to see more like this. A consistent UX would be helpful on this, too.

Here is a summary view of a post in my dashboard where the tags are not links today

Here they are links, with underlines in the page https://dev.to/t/webdev

Here they are links with a color in the post itself

The about page is not up to date with the Readme

Describe the bug A clear and concise description of what the bug is. Varnish cache first byte timeout error when changing username

To Reproduce Steps to reproduce the behavior:

1. Go to profile
2. Click on username
3. Type new username
4. Press submit
5. 503 first bytes timeout Guru Mediation

Expected behavior A clear and concise description of what you expected to happen. Expected to change my username after hitting submit

Screenshots If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

• Device: 2015 iMac 5k 27"
• OS: macOS 10.14.4

Additional context Add any other context about the problem here.

I've done everything I could on my end but this seems to be a server problem.

• move asynchronous notification methods to separate Active Jobs
• pass entities id instead of an object
• add a check for the entity presence before following up

These methods are suspectible to causing delayed job errors (#1621), so they should be adressed first:

• [x] send_new_follower_notification #2030
• [x] send_reaction_notification
• [x] send_new_comment_notifications

Other async methods:

• [x] send_to_followers
• [x] send_new_badge_notification #2474
• [x] send_welcome_notification #2485
• [x] send_moderation_notification
• [x] send_mention_notification @copasetickid
• [x] send_tag_adjustment_notification
• [x] send_milestone_notification #2804
• [x] remove_all @cyrillefr
• [x] remove_each @cyrillefr
• [x] update_notifications @lightalloy

Describe the bug A clear and concise description of what the bug is.

With Chrome's newly shipped Desktop PWA feature, the 100% square 512x512 image in manifest.json is being loaded instead of the rounded 192x192version. On desktop/macOS, the square version doesn't look as polished as the rounded version would.

To Reproduce Steps to reproduce the behavior:

1. Add dev.to to your desktop from the Chrome menu on Desktop:

• Click vertical dots menu > Install DEV Community

2. Open up the app
3. See the icon 😄

Expected behavior Rounded-corners version of the image should be used for 512x512, not the square version.

Desktop (please complete the following information):

• OS: [e.g. iOS] macOS
• Browser [e.g. chrome, safari] Chrome
• Version [e.g. 22] 72.0.3626.119

A user reported having troubles uploading their cover image in Safari:

"Hey hey team!

Just wanted to reach out cause I think I found an issue with image uploading for Safari.

I was trying to upload a cover image for my post https://dev.to/michael/silencing-the-lizard-brain-4leg but every time I hit done, nothing would show up.

Finally thought to look the console window and saw this on Safari..."

Additional context

• They were using our v2 editor.
• Here's a link to the image too if it helps - https://unsplash.com/photos/RxZUEaa4fik

Is your feature request related to a problem? Please describe. I was looking at my Notification history earlier today and noticed that individual notification cards aren't timestamped, which can be a bit confusing if you are trying to look at a larger notification stream and need to know details about when replies were posted.

Describe the solution you'd like The timestamp of each notification should be visible in the Notifications tab.

Describe alternatives you've considered Opening up each notification, which gets troublesome really fast.

Additional context I'd be happy to take this on, but I'm not sure if it's a feature that was left out intentionally because of some technical limitation. It would be awesome to have that extra temporal context around notifications.

Describe the bug Going in to attempt to finish a long-neglected unfinished post, I get an error 500.

To Reproduce Steps to reproduce the behavior:

1. Go to my Dashboard
2. Click on the title or Edit button of any one of the last three of four unpublished posts
3. See error

Expected behavior View and/or edit post

Desktop (please complete the following information):

• OS: Windows 10 1809
• Browser Mozilla
• Version 66.0b12

It may be relevant that I originally signed up with an account linked to my Twitter handle, then started using my GitHub account, and after submitting an issue relating to that, my account was fixed. Possibly the latter posts were created after my GitHub account became my primary means of logging onto dev.to.

Is your feature request related to a problem? Please describe. Currently, many rubocop cops are disabled (see .rubocop.yml), I think it would be beneficial to enable most of them. In such a way at least the new code will follow the guidelines.

Describe the solution you'd like I like the way how we dealt with the views linting problems (#1842) The similar approach is possible for the ruby code & the rubocop

The workflow I suggest:

• enable 1 cop from the .rubocop.yml
• fix related issues if possible
• if it's not possible (or optimal), add exceptions to the .rubocop_todo.yml (there're already some examples)
• make a pull request

For some cops, there are no violations in the code, so they could just be enabled. I can prepare a list of cops to enable if this issue gets approved.

Describe the bug

A couple of days ago I requested the export of my content on dev.to, the requeste generated the notice message but then I've never received the email.

I went back to check https://dev.to/settings/misc and noticed that the feature is still disabled:

which means that the async job in charge of exporting has not completed. It's either stuck or has died. That's also probably why I haven't received the email.

To Reproduce Steps to reproduce the behavior:

1. Go to https://dev.to/settings/misc
2. Scroll down to "Export content"
3. Request an export
4. Wait

Expected behavior

I'd expect the job to complete in a timely fashion, the email to be delivered and the feature to be re-enabled.

Desktop (please complete the following information):

• OS: macOS 10.14
• Browser: Firefox
• Version: 66

Is your feature request related to a problem? Please describe.

I tried to embed a few lines of code in a post from github. It did not work, but would be cool if it did.

This would be the expected format, I think

{% github https://github.com/johnpapa/vscode-peacock/blob/master/.vscodeignore#L12-L17 %}

Is your feature request related to a problem? Please describe. It's not "frustrating", but I don't know how to remove a notification in my list. I only see the heart and the "save" button. Clicking on the article doesn't remove it from the notification list either (at least for me).

Describe the solution you'd like It would be nice to have an "x" or a "read" button to just acknowledge the notification and make it disappear.

Describe alternatives you've considered I've refreshed the page while on the notifications, and I've read an article linked from a notification. Both actions don't remove any notification.

Additional context Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe. Connecting people who need help editing their post to people who would be up for helping. As described by https://github.com/thepracticaldev/dev.to/issues/464#issuecomment-472454990 and something we've heard anecdotally, it can be intimidating to post.

Describe the solution you'd like We could have people request for help on their posts and send a notification to anyone with a 'volunteer editor' role but we'd need some form of version control or comment system on the unpublished post.

Describe alternatives you've considered Maybe to start, we can simply connect people to one another and have them handle the details off platform.

Currently, some people (myself included) are experiencing long sign in times, which usually end up timing out, thus preventing people from signing in.

Looking at Skylight we can see that the requests take on average 2.7 seconds. Looking deeper in the #github or #twitter actions we can see that there are a lot of repeated queries:

This can definitely be refactored and the amount of queries can be reduced. The main -- and probably only -- file that needs to be refactored is the authorization_service.rb file.

Of course, this should be approached with care, as this affects how people authorize themselves into the app. The sign in process should still work, and refactoring shouldn't cause any weird data leakage (probably hard to accomplish, but good to keep it in mind).

Describe the bug I created a new article and saved it. Then I wanted to change the title and it got me to a page with the title "Search Results - Dev Community" that showed users, while the URL still includes the old title.

To Reproduce Steps to reproduce the behavior:

1. Create a new article
2. Save it
3. Change the title
4. Save it
5. End up at the search results page

Expected behavior To get a new URL and end up in the editor again.

Desktop (please complete the following information):

• OS: macOS Mojave
• Browser: Firefox
• Version: 65.0.1 (64-Bit)