Firefox and "NOT SECURE" -- what's the plan?

Open
#88 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
10/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
security, web-dev

Research direction

Start by reading the linked background post and CNET article, then review the seven issue comments for any agreed direction. The issue names no repository files, tests, implementation entry point, or acceptance criteria; it would need a maintainer decision defining what change, if any, is wanted before work could be considered done.

Written by the indexing model from the issue text.

Description

See this post for background.

I read in the CNET story (warning self-playing video) earlier in the week that Firefox isn't labeling HTTP-standard sites as evil incarnate.

Is this true? Is it something they are perhaps willing to commit to? If so, I will probably switch to Firefox. I am, unfortunately, a Chrome user.

Note: Posts like this tend to draw trolls. You know who you are. Restrain yourself! 💥

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.