No description available

W3C Strategic Highlights September 2019 This report was prepared for the September 2019 W3C Advisory Committee Meeting (W3C Member link). See the accompanying W3C Fact Sheet — September 2019. For the previous edition, see the April 2019 W3C Strategic Highlights. For future editions of this report, please consult the latest version. A Chinese translation is available. ☰ Contents Introduction Future Web Standards Meeting Industry Needs Web Payments Digital Publishing Media and Entertainment Web & Telecommunications Real-Time Communications (WebRTC) Web & Networks Automotive Web of Things Strengthening the Core of the Web HTML CSS Fonts SVG Audio Performance Web Performance WebAssembly Testing Browser Testing and Tools WebPlatform Tests Web of Data Web for All Security, Privacy, Identity Internationalization (i18n) Web Accessibility Outreach to the world W3C Developer Relations W3C Training Translations W3C Liaisons Introduction This report highlights recent work of enhancement of the existing landscape of the Web platform and innovation for the growth and strength of the Web. 33 working groups and a dozen interest groups enable W3C to pursue its mission through the creation of Web standards, guidelines, and supporting materials. We track the tremendous work done across the Consortium through homogeneous work-spaces in Github which enables better monitoring and management. We are in the middle of a period where we are chartering numerous working groups which demonstrate the rapid degree of change for the Web platform: After 4 years, we are nearly ready to publish a Payment Request API Proposed Recommendation and we need to soon charter follow-on work. In the last year we chartered the Web Payment Security Interest Group. In the last year we chartered the Web Media Working Group with 7 specifications for next generation Media support on the Web. We have Accessibility Guidelines under W3C Member review which includes Silver, a new approach. We have just launched the Decentralized Identifier Working Group which has tremendous potential because Decentralized Identifier (DID) is an identifier that is globally unique, resolveable with high availability, and cryptographically verifiable. We have Privacy IG (PING) under W3C Member review which strengthens our focus on the tradeoff between privacy and function. We have a new CSS charter under W3C Member review which maps the group's work for the next three years. In this period, W3C and the WHATWG have succesfully completed the negotiation of a Memorandum of Understanding rooted in the mutual belief that that having two distinct specifications claiming to be normative is generally harmful for the Web community. The MOU, signed last May, describes how the two organizations are to collaborate on the development of a single authoritative version of the HTML and DOM specifications. W3C subsequently rechartered the HTML Working Group to assist the W3C community in raising issues and proposing solutions for the HTML and DOM specifications, and for the production of W3C Recommendations from WHATWG Review Drafts. As the Web evolves continuously, some groups are looking for ways for specifications to do so as well. So-called "evergreen recommendations" or "living standards" aim to track continuous development (and maintenance) of features, on a feature-by-feature basis, while getting review and patent commitments. We see the maturation and further development of an incredible number of new technologies coming to the Web. Continued progress in many areas demonstrates the vitality of the W3C and the Web community, as the rest of the report illustrates. Future Web Standards W3C has a variety of mechanisms for listening to what the community thinks could become good future Web standards. These include discussions with the Membership, discussions with other standards bodies, the activities of thousands of participants in over 300 community groups, and W3C Workshops. There are lots of good ideas. The W3C strategy team has been identifying promising topics and invites public participation. Future, recent and under consideration Workshops include: Inclusive XR (5-6 November 2019, Seattle, WA, USA) to explore existing and future approaches on making Virtual and Augmented Reality experiences more inclusive, including to people with disabilities; W3C Workshop on Data Models for Transportation (12-13 September 2019, Palo Alto, CA, USA) W3C Workshop on Web Games (27-28 June 2019, Redmond, WA, USA), view report Second W3C Workshop on the Web of Things (3-5 June 2019, Munich, Germany) W3C Workshop on Web Standardization for Graph Data; Creating Bridges: RDF, Property Graph and SQL (4-6 March 2019, Berlin, Germany), view report Web & Machine Learning. The Strategy Funnel documents the staff's exploration of potential new work at various phases: Exploration and Investigation, Incubation and Evaluation, and eventually to the chartering of a new standards group. The Funnel view is a GitHub Project where new area are issues represented by “cards” which move through the columns, usually from left to right. Most cards start in Exploration and move towards Chartering, or move out of the funnel. Public input is welcome at any stage but particularly once Incubation has begun. This helps W3C identify work that is sufficiently incubated to warrant standardization, to review the ecosystem around the work and indicate interest in participating in its standardization, and then to draft a charter that reflects an appropriate scope. Ongoing feedback can speed up the overall standardization process. Since the previous highlights document, W3C has chartered a number of groups, and started discussion on many more: Newly Chartered or Rechartered Web Application Security WG (03-Apr) Web Payment Security IG (17-Apr) Patent and Standards IG (24-Apr) Web Applications WG (14-May) Web & Networks IG (16-May) Media WG (23-May) Media and Entertainment IG (06-Jun) HTML WG (06-Jun) Decentralized Identifier WG (05-Sep) Extended Privacy IG (PING) (30-Sep) Verifiable Claims WG (30-Sep) Service Workers WG (31-Dec) Dataset Exchange WG (31-Dec) Web of Things Working Group (31-Dec) Web Audio Working Group (31-Dec) Proposed charters / Advance Notice Accessibility Guidelines WG Privacy IG (PING) RDF Literal Direction WG Timed Text WG CSS WG Web Authentication WG Closed Internationalization Tag Set IG Meeting Industry Needs Web Payments All Web Payments specifications W3C's payments standards enable a streamlined checkout experience, enabling a consistent user experience across the Web with lower front end development costs for merchants. Users can store and reuse information and more quickly and accurately complete online transactions. The Web Payments Working Group has republished Payment Request API as a Candidate Recommendation, aiming to publish a Proposed Recommendation in the Fall 2019, and is discussing use cases and features for Payment Request after publication of the 1.0 Recommendation. Browser vendors have been finalizing implementation of features added in the past year (view the implementation report). As work continues on the Payment Handler API and its implementation (currently in Chrome and Edge Canary), one focus in 2019 is to increase adoption in other browsers. Recently, Mastercard demonstrated the use of Payment Request API to carry out EMVCo's Secure Remote Commerce (SRC) protocol whose payment method definition is being developed with active participation by Visa, Mastercard, American Express, and Discover. Payment method availability is a key factor in merchant considerations about adopting Payment Request API. The ability to get uniform adoption of a new payment method such as Secure Remote Commerce (SRC) also depends on the availability of the Payment Handler API in browsers, or of proprietary alternatives. Web Monetization, which the Web Payments Working Group will discuss again at its face-to-face meeting in September, can be used to enable micropayments as an alternative revenue stream to advertising. Since the beginning of 2019, Amazon, Brave Software, JCB, Certus Cybersecurity Solutions and Netflix have joined the Web Payments Working Group. In April, W3C launched the Web Payment Security Group to enable W3C, EMVCo, and the FIDO Alliance to collaborate on a vision for Web payment security and interoperability. Participants will define areas of collaboration and identify gaps between existing technical specifications in order to increase compatibility among different technologies, such as: How do SRC, FIDO, and Payment Request relate? The Payment Services Directive 2 (PSD2) regulations in Europe are scheduled to take effect in September 2019. What is the role of EMVCo, W3C, and FIDO technologies, and what is the current state of readiness for the deadline? How can we improve privacy on the Web at the same time as we meet industry requirements regarding user identity? Digital Publishing All Digital Publishing specifications, Publication milestones The Web is the universal publishing platform. Publishing is increasingly impacted by the Web, and the Web increasingly impacts Publishing. Topic of particular interest to Publishing@W3C include typography and layout, accessibility, usability, portability, distribution, archiving, offline access, print on demand, and reliable cross referencing. And the diverse publishing community represented in the groups consist of the traditional "trade" publishers, ebook reading system manufacturers, but also publishers of audio book, scholarly journals or educational materials, library scientists or browser developers. The Publishing Working Group currently concentrates on Audiobooks which lack a comprehensive standard, thus incurring extra costs and time to publish in this booming market. Active development is ongoing on the future standard: Publication Manifest Audiobook profile for Web Publications Lightweight Packaging Format The BD Comics Manga Community Group, the Synchronized Multimedia for Publications Community Group, the Publishing Community Group and a future group on archival, are companions to the working group where specific work is developed and incubated. The Publishing Community Group is a recently launched incubation channel for Publishing@W3C. The goal of the group is to propose, document, and prototype features broadly related to: publications on the Web reading modes and systems and the user experience of publications The EPUB 3 Community Group has successfully completed the revision of EPUB 3.2. The Publishing Business Group fosters ongoing participation by members of the publishing industry and the overall ecosystem in the development of Web infrastructure to better support the needs of the industry. The Business Group serves as an additional conduit to the Publishing Working Group and several Community Groups for feedback between the publishing ecosystem and W3C. The Publishing BG has played a vital role in fostering and advancing the adoption and continued development of EPUB 3. In particular the BG provided critical support to the update of EPUBCheck to validate EPUB content to the new EPUB 3.2 specification. This resulted in the development, in conjunction with the EPUB3 Community Group, of a new generation of EPUBCheck, i.e., EPUBCheck 4.2 production-ready release. Media and Entertainment All Media specifications The Media and Entertainment vertical tracks media-related topics and features that create immersive experiences for end users. HTML5 brought standard audio and video elements to the Web. Standardization activities since then have aimed at turning the Web into a professional platform fully suitable for the delivery of media content and associated materials, enabling missing features to stream video content on the Web such as adaptive streaming and content protection. Together with Microsoft, Comcast, Netflix and Google, W3C received an Technology & Engineering Emmy Award in April 2019 for standardization of a full TV experience on the Web. Current goals are to: Reinforce core media technologies: Creation of the Media Working Group, to develop media-related specifications incubated in the WICG (e.g. Media Capabilities, Picture-in-picture, Media Session) and maintain maintain/evolve Media Source Extensions (MSE) and Encrypted Media Extensions (EME). Improve support for Media Timed Events: data cues incubation. Enhance color support (HDR, wide gamut), in scope of the CSS WG and in the Color on the Web CG. Reduce fragmentation: Continue annual releases of a common and testable baseline media devices, in scope of the Web Media APIs CG and in collaboration with the CTA WAVE Project. Maintain the Road-map of Media Technologies for the Web which highlights Web technologies that can be used to build media applications and services, as well as known gaps to enable additional use cases. Create the future: Discuss perspectives for Media and Entertainment for the Web. Bring the power of GPUs to the Web (graphics, machine learning, heavy processing), under incubation in the GPU for the Web CG. Transition to a Working Group is under discussion. Determine next steps after the successful W3C Workshop on Web Games of June 2019. View the report. Timed Text The Timed Text Working Group develops and maintains formats used for the representation of text synchronized with other timed media, like audio and video, and notably works on TTML, profiles of TTML, and WebVTT. Recent progress includes: A robust WebVTT implementation report poises the specification for publication as a proposed recommendation. Discussions around re-chartering, notably to add a TTML Profile for Audio Description deliverable to the scope of the group, and clarify that rendering of captions within XR content is also in scope. Immersive Web Hardware that enables Virtual Reality (VR) and Augmented Reality (AR) applications are now broadly available to consumers, offering an immersive computing platform with both new opportunities and challenges. The ability to interact directly with immersive hardware is critical to ensuring that the web is well equipped to operate as a first-class citizen in this environment. The Immersive Web Working Group has been stabilizing the WebXR Device API while the companion Immersive Web Community Group incubates the next series of features identified as key for the future of the Immersive Web. W3C plans a workshop focused on the needs and benefits at the intersection of VR & Accessibility (Inclusive XR), on 5-6 November 2019 in Seattle, WA, USA, to explore existing and future approaches on making Virtual and Augmented Reality experiences more inclusive. Web & Telecommunications The Web is the Open Platform for Mobile. Telecommunication service providers and network equipment providers have long been critical actors in the deployment of Web technologies. As the Web platform matures, it brings richer and richer capabilities to extend existing services to new users and devices, and propose new and innovative services. Real-Time Communications (WebRTC) All Real-Time Communications specifications WebRTC has reshaped the whole communication landscape by making any connected device a potential communication end-point, bringing audio and video communications anywhere, on any network, vastly expanding the ability of operators to reach their customers. WebRTC serves as the corner-stone of many online communication and collaboration services. The WebRTC Working Group aims to bringing WebRTC 1.0 (and companion specification Media Capture and Streams) to Recommendation by the end of 2019. Intense efforts are focused on testing (supported by a dedicated hackathon at IETF 104) and interoperability. The group is considering pushing features that have not gotten enough traction to separate modules or to a later minor revision of the spec. Beyond WebRTC 1.0, the WebRTC Working Group will focus its efforts on WebRTC NV which the group has started documenting by identifying use cases. Web & Networks Recently launched, in the wake of the May 2018 Web5G workshop, the Web & Networks Interest Group is chaired by representatives from AT&T, China Mobile and Intel, with a goal to explore solutions for web applications to achieve better performance and resource allocation, both on the device and network. The group's first efforts are around use cases, privacy & security requirements and liaisons. Automotive All Automotive specifications To create a rich application ecosystem for vehicles and other devices allowed to connect to the vehicle, the W3C Automotive Working Group is delivering a service specification to expose all common vehicle signals (engine temperature, fuel/charge level, range, tire pressure, speed, etc.) The Vehicle Information Service Specification (VISS), which is a Candidate Recommendation, is seeing more implementations across the industry. It provides the access method to a common data model for all the vehicle signals –presently encapsulating a thousand or so different data elements– and will be growing to accommodate the advances in automotive such as autonomous and driver assist technologies and electrification. The group is already working on a successor to VISS, leveraging the underlying data model and the VIWI submission from Volkswagen, for a more robust means of accessing vehicle signals information and the same paradigm for other automotive needs including location-based services, media, notifications and caching content. The Automotive and Web Platform Business Group acts as an incubator for prospective standards work. One of its task forces is using W3C VISS in performing data sampling and off-boarding the information to the cloud. Access to the wealth of information that W3C's auto signals standard exposes is of interest to regulators, urban planners, insurance companies, auto manufacturers, fleet managers and owners, service providers and others. In addition to components needed for data sampling and edge computing, capturing user and owner consent, information collection methods and handling of data are in scope. The upcoming W3C Workshop on Data Models for Transportation (September 2019) is expected to focus on the need of additional ontologies around transportation space. Web of Things All Web of Things specifications W3C's Web of Things work is designed to bridge disparate technology stacks to allow devices to work together and achieve scale, thus enabling the potential of the Internet of Things by eliminating fragmentation and fostering interoperability. Thing descriptions expressed in JSON-LD cover the behavior, interaction affordances, data schema, security configuration, and protocol bindings. The Web of Things complements existing IoT ecosystems to reduce the cost and risk for suppliers and consumers of applications that create value by combining multiple devices and information services. There are many sectors that will benefit, e.g. smart homes, smart cities, smart industry, smart agriculture, smart healthcare and many more. The Web of Things Working Group is finishing the initial Web of Things standards, with support from the Web of Things Interest Group: Web of Things Architecture Thing Descriptions Strengthening the Core of the Web HTML The HTML Working Group was chartered early June to assist the W3C community in raising issues and proposing solutions for the HTML and DOM specifications, and to produce W3C Recommendations from WHATWG Review Drafts. A few days before, W3C and the WHATWG signed a Memorandum of Understanding outlining the agreement to collaborate on the development of a single version of the HTML and DOM specifications. Issues and proposed solutions for HTML and DOM done via the newly rechartered HTML Working Group in the WHATWG repositories The HTML Working Group is targetting November 2019 to bring HTML and DOM to Candidate Recommendations. CSS All CSS specifications CSS is a critical part of the Open Web Platform. The CSS Working Group gathers requirements from two large groups of CSS users: the publishing industry and application developers. Within W3C, those groups are exemplified by the Publishing groups and the Web Platform Working Group. The former requires things like better pagination support and advanced font handling, the latter needs intelligent (and fast!) scrolling and animations. What we know as CSS is actually a collection of almost a hundred specifications, referred to as ‘modules’. The current state of CSS is defined by a snapshot, updated once a year. The group also publishes an index defining every term defined by CSS specifications. Fonts All Fonts specifications The Web Fonts Working Group develops specifications that allow the interoperable deployment of downloadable fonts on the Web, with a focus on Progressive Font Enrichment as well as maintenance of WOFF Recommendations. Recent and ongoing work includes: Early API experiments by Adobe and Monotype have demonstrated the feasibility of a font enrichment API, where a server delivers a font with minimal glyph repertoire and the client can query the full repertoire and request additional subsets on-the-fly. In other experiments, the Brotli compression used in WOFF 2 was extended to support shared dictionaries and patch update. Metrics to quantify improvement are a current hot discussion topic. The group will meet at ATypi 2019 in Japan, to gather requirements from the international typography community. The group will first produce a report summarizing the strengths and weaknesses of each prototype solution by Q2 2020. SVG All SVG specifications SVG is an important and widely-used part of the Open Web Platform. The SVG Working Group focuses on aligning the SVG 2.0 specification with browser implementations, having split the specification into a currently-implemented 2.0 and a forward-looking 2.1. Current activity is on stabilization, increased integration with the Open Web Platform, and test coverage analysis. The Working Group was rechartered in March 2019. A new work item concerns native (non-Web-browser) uses of SVG as a non-interactive, vector graphics format. Audio The Web Audio Working Group was extended to finish its work on the Web Audio API, expecting to publish it as a Recommendation by year end. The specification enables synthesizing audio in the browser. Audio operations are performed with audio nodes, which are linked together to form a modular audio routing graph. Multiple sources — with different types of channel layout — are supported. This modular design provides the flexibility to create complex audio functions with dynamic effects. The first version of Web Audio API is now feature complete and is implemented in all modern browsers. Work has started on the next version, and new features are being incubated in the Audio Community Group. Performance Web Performance All Web Performance specifications There are currently 18 specifications in development in the Web Performance Working Group aiming to provide methods to observe and improve aspects of application performance of user agent features and APIs. The W3C team is looking at related work incubated in the W3C GPU for the Web (WebGPU) Community Group which is poised to transition to a W3C Working Group. A preliminary draft charter is available. WebAssembly All WebAssembly specifications WebAssembly improves Web performance and power by being a virtual machine and execution environment enabling loaded pages to run native (compiled) code. It is deployed in Firefox, Edge, Safari and Chrome. The specification will soon reach Candidate Recommendation. WebAssembly enables near-native performance, optimized load time, and perhaps most importantly, a compilation target for existing code bases. While it has a small number of native types, much of the performance increase relative to Javascript derives from its use of consistent typing. WebAssembly leverages decades of optimization for compiled languages and the byte code is optimized for compactness and streaming (the web page starts executing while the rest of the code downloads). Network and API access all occurs through accompanying Javascript libraries -- the security model is identical to that of Javascript. Requirements gathering and language development occur in the Community Group while the Working Group manages test development, community review and progression of specifications on the Recommendation Track. Testing Browser testing plays a critical role in the growth of the Web by: Improving the reliability of Web technology definitions; Improving the quality of implementations of these technologies by helping vendors to detect bugs in their products; Improving the data available to Web developers on known bugs and deficiencies of Web technologies by publishing results of these tests. Browser Testing and Tools The Browser Testing and Tools Working Group is developing WebDriver version 2, having published last year the W3C Recommendation of WebDriver. WebDriver acts as a remote control interface that enables introspection and control of user agents, provides a platform- and language-neutral wire protocol as a way for out-of-process programs to remotely instruct the behavior of Web, and emulates the actions of a real person using the browser. WebPlatform Tests The WebPlatform Tests project now provides a mechanism which allows to fully automate tests that previously needed to be run manually: TestDriver. TestDriver enables sending trusted key and mouse events, sending complex series of trusted pointer and key interactions for things like in-content drag-and-drop or pinch zoom, and even file upload. Since 2014 W3C began work on this coordinated open-source effort to build a cross-browser test suite for the Web Platform, which WHATWG, and all major browsers adopted. Web of Data All Data specifications There have been several great success stories around the standardization of data on the web over the past year. Verifiable Claims seems to have significant uptake. It is also significant that the Distributed Identifier WG charter has received numerous favorable reviews, and was just recently launched. JSON-LD has been a major success with the large deployment on Web sites via schema.org. JSON-LD 1.1 completed technical work, about to transition to CR More than 25% of websites today include schema.org data in JSON-LD The Web of Things description is in CR since May, making use of JSON-LD Verifiable Credentials data model is in CR since July, also making use of JSON-LD Continued strong interest in decentralized identifiers Engagement from the TAG with reframing core documents, such as Ethical Web Principles, to include data on the web within their scope Data is increasingly important for all organizations, especially with the rise of IoT and Big Data. W3C has a mature and extensive suite of standards relating to data that were developed over two decades of experience, with plans for further work on making it easier for developers to work with graph data and knowledge graphs. Linked Data is about the use of URIs as names for things, the ability to dereference these URIs to get further information and to include links to other data. There are ever-increasing sources of open Linked Data on the Web, as well as data services that are restricted to the suppliers and consumers of those services. The digital transformation of industry is seeking to exploit advanced digital technologies. This will facilitate businesses to integrate horizontally along the supply and value chains, and vertically from the factory floor to the office floor. W3C is seeking to make it easier to support enterprise-wide data management and governance, reflecting the strategic importance of data to modern businesses. Traditional approaches to data have focused on tabular databases (SQL/RDBMS), Comma Separated Value (CSV) files, and data embedded in PDF documents and spreadsheets. We're now in midst of a major shift to graph data with nodes and labeled directed links between them. Graph data is: Faster than using SQL and associated JOIN operations More favorable to integrating data from heterogeneous sources Better suited to situations where the data model is evolving In the wake of the recent W3C Workshop on Graph Data we are in the process of launching a Graph Standardization Business Group to provide a business perspective with use cases and requirements, to coordinate technical standards work and liaisons with external organizations. Web for All Security, Privacy, Identity All Security specifications, all Privacy specifications Authentication on the Web As the WebAuthn Level 1 W3C Recommendation published last March is seeing wide implementation and adoption of strong cryptographic authentication, work is proceeding on Level 2. The open standard Web API gives native authentication technology built into native platforms, browsers, operating systems (including mobile) and hardware, offering protection against hacking, credential theft, phishing attacks, thus aiming to end the era of passwords as a security construct. You may read more in our March press release. Privacy An increasing number of W3C specifications are benefitting from Privacy and Security review; there are security and privacy aspects to every specification. Early review is essential. Working with the TAG, the Privacy Interest Group has updated the Self-Review Questionnaire: Security and Privacy. Other recent work of the group includes public blogging further to the exploration of anti-patterns in standards and permission prompts. Security The Web Application Security Working Group adopted Feature Policy, aiming to allow developers to selectively enable, disable, or modify the behavior of some of these browser features and APIs within their application; and Fetch Metadata, aiming to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used. The Web Payment Security Interest Group, launched last April, convenes members from W3C, EMVCo, and the FIDO Alliance to discuss cooperative work to enhance the security and interoperability of Web payments (read more about payments). Internationalization (i18n) All Internationalization specifications, educational articles related to Internationalization, spec developers checklist Only a quarter or so current Web users use English online and that proportion will continue to decrease as the Web reaches more and more communities of limited English proficiency. If the Web is to live up to the "World Wide" portion of its name, and for the Web to truly work for stakeholders all around the world engaging with content in various languages, it must support the needs of worldwide users as they engage with content in the various languages. The growth of epublishing also brings requirements for new features and improved typography on the Web. It is important to ensure the needs of local communities are captured. The W3C Internationalization Initiative was set up to increase in-house resources dedicated to accelerating progress in making the World Wide Web "worldwide" by gathering user requirements, supporting developers, and education & outreach. For an overview of current projects see the i18n radar. W3C's Internationalization efforts progressed on a number of fronts recently: Requirements: New African and European language groups will work on the gap analysis, errata and layout requirements. Gap analysis: Japanese, Devanagari, Bengali, Tamil, Lao, Khmer, Javanese, and Ethiopic updated in the gap-analysis documents. Layout requirements document: notable progress tracked in the Southeast Asian Task Force while work continues on Chinese layout requirements. Developer support: Spec reviews: the i18n WG continues active review of specifications of the WHATWG and other W3C Working Groups. Short review checklist: easy way to begin a self-review to help spec developers understand what aspects of their spec are likely to need attention for internationalization, and points them to more detailed checklists for the relevant topics. It also helps those reviewing specs for i18n issues. Strings on the Web: Language and Direction Metadata lays out issues and discusses potential solutions for passing information about language and direction with strings in JSON or other data formats. The document was rewritten for clarity, and expanded. The group is collaborating with the JSON-LD and Web Publishing groups to develop a plan for updating RDF, JSON-LD and related specifications to handle metadata for base direction of text (bidi). User-friendly test format: a new format was developed for Internationalization Test Suite tests, which displays helpful information about how the test works. This particularly useful because those tests are pointed to by educational materials and gap-analysis documents. Web Platform Tests: a large number of tests in the i18n test suite have been ported to the WPT repository, including: css-counter-styles, css-ruby, css-syntax, css-test, css-text-decor, css-writing-modes, and css-pseudo. Education & outreach: (for all educational materials, see the HTML & CSS Authoring Techniques) Web Accessibility All Accessibility specifications, WAI resources The Web Accessibility Initiative supports W3C's Web for All mission. Recent achievements include: Education and training: Inaccessibility of CAPTCHA updated to bring our analysis and recommendations up to date with CAPTCHA practice today, concluding two years of extensive work and invaluable input from the public (read more on the W3C Blog Learn why your web content and applications should be accessible. The Education and Outreach Working Group has completed revision and updating of the Business Case for Digital Accessibility. Accessibility guidelines: The Accessibility Guidelines Working Group has continued to update WCAG Techniques and Understanding WCAG 2.1; and published a Candidate Recommendation of Accessibility Conformance Testing Rules Format 1.0 to improve inter-rater reliability when evaluating conformance of web content to WCAG An updated charter is being developed to host work on "Silver", the next generation accessibility guidelines (WCAG 2.2) There are accessibility aspects to most specifications. Check your work with the FAST checklist. Outreach to the world W3C Developer Relations To foster the excellent feedback loop between Web Standards development and Web developers, and to grow participation from that diverse community, recent W3C Developer Relations activities include: @w3cdevs tracks the enormous amount of work happening across W3C W3C Track during the Web Conference 2019 in San Francisco Tech videos: W3C published the 2019 Web Games Workshop videos The 16 September 2019 Developer Meetup in Fukuoka, Japan, is open to all and will combine a set of technical demos prepared by W3C groups, and a series of talks on a selected set of W3C technologies and projects W3C is involved with Mozilla, Google, Samsung, Microsoft and Bocoup in the organization of ViewSource 2019 in Amsterdam (read more on the W3C Blog) W3C Training In partnership with EdX, W3C's MOOC training program, W3Cx offers a complete "Front-End Web Developer" (FEWD) professional certificate program that consists of a suite of five courses on the foundational languages that power the Web: HTML5, CSS and JavaScript. We count nearly 900K students from all over the world. Translations Many Web users rely on translations of documents developed at W3C whose official language is English. W3C is extremely grateful to the continuous efforts of its community in ensuring our various deliverables in general, and in our specifications in particular, are made available in other languages, for free, ensuring their exposure to a much more diverse set of readers. Last Spring we developed a more robust system, a new listing of translations of W3C specifications and updated the instructions on how to contribute to our translation efforts. W3C Liaisons Liaisons and coordination with numerous organizations and Standards Development Organizations (SDOs) is crucial for W3C to: make sure standards are interoperable coordinate our respective agenda in Internet governance: W3C participates in ICANN, GIPO, IGF, the I* organizations (ICANN, IETF, ISOC, IAB). ensure at the government liaison level that our standards work is officially recognized when important to our membership so that products based on them (often done by our members) are part of procurement orders. W3C has ARO/PAS status with ISO. W3C participates in the EU MSP and Rolling Plan on Standardization ensure the global set of Web and Internet standards form a compatible stack of technologies, at the technical and policy level (patent regime, fragmentation, use in policy making) promote Standards adoption equally by the industry, the public sector, and the public at large Coralie Mercier, Editor, W3C Marketing & Communications $Id: Overview.html,v 1.60 2019/10/15 12:05:52 coralie Exp $ Copyright © 2019 W3C ® (MIT, ERCIM, Keio, Beihang) Usage policies apply.

NETFLIX 2.0 with NEXT.JS!(Next.js, NextAuth.js v4, Tailwind CSS, framer-motion, TMDB Api, Google Authentication, primary information about a movies, Users can Add Bookmark in favorite actors and movies)

No description available

No description available

# Loon全局配置 by nzw9314 # YouTube去广告请删除hostname 后的.bak # GitHub主页(https://github.com/nzw9314) # TG通知频道 (https://t.me/nzw9314News) [General] ipv6 = false skip-proxy = 10.0.0.0/8,127.0.0.0/8,169.254.0.0/16,192.0.2.0/24,192.168.0.0/16,198.51.100.0/24,224.0.0.0/4,*.local,localhostlocal bypass-tun = 10.0.0.0/8,127.0.0.0/8,169.254.0.0/16,192.0.2.0/24,192.168.0.0/16,198.51.100.0/24,224.0.0.0/4 # [DNS] => DNS 服务器 dns-server = system,1.2.4.8,119.29.29.29,223.5.5.5 allow-udp-proxy = true host = 127.0.0.1 [Remote Proxy] # 订阅节点 # 别名 = 订阅URL ✈️机场1 = https://example/server-complete.txt ✈️机场2 = https://example2/server-complete.txt [Remote Filter] # 筛选订阅节点，筛选后的结果可加入到策略组中，目前支持三种筛选方式 # NodeSelect: 使用在UI上选择的节点。 # NameKeyword: 根据提供的关键词对订阅中所有节点的名称进行筛选，使用筛选后的节点。 # NameRegex: 根据提供的正则表达式对订阅中所有节点的名称进行筛选，使用筛选后的节点。 𝐏𝐚𝐲𝐏𝐚𝐥 = NodeSelect,✈️机场1,✈️机场2 𝐍𝐞𝐭𝐟𝐥𝐢𝐱 = NameKeyword,✈️机场1,✈️机场2, FilterKey = Netflix 🇭🇰香港 = NameRegex,✈️机场1,✈️机场2, FilterKey = 香港|HK 🇯🇵日本 = NameRegex,✈️机场1,✈️机场2, FilterKey = 日本|JP 🇰🇷韩国 = NameRegex,✈️机场1,✈️机场2, FilterKey = 韩国|KR 🇺🇸美国 = NameRegex,✈️机场1,✈️机场2, FilterKey = 美国|US Other = NameRegex,✈️机场1,✈️机场2, FilterKey = ^(?!.*(HK|JP|US|KR|香港|日本|韩国|美国)).*$ [Proxy] # 本地节点 # 内置 DIRECT、REJECT 策略 # 节点名称 = 协议，服务器地址，服务器端口，加密协议，密码， 1 = Shadowsocks,1.2.3.4,443,aes-128-gcm,"”password“" 2 = Shadowsocks,1.2.3.4,443,aes-128-gcm,"”password“" 3 = ShadowsocksR,1.2.3.4,443,aes-256-cfb,"”password“",auth_aes128_md5,{},tls1.2_ticket_auth,{} 4 = ShadowsocksR,1.2.3.4,10076,aes-128-cfb,"”password“",auth_aes128_md5,{},tls1.2_ticket_auth,{} # vmess # 节点名称 = 协议，服务器地址，端口，加密方式，UUID，传输方式:(tcp/ws),path：websocket握手header中的path，host：websocket握手header中的path，over-tls:是否tls，tls-name：远端w服务器域名，skip-cert-verify：是否跳过证书校验（默认否） #5 = vmess, 1.2.3.4, 10086, aes-128-gcm,”uuid“,transport:ws,path:/,host:icloud.com,over-tls:true,tls-name:youtTlsServerName.com,skip-cert-verify:false # 解锁网易云音乐灰色歌曲 🎧 = http,106.52.127.72,19951 [Proxy Group] # 策略组 # 节点选项 🕹𝐅𝐢𝐧𝐚𝐥 = select,🔰𝐏𝐫𝐨𝐱𝐲,🎯𝐃𝐢𝐫𝐞𝐜𝐭 🔰𝐏𝐫𝐨𝐱𝐲 = select,♻️𝐀𝐮𝐭𝐨,🌀𝐒𝐞𝐥𝐞𝐜𝐭,🔴𝐅𝐚𝐥𝐥𝐛𝐚𝐜𝐤 # url-test模式，给提供的url发出http header请求，根据返回结果，选择测速最快的节点，默认间隔600s，测速超时时间5s，为了避免资源浪费，建议节点数不要过多，只支持单个节点和远端节点，其他会被忽略 ♻️𝐀𝐮𝐭𝐨 = url-test,🇭🇰香港,🇯🇵日本,🇰🇷韩国,🇺🇸美国,url = http://bing.com/,interval = 600 # select模式,手动选择模式 🌀𝐒𝐞𝐥𝐞𝐜𝐭 = select,🇭🇰香港,🇯🇵日本,🇰🇷韩国,🇺🇸美国 # fallback模式，和url-test类似，不同的是会根据顺序返回第一个可用的节点，为了避免资源浪费，建议节点数不要过多，只支持单个节点和远端节点，其他会被忽略 🔴𝐅𝐚𝐥𝐥𝐛𝐚𝐜𝐤 = fallback,🇭🇰香港,🇯🇵日本,🇰🇷韩国,🇺🇸美国,REJECT,url = http://bing.com/,interval = 600 🎵𝐓𝐢𝐤𝐓𝐨𝐤 = select,🔰𝐏𝐫𝐨𝐱𝐲,🎯𝐃𝐢𝐫𝐞𝐜𝐭 🖥𝐍𝐞𝐭𝐟𝐥𝐢𝐱 = select,𝐍𝐞𝐭𝐟𝐥𝐢𝐱,🎯𝐃𝐢𝐫𝐞𝐜𝐭 💳𝐏𝐚𝐲𝐏𝐚𝐥 = select,𝐏𝐚𝐲𝐏𝐚𝐥,🎯𝐃𝐢𝐫𝐞𝐜𝐭 📱𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦 = select,🔰𝐏𝐫𝐨𝐱𝐲,🎯𝐃𝐢𝐫𝐞𝐜𝐭 🎬𝐘𝐨𝐮𝐓𝐮𝐛𝐞 = select,🔰𝐏𝐫𝐨𝐱𝐲,🎯𝐃𝐢𝐫𝐞𝐜𝐭 🔞𝐏𝐨𝐫𝐧𝐇𝐮𝐛 = select,🔰𝐏𝐫𝐨𝐱𝐲,🎯𝐃𝐢𝐫𝐞𝐜𝐭 # 🔓网易云音乐灰色歌曲,需要节点支持解锁 🎧𝐍𝐞𝐭𝐞𝐚𝐬𝐞𝐌𝐮𝐬𝐢𝐜 = select,🎯𝐃𝐢𝐫𝐞𝐜𝐭,🎧,🔰𝐏𝐫𝐨𝐱𝐲 # 网络测速 🚀𝐒𝐩𝐞𝐞𝐝𝐓𝐞𝐬𝐭 = select,🔰𝐏𝐫𝐨𝐱𝐲,🎯𝐃𝐢𝐫𝐞𝐜𝐭 # 苹果服务 🍎𝐀𝐩𝐩𝐥𝐞 = select,🎯𝐃𝐢𝐫𝐞𝐜𝐭,🔰𝐏𝐫𝐨𝐱𝐲 # 白名单模式 PROXY，黑名单模式 DIRECT # 广告拦截 🚫𝐀𝐝 𝐁𝐥𝐨𝐜𝐤 = select,⛔️𝐑𝐞𝐣𝐞𝐜𝐭,🎯𝐃𝐢𝐫𝐞𝐜𝐭 # 直接连接 🎯𝐃𝐢𝐫𝐞𝐜𝐭 = select,DIRECT # 拦截 ⛔️𝐑𝐞𝐣𝐞𝐜𝐭 = select,REJECT # SSID # 别名 = ssid，默认 = 策略， 蜂窝 = 策略， ssid名称 = 策略 #SSID = ssid, default = PROXY, cellular = DIRECT, ”DivineEngine“ = PROXY [Rule] # 本地规则 # Type:DOMAIN-SUFFIX,DOMAIN,DOMAIN-KEYWORD,USER-AGENT,URL-REGEX,IP-CIDR # Strategy:DIRECT,Proxy,REJECT # Options:force-remote-dns(Default:false),no-resolve # 𝐍𝐞𝐭𝐞𝐚𝐬𝐞𝐌𝐮𝐬𝐢𝐜 DOMAIN-SUFFIX,music.126.net,DIRECT # GeoIP China GEOIP,CN,🎯𝐃𝐢𝐫𝐞𝐜𝐭 FINAL, 🕹𝐅𝐢𝐧𝐚𝐥 [Remote Rule] # 订阅规则 https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Liby.list,🚫𝐀𝐝 𝐁𝐥𝐨𝐜𝐤 # BlockOTA https://raw.githubusercontent.com/nzw9314/Surge/master/Ruleset/BlockOTA.list,🚫𝐀𝐝 𝐁𝐥𝐨𝐜𝐤 # Antirevoke https://raw.githubusercontent.com/nzw9314/Surge/master/Ruleset/Antirevoke.list,🚫𝐀𝐝 𝐁𝐥𝐨𝐜𝐤 # > TikTok https://raw.githubusercontent.com/nzw9314/Surge/master/Ruleset/TikTok.list,🎵𝐓𝐢𝐤𝐓𝐨𝐤 # > Youtube https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Sub/YouTube.list,🎬𝐘𝐨𝐮𝐓𝐮𝐛𝐞 # > Netflix https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Sub/Netflix.list,🖥𝐍𝐞𝐭𝐟𝐥𝐢𝐱 # > PronHub https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Sub/Pornhub.list,🔞𝐏𝐨𝐫𝐧𝐇𝐮𝐛 # Telegram https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Sub/Telegram.list,📱𝐓𝐞𝐥𝐞𝐠𝐫𝐚𝐦 # > PayPal https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Sub/PayPal.list,💳𝐏𝐚𝐲𝐏𝐚𝐥 # > Outlook、Gmail https://raw.githubusercontent.com/nzw9314/Surge/master/Ruleset/Mail.list,🔰𝐏𝐫𝐨𝐱𝐲 # > GoogleDrive https://raw.githubusercontent.com/nzw9314/Surge/master/Ruleset/GoogleDrive.list,🔰𝐏𝐫𝐨𝐱𝐲 # Speedtest https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Sub/Speedtest.list,🚀𝐒𝐩𝐞𝐞𝐝𝐓𝐞𝐬𝐭 # >Unlock NeteaseMusic https://raw.githubusercontent.com/nzw9314/Surge/master/Ruleset/UnlockNeteaseMusic.list,🎧𝐍𝐞𝐭𝐞𝐚𝐬𝐞𝐌𝐮𝐬𝐢𝐜 https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Apple_CDN.list,🍎𝐀𝐩𝐩𝐥𝐞 https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Apple_API.list,🍎𝐀𝐩𝐩𝐥𝐞 https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/AsianMedia.list,🎯𝐃𝐢𝐫𝐞𝐜𝐭 https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/GlobalMedia.list,🔰𝐏𝐫𝐨𝐱𝐲 https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Domestic.list,🎯𝐃𝐢𝐫𝐞𝐜𝐭 https://raw.githubusercontent.com/eHpo1/Rules/master/Surge4/Ruleset/Global.list,🔰𝐏𝐫𝐨𝐱𝐲 [URL Rewrite] # 本地重写 # > TikTok Unlock (By Choler) # 区域请修改下方国家代码，默认为日本 JP (?<=_region=)CN(?=&) JP 307 (?<=&app_version=)16..(?=.?.?&) 1 307 (?<=\?version_code=)16..(?=.?.?&) 1 307 # > 抖音 去广告&水印 # 需配合脚本使用 ^https?:\/\/[\w-]+\.amemv\.com\/aweme\/v\d\/feed\/ https://aweme.snssdk.com/aweme/v1/feed/ header ^https?:\/\/[\w-]+\.amemv\.com\/aweme\/v\d\/aweme\/post\/ https://aweme.snssdk.com/aweme/v1/aweme/post/ header ^https?:\/\/[\w-]+\.amemv\.com\/aweme\/v\d\/follow\/feed\/ https://aweme.snssdk.com/aweme/v1/follow/feed/ header ^https?:\/\/[\w-]+\.amemv\.com\/aweme\/v\d\/nearby\/feed\/ https://aweme.snssdk.com/aweme/v1/nearby/feed/ header ^https?:\/\/[\w-]+\.amemv\.com\/aweme\/v\d\/search\/item\/ https://aweme.snssdk.com/aweme/v1/search/item/ header ^https?:\/\/[\w-]+\.amemv\.com\/aweme\/v\d\/general\/search\/single\/ https://aweme.snssdk.com/aweme/v1/general/search/single/ header ^https?:\/\/[\w-]+\.amemv\.com\/aweme\/v\d\/hot/search\/video\/list\/ https://aweme.snssdk.com/aweme/v1/hot/search/video/list/ header enable = true [Remote Rewrite] #订阅重写 去广告 by eHpo # 格式：订阅url，别名(可选) https://raw.githubusercontent.com/eHpo1/Rules/master/Loon/Rewrite.conf,eHpo https://raw.githubusercontent.com/nzw9314/Loon/master/Q-Search_All_in_one.conf,Q-Search_All_in_one [Script] # 本地脚本 enable = true [Remote Script] # 远程脚本 https://raw.githubusercontent.com/nzw9314/Loon/master/Task.conf,签到 https://raw.githubusercontent.com/nzw9314/Loon/master/Script.conf,脚本 https://raw.githubusercontent.com/nzw9314/Loon/master/Cookie.conf,Cookie [MITM] enable = true hostname = *.googlevideo.com.bak skip-server-cert-verify = true ca-p12 = MIIJrgIBAzCCCXgGCSqGSIb3DQEHAaCCCWkEggllMIIJYTCCA/8GCSqGSIb3DQEHBqCCA/AwggPsAgEAMIID5QYJKoZIhvcNAQcBMBwGCiqGSIb3DQEMAQYwDgQIYl/myyqpUtwCAggAgIIDuMYEzEUgSxIUScp1vSSooV2iePmy4Q7YP8cfnhaatGNnX+CC9/rDdPgDuz7k1D/7hYdaOsTKpXU9aUAxHvg9SLAWFm5dL4g/9MVk7Id8qCPMYbO2H+lQTChEN8iTpWdq+qlAC8VpqY1TTXhQTkCKF3cT+S68xZUMFDuX95INBUswjN+imGIYVKFBp4s0K7UDFpF0BMUD5HwR9U/QFsZ+ScCaNj/Y1p95LWPllUkeeb67uTOeXc55yEM+O8W/SGjJhgjdnvPgetCfLMc6RWREK0SNAGMzHibuvHHHm0fIBg5zwE+DjDdefwYMUghpQVl+0gSeASjsvP9mSgtm9+horQCw/ef0a3FxcKsmTzSE6o4dx37fEckEouYN/Ni+OWnKWb6eXeaL6yVD4gLDmEwV8lmgBG4OjYcdY9jeIBFkDzbG70eUvmj6/1olUtnOnkGY5ZMvCGhVr8K4ZJ80xuykgxgPI/5enNZZiS9cAuk85xAN+XeDvmQdIHF9TxMRyLGJyWUkczjV3DSPkqZ2hMFJRuOF5zbhZlCcJgkEdCYbb4sebYnGKOEVnfceFVK1yv33Hp+BcQDmqEm+gssrtNhJGCWtqTjT28WeGxGgAWOaY2e+isVJG6TvU1D+tHCl09WyLKM671a63jY6QvpWwRpSMkbcrGEMhQRo2IMrxhwkia9vkk+eDYRt4jJcG8gRAWB0crXuYMM/t0gxDKTiVF7aS0XEHWMkH7ATWFI/+Yta4dsVLAOACnTCarD80RH/xV5JK1KiAn5pSzy13fRwvYcHAluJ/7JHphVUtNYroNgfzdt5n65B7qD5PU4ykhVMfflZXom17VGwUqf750kx0fowU23XCUyWoifoGBbkR9mgGHBqZyMZHv+Z9iWPmpqJcfjL9UBX91Ulzg74IQocvNTHMVu3cLXx63OiQ6k4+FYZcvTiJyYpu7N36I/nLz61L3D2d8LaYLHAcvnsClfC6QRVVAU/wvQnhp2/oPh/l19KBX7QUnBKPU1oFLEV8y1G87IbN/LDJ0SUroS/McCojANgutTpKQJT+5jlid+GxZkEi4CXlTAUfu6/lioLdJugycPEKHu49zAmbDw8lUy5QRUbyjWrZk8tLu2bKzaxg5A21N9N/zKt9uXmcN5J/O1L8WIcAIXDytAmkyw7ez45EF631i6k2uJeuIxtBwRfwDyuw4FwKrsqw197FoqsvsMb68Tak2vVtzgs/rSQ1PL3acsLQ0CBZ9/Do1WxAb8azc4ko36JE7e0xtM43qswggVaBgkqhkiG9w0BBwGgggVLBIIFRzCCBUMwggU/BgsqhkiG9w0BDAoBAqCCBO4wggTqMBwGCiqGSIb3DQEMAQMwDgQI3rZrdI9fPuMCAggABIIEyGZyUi/orJ8LMBdjZFQaCNXECddtwPuKPg+QxAzpxC0/VSgdtHsOR/v8koAJgddmGJUDwLXGVcuasJ7YlhdIKpnvSzNBB7qjJoQBQ5dMsXVfcJaRwbhjMExjZyvUjCKH21lJ7yaxGQORtmIXTpx0FPQUprJtghF/C2ejA9QSW+SCjYY64dkvUovvXMDaddKWq+i0lOGKi0hvCjGiLobIovBpSfjX1EYTK5pmpBtWKro5Wnm/Q5r/OBU2+PyzlFCZdMdov7bIcUwnz4D1Oypn6woQol8N9AqgQL52pMweL8k0fK8YH3eChE5EP0JNc1X0vRTHhKiAB0Su5vjSVa5QU4ZBTCdNdwM7rr2NJMzMjF8g4y7fXMTVXdPUi1QeYihOqmcU2i0pmrk4zPeobGfzLIcgRSLf9qeP2r9Gw3yt3rjJMHgbx6QvBZ+5GZ8/iooQTbLjUj83QfdGeidkD+Auba9f8cPDiurDF+Pjt2FotaT3Vqx38qlaprBdlk7H1yVZtY2G5Y5pquiyPK/C+QwrXYWEocsJIAvAb3xhXalqkUs6ZmKTVQqlpUR0L/ogRmeJ0OxHYKbqy4Rg2eIcHogPEK2Xa2iiPFmG6AbWUnE8mmH5PunCPGuhcOxFYZAkpf96//c0J9ry52pcvR15ZIvmZdSLrhjD4pD+CElUKFS6izafXSyFQpjNuQI2aCnMNS/AFSe3kH6naARoOUnXFC7Wz+e69nOKs6G84/gV3xD4klk5vCza32e55MtUD9SX09+q9XItarBeBYCn3XCZk1sZADmg8gHxZzgEj3mA7slqsRnx7E80lz1UlHU4FSLkeMEU2u9/K1QA6VZzFfFRXtitZuam2Di98zCyftyb0D0DwlywSab/ww7VrROnBq3sozc7uo7eEiT8Jx9qd2kGNF+r9KI6QePBtATJzsgCNoPHNTdA7DNX4opD0bNsRtFHQLW3b9k1PeeAix1agcrqsDVV2PsWn9Qae9vY4zqwkNY+hjlmt2CRPG/5pX8COVn+dzqGHTksFg/NgVZsAj8NK4ZGf+QSRxSUo/5sYbu61Pj6TpyEIjOEPM+ylXdhziKhDTfw4GkrmTjlrQQ9T+7pqC86nYS8HH9ZcET+SecZK8kMPe7pwbzwHPWsl+OqHTP01KvEAogOL8fAZ7LsbaHlPoLHkHDQzxeep6ZKDnoCphjsf4oqSlcQzNh383mAr0YTPY8SaVV5G6Hh9mCHQqKWWmXhNd8rN/kqZn0H7KvfMJW2BGVWgCvYaE5m5sodhHYjSMGzgauV7O9DL3H+Az2Ztz0K2hj11xsz/C7nRVNOgV02rDvIEHw0asBPq2gYPC4OG/HutK+etT87z+tLftGO9V5+TMcIc4JKaNVOUg814DP59yo/WptH346rHwY7AqvgmEi6LJ1LLP9W6+HH1k3Fk6WEpOtDJS3YqV4EjswXGCtLXu6y/IvqLkyvT7NIZi/BYFf39xwJDvD5SbLM2jhCShG/HsD0/4qfqeGA/x4LLaM9Lyl091XeKWtY9XpP9nZzfgOJkk2rsBH29jS5d8lLkz+GhdzrROPIgHn+yaSsp8vIwr8L9h27+6/95kbUiQugOWEWdO/ZO+X/iyhThallmiNbJP+Qv3abUJgzcTE+MBcGCSqGSIb3DQEJFDEKHggAZQBIAHAAbzAjBgkqhkiG9w0BCRUxFgQU5gr9fNKSpq6pZ3g5Hca/uXOuY+cwLTAhMAkGBSsOAwIaBQAEFKXWG0IDj30Q2VfVGNWcVJ8iipuZBAgHvSM3D+pSUA== ca-passphrase = eHpoj

BLACKEYE v1.5.1 UPDATES : Updated the port forwarding support to ngrok2.0 FOR ANY SUGGESTION CONTACT :@suljot_gjoka or x3rz.r on Instagram! From @An0nUD4Y (https://github.com/An0nUD4Y/blackeye) BLACKEYE v1.5 UPDATES : Added 10 new websites from the Pro version! The tool is completely free now FOR ANY SUGGESTION CONTACT :@suljot_gjoka on Instagram! BLACKEYE v1.2 UPDATES : Added 2 new websites : iCloud ID , Wi-Fi phisher Updated Google Account website Removed : Spotify,Netflix,Paypal,eBay,Amazon,CryptoCurrency and Steam. They are available on the pro version of Blackeye including more websites with paid content. Contact me on Instagram : @suljot_gjoka for the Pro Version BLACKEYE v1.0 Coded by: @thelinuxchoice (https://github.com/thelinuxchoice/blackeye) Upgraded by: @suljot_gjoka (https://github.com/whiteeagle0/blackeye) Credits (Copyright) Phishing Pages generated by An0nUD4Y (https://github.com/An0nUD4Y): Instagram Phishing Pages generated by Social Fish tool (UndeadSec) (https://github.com/UndeadSec/SocialFish): Facebook,Google,SnapChat,Twitter,Microsoft Phishing Pages generated by @suljot_gjoka (https://github.com/whiteeagle0/blackeye): PayPal,eBay,CryptoCurrency,Verizon,Drop Box,Adobe ID,Shopify,Messenger,TwitchMyspace,Badoo,VK,Yandex,devianART Description BLACKEYE is an upgrade from original ShellPhish Tool (https://github.com/thelinuxchoice/shellphish) by thelinuxchoice under GNU LICENSE. It is the most complete Phishing Tool, with 32 templates +1 customizable Legal disclaimer: Usage of BlackEye for attacking targets without prior mutual consent is illegal. It's the end user's responsibility to obey all applicable local, state and federal laws. Developers assume no liability and are not responsible for any misuse or damage caused by this program. Only use for educational purposes. Usage: git clone https://github.com/x3rz/blackeye.git cd blackeye bash blackeye.sh ./ngrok authtoken <your_auth_token> bash blackeye.sh

Netflix demo using Graphql features, adopting Apollo client 2.0 for Graphql

NETFLIX 2.0 - React, Redux, TMDB, Firebase v9, Stripe Payments and Subscription Integration, React-Router, etc.

📝 𝐑𝐔𝐋𝐄𝐒 & 𝐑𝐄𝐆𝐔𝐋𝐀𝐓𝐈𝐎𝐍𝐒: 💗𝚆𝚎𝚕𝚌𝚘𝚖𝚎 𝚝𝚘 𝙼𝙰𝚇𝚇 𝙼𝙸𝚁𝚁𝙾𝚁 𝚉𝙾𝙽𝙴 ⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛ 📜 𝗠𝗜𝗥𝗥𝗢𝗥 𝗥𝗨𝗟𝗘𝗦 📃 ★ 18+ Not Allow ★ Mirror Limit: 100GB ★ MEGA Link Limit: 20GB/day ★ Before Mirror anything Must Search 🔍 Files ★ Clone Limit: 50GB/day ★ Playlist Mirror : if 50 above Video in your Playlist Link then don't Mirror ⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛⇛ ⛔ 𝐑𝐄𝐀𝐒𝐎𝐍: 𝐘𝐎𝐔 𝐌𝐈𝐆𝐇𝐓 𝐁𝐄 𝐆𝐄𝐓 𝐁𝐀𝐍 🛠️ ⛔ ⚠️ 𝙸𝙵 𝚈𝙾𝚄 𝙳𝙸𝙳 𝙰𝙽𝚈 𝙾𝙵 𝚃𝙷𝙴𝚂𝙴!! 𝚈𝙾𝚄 𝚆𝙸𝙻𝙻 𝙱𝙴 𝙱𝙰𝙽 𝙵𝙾𝚁 𝙿𝙴𝚁𝙼𝙰𝙽𝙴𝙽𝚃 📄 1) Uploading pornography content 2) Abused Admins , Members 3) Same Link Mirror in multiple bots 4) Share INDEX Link at others group 5) Mirror Without Search 🔍 Files 6) Use Wrong Command 7) Spamming, Flooding with Bots 8) CamRip Content Upload 9) BREAK above Rules 10) Same Link two times Mirror 11) Drugs, illegal , Malware Prohibited 13) Try to clone Private Link 14) Trying To Mirror Webpage / HTML Link 15) Without Join our 💡 CHANNEL 💡you using our Bots 16) Try to Mirror , Amazon , Netflix , Hotstar Premium , Zee5 other's OTT Plateform Premium Content 17) Join our Group with Multiple Account 18) Self promotion, Share Channel Link 19) While Mirror Deleted Link 20) Argument with Adminstrator 21) Share INDEX link and posted on others channel, groups. 22) Playing with bots and time pass 23) Not using bots! But you are stealing the INDEX links 24) Suspicious users 25) Hacker 26) Scammer , Ripper 27) Mirror Software, Games ➖➖➖➖➖➖➖➖➖➖➖➖ 📙 𝐈𝐍𝐃𝐄𝐗 𝐏𝐀𝐒𝐒𝐖𝐎𝐑𝐃: ★ UserName: maxx ★ PassWord: 143 💡𝗛𝗢𝗪 𝗧𝗢 𝗨𝗦𝗘 ❓💡 If you don't know how to use Then Visit: 𝑯𝑬𝑳𝑷 𝑭𝑶𝑹 𝑼𝑺𝑬 𝑩𝑶𝑻𝑺 Otherwise check others people Message or join @MaxxBotChat ▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️▫️ 📮 NOTES 📝 🎋 JOIN OUR LOGS CHANNEL FOR GET YOUR FILES 🔒 For access Drive Link. You must be join our Team Drive. Otherwise you can't access Drive Link 👥 𝙅𝙊𝙄𝙉 𝙏𝙀𝘼𝙈 𝘿𝙍𝙄𝙑𝙀 👤 🎯 Check your Torrent Seeders: Go >> https://checker.openwebtorrent.com/ ✏️ Torrent to Direct Link Generator Bot: @UploadBot 𝙸𝙵 𝚈𝙾𝚄 𝙳𝙸𝙳 𝙰𝙽𝚈 𝙾𝙵 𝚃𝙷𝙴𝚂𝙴!! 𝚈𝙾𝚄 𝚆𝙸𝙻𝙻 𝙱𝙴 𝙱𝙰𝙽 𝙵𝙾𝚁 𝙿𝙴𝚁𝙼𝙰𝙽𝙴𝙽𝚃 ➖➖➖➖➖➖➖➖➖➖➖➖ 🎉🎉 𝐀𝐃𝐌𝐈𝐍 𝐋𝐈𝐒𝐓 🎉🎉 🤴 Owner (KING)= @TG_KingX 👲 Co- Owner = @MaxxRiderz 🕵️ Maintained By = @RangoZex 👤Admins= @Gowtham0625 @CyberW4rriors @Deadpool_2_0 @AbirHasan2005 ⟺⟺⟺⟺⟺⟺⟺⟺⟺⟺⟺⟺⟺⟺ 🏷️ 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐂𝐡𝐚𝐧𝐧𝐞𝐥: @MaxxBots 🎴 𝐋𝐞𝐞𝐜𝐡 𝐆𝐫𝐨𝐮𝐩 : @UploadPro 👤 𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐆𝐫𝐨𝐮𝐩 : @MaxxBotChat 📯 𝗣𝗼𝘄𝗲𝗿𝗲𝗱 𝗕𝘆: @TGFilmZone 📀🇫​​​​​🇦​​​​​🇶​​​​​ 📀 Q: Team Drive Files Are Permanent Stored ? Ans: No ! Any time be can Lost 😶 Q: Do we have to pay to use bots? Ans: No! It's Free Q: The group is permanent?Or will it close? Ans: No ! Any Time can be Closed

No description available

Cloud Computing – De plus en plus utilisé par les entreprises de toutes les industries, le Cloud Computing est la nouvelle forme de stockage de données du 21ème siècle. Cependant, il se décline en de nombreuses variantes, et il n’est pas toujours facile de choisir l’offre qui convient le mieux à son activité. Pour mieux comprendre le phénomène Cloud Computing, voici une définition complète de ce terme. Le Cloud Computing est un terme général employé pour désigner la livraison de ressources et de services à la demande par internet. Il désigne le stockage et l’accès aux données par l’intermédiaire d’internet plutôt que via le disque dur d’un ordinateur. Il s’oppose ainsi à la notion de stockage local, consistant à entreposer des données ou à lancer des programmes depuis le disque dur. La notion de Cloud ne doit pas non plus être confondue avec celle du Network Attached Storage (NAS), utilisée par beaucoup d’entreprises via un serveur en résidence. Ces réseaux locaux n’entrent pas dans la définition du Cloud. Cependant, certains NAS permettent d’accéder aux données à distance depuis Internet. De manière générale, on parle de Cloud Computing lorsqu’il est possible d’accéder à des données ou à des programmes depuis internet, ou tout du moins lorsque ces données sont synchronisées avec d’autres informations sur internet. Il suffit donc pour y accéder de bénéficier d’une connexion internet. L’image du Cloud est utilisée de façon métaphorique pour désigner internet. Cette comparaison date de l’époque à laquelle on représentait les infrastructures gigantesques des fermes de serveurs internet sous la forme d’un grand nuage blanc, acceptant les connexions et distribuant des informations tout en flottant. Cette technologie permet aux entreprises d’acheter des ressources informatiques sous la forme de service, de la même manière que l’on consomme de l’électricité, au lieu d’avoir à construire et entretenir des infrastructures informatiques en interne. Selon U.S. National Institute of Standards and Technology, le Cloud Computing est un modèle permettant d’établir un accès à la demande en réseau vers un bassin partagé de ressources informatiques configurable. Ces ressources sont par exemple des réseaux, des serveurs, de l’espace de stockage, des application et des services. Elles peuvent être approvisionnées rapidement avec un effort de gestion et une interaction avec le fournisseur de services minimes. Le modèle Cloud met en avant la disponibilité, et se compose de cinq caractéristiques essentielles, trois modèles de livraisons, et quatre modèles de déploiement. Profitez de 2 To à vie de stockage en ligne avec pCloud En savoir plus Avantages et inconvénients Cette technologie offre plusieurs avantages et bénéfices pour les utilisateurs professionnels et les utilisateurs finaux. Les trois principaux avantages sont l’approvisionnement en libre-service, l’élasticité, et le paiement à l’utilisation. L’approvisionnement en libre service permet aux utilisateurs finaux d’accéder à n’importe quelle ressource informatique à la demande. L’élasticité offre l’opportunité d’augmenter ou de réduire la consommation de ressources en fonction des besoins de l’entreprise. Enfin, le paiement à l’utilisation autorise les firmes à ne payer que pour les ressources consommées. Pour de nombreuses personnes, le stockage local utilisé pendant les dernières décennies demeure aujourd’hui supérieur au Cloud Computing. Ces personnes considèrent qu’un disque dur permet de garder les données et les programmes physiquement proches, autorisant un accès rapide et simplifié pour les utilisateurs de l’ordinateur ou du réseau local. En 2013, l’ancien roboticien de la NASA Randall Monroe a tenté de prédire quand la bande passante d’internet surpasserait celle de FedEx. Pour cause, peu importe la vitesse d’une connexion internet, il reste moins cher d’envoyer des centaines de giga-octets de données via les avions et les camions de FedEx que par internet. Après réflexion, sa prédiction porte sur l’année 2040. En lisant cette conclusion, Cory Doctorow a perçu une critique implicite du Cloud Computing de la part de Monroe. Selon lui, la vitesse et le coût du stockage local sont moins élevés qu’une connexion en réseau contrôlée par une entreprise de télécommunications. Faire confiance aux opérateurs C’est le principal reproche émis à l’égard du Cloud. Les télécoms, les entreprises de médias et les FAI contrôlent l’accès. Faire entièrement confiance au Cloud signifie également croire en un accès continu aux données sans aucun problème sur le long terme. Un tel confort est envisageable, mais son coût est élevé. De plus, ce prix continuera d’augmenter à mesure que les fournisseurs de Cloud trouvent un moyen de faire payer plus cher en mesurant par exemple l’utilisation du service. Le tarif augmente proportionnellement à la bande passante utilisée. En dehors de ce problème de confiance, de nombreux autres arguments s’opposent au Cloud Computing. Le cofondateur d’Apple, Steve Wozniak, a ainsi critiqué le Cloud en 2012 en présageant de nombreux problèmes de grande envergure dans les cinq années à venir. On peut par exemple redouter des crashs. Durant l’été 2012, Amazon a rencontré ce type de problème. En tant que fournisseur d’entreprises comme Netflix ou Pinterest, l’entreprise américaine a ainsi provoqué la mise hors service des plateformes de ces clients. En 2014, Dropbox, Gmail, Basecamp, Adobe, Evernote, iCloud et Microsoft ont rencontré des problèmes similaires. En 2015, ce fut le tour de Apple, Verizon, Microsoft, AOL, Level 3, Google et Microsoft. Ces désagréments ne durent généralement que quelques heures, mais représentent une perte d’argent colossale pour les entreprises affectées. La question de la propriété intellectuelle Cloud Computing Public, Privé ou Hybride Cloud privé Les services de Cloud Computing se distinguent en trois catégories : le cloud public, le cloud privé et le cloud hybride. Un Cloud privé est une infrastructure entièrement dédiée à une entreprise unique, pouvant être gérée en interne ou par un tiers, et hébergée en interne ou en externe. Ce modèle offre une versatilité aux entreprises, tout en préservant la gestion, le contrôle et la sécurité. Les avantages sont l’accès en self-service à l’interface de contrôle, permettant à l’équipe informatique un approvisionnement rapide, et l’allocation ou la livraison de ressources informatiques à la demande. De même, la gestion des ressources est automatisée, aussi bien pour le stockage ou l’analyse. De même, la sécurité et la gouvernance sont conçues sur mesure pour les besoins spécifiques de l’entreprise. Cloud privé Cloud hybride Les spécificités du Cloud professionnel Le Cloud professionnel est très différent du Cloud utilisé par le grand public. De nombreuses entreprises choisissent d’implémenter des Logiciels en tant que service. Il s’agit d’applications accessibles depuis internet, à l’instar de Salesforce.com. Les Plateformes en tant que service permettent quant à elles aux entreprises de créer leurs propres applications Cloud personnalisées. Enfin, les Infrastructures en tant que service peuvent être louées auprès d’entreprises comme Amazon, Microsoft, Google ou Rackspace. Le Cloud Computing est une industrie qui a généré 100 milliards de dollars en 2012, pourrait générer 127 milliards de dollars en 2017 et 500 milliards en 2020. Profitez de 2 To à vie de stockage en ligne avec pCloud En savoir plus Trois avantages du Cloud Computing en entreprise Le Cloud Computing d’entreprise est un cas spécial d’utilisation du Cloud Computing permettant aux entreprises de bénéficier d’avantages compétitifs de stockage afin de réduire leurs coûts et d’accélérer l’innovation en améliorant la collaboration avec les partenaires et les clients. Plus précisément, le Cloud Computing apporte trois avantages majeurs aux entreprises : Avantage #1 Les coûts des Data Centers et des services informatiques peuvent être réduits et établis de manière proportionnelle à l’utilisation. Selon la quantité d’usage, les coûts seront plus ou moins élevés grâce à l’élasticité rapide. Avantage #2 Avantage #3 Qu’est-ce qui guide le Cloud Computing en entreprise ? Le Cloud Computing d’entreprise est guidé par la réduction des coûts, mais également par les changements du monde extérieur, au-delà du monde de l’entreprise dans notre société hyper-connectée. L’avènement de Consumer IT ou du Web 2.0, des réseaux sociaux et de l’Internet des Objets transforment la façon dont nous vivons, dont nous apprenons, dont nous collaborons, travaillons, consommons et jouons. Ces changements dans la société transforment également la façon dont nous concevons et gérons nos entreprises et notre chaîne de valeur. Le multi-cloud, futur du cloud computing À l’origine, le cloud computing était supposé simplifier les environnements informatiques en entreprise. Cependant, selon une récente étude menée par Microsoft et 451 Research, près d’un tiers des entreprises travaillent avec 4 vendeurs cloud ou plus. De fait, on peut considérer que le multi-cloud est le futur du cloud. Cette tendance est liée à plusieurs facteurs. Tout d’abord, certaines entreprises souhaitent tout simplement avoir davantage d’options. En faisant appel à plusieurs fournisseurs de cloud, pour prendre en charge différentes applications et divers workload, ces entreprises peuvent utiliser la solution qui correspond le mieux à chacun de leurs besoins. En s’appuyant sur un seul modèle cloud, une entreprise risque d’être handicapée. Il est donc inévitable pour les grandes entreprises aux divisions multiples d’utiliser plusieurs clouds. Selon un rapport publié par Ovum, un quart des entreprises européennes ne sont pas satisfaites par leur fournisseur de services cloud, notamment à cause de mauvaises performances, d’une garantie insuffisante, et d’un manque de support personnalisé. Par ailleurs, s’appuyer sur un seul service cloud augmente la vulnérabilité de l’entreprise face à différents problèmes tels que les pannes de data centers ou les problèmes de bande passante. Une application cloud qui est sans cesse hors-ligne donne une mauvaise image de l’entreprise et peut conduire à la perte de clients. Si une application dépend d’un seul fournisseur cloud, il est également difficile de négocier en cas de désaccord. Les controverses liées à la souveraineté des données mènent également à l’essor du multi-cloud, notamment pour les entreprises européennes. Le fait de stocker les données localement minimalise ces problèmes de souveraineté. En revanche, diriger le trafic vers des data centers situés le plus près possible des utilisateurs est indispensable pour les applications en proie à la latence. Le multi-cloud présente des avantages, mais peut aussi représenter un challenge pour les entreprises, notamment pour passer d’un cloud à l’autre. Malheureusement, tous les environnements informatiques sont différents, et le cloud ne fait pas exception. Les fournisseurs cloud font leur possible pour simplifier au maximum le transfert des applications sur leurs plateformes respectives, mais font aussi de leur mieux pour empêcher les clients de quitter leur service. De nombreuses entreprises se soucient, à juste titre, du temps nécessaire pour déplacer des petabytes de données entre deux services cloud. Heureusement, tous les principaux fournisseurs de services cloud utilisent la même technologie Active Data Replication, permettant de déplacer facilement des données entre les clouds. Google a récemment acquis Orbitera, une plateforme prenant en charge le commerce multi-cloud. C’est la preuve que Google considère également les environnements multi-cloud comme un enjeu du futur. Amazon Web Services reste à l’heure actuelle le leader du marché du cloud, mais les entreprises qui souhaitent avoir la liberté de jongler entre plusieurs services cloud et d’éviter de s’astreindre à un seul vendeur pourraient permettre aux autres fournisseurs de prendre leur envol. Selon Gartner, le marché du cloud computing atteindrait une valeur de 240 milliards de dollars dès l’année prochaine. Sur ce marché compétitif, le multi-cloud représente un nouveau front dans la guerre du cloud. Il s’agit d’une bonne nouvelle pour les entreprises en recherche de flexibilité, d’économies, et éventuellement de meilleures solutions. Profitez de 2 To à vie de stockage en ligne avec pCloud En savoir plus IaaS, PaaS et SaaS Même si le Cloud Computing évolue au fil du temps, il est toujours divisé en trois catégories de service : l’infrastructure en tant que service (IaaS), la plateforme en tant que service (PaaS) et le logiciel en tant que service (SaaS). IaaS Les fournisseurs d’Infrastructures en tant que Service, comme AWS, proposent un stockage sur serveur virtuel, mais également des API laissant les utilisateurs transférer leurs charges de travail vers des machines virtuelles (VM). Les IAAS peuvent être des serveurs, des réseaux, de l’espace de stockage ou des espaces au sein de Data Centers. Les utilisateurs disposent d’une capacité de stockage allouée. Ils peuvent ensuite démarrer, arrêter ou configurer la machine virtuelle et le stockage selon leurs désirs. Les infrastructures fournies peuvent être petites, moyennes, grandes ou très grandes pur s’adapter aux différents besoins. Grâce à ce type d’infrastructures, les entreprises n’ont pas besoin d’investir dans leur propre matériel. Les IaaS sont également scalables et flexibles, et s’adaptent à la charge de travail. PaaS SaaS Plusieurs exemples de Cloud Computing La frontière entre le Local Computing et le Cloud Computing est parfois très fine. Pour cause, le Cloud est désormais ancré dans presque toutes les tâches que nous accomplissons sur ordinateur. Ainsi, certains logiciels locaux comme Microsoft Office 365 utilisent le Cloud Computing pour le stockage. Cependant, Microsoft propose également différentes applications basées sur le web, réunies sous Office Online. Il s’agit des versions internet de Word, Excel, PowerPoint et OneNote, accessibles depuis un navigateur internet sans avoir besoin de procéder à ne installation. Autres exemples connus de Cloud Computing Google Drive Google Drive est un pur service Cloud Computing. Il propose un stockage en ligne, et fonctionne avec les applications Cloud Google Docs, Google Sheets et Google Slides. Ce service est accessible depuis un ordinateur, depuis une tablette, ou même depuis un smartphone, au même titre que les applications mobiles Docs et Sheets. La plupart des services Google peuvent d’ailleurs être classés dans la catégorie du Cloud Computing. C’est le cas de Gmail, Google Calendar, et Google Maps par exemple. Apple iCloud Amazon Cloud Drive Des services hybrides comme Box, Dropbox ou SugarSynch se positionnent dans la catégorie Cloud en proposant une version synchronisée sur internet des fichiers stockés. La synchronisation est une pierre angulaire du Cloud Computing, même si l’accès aux fichiers se fait de façon locale. De même, si plusieurs personnes avec des appareils séparés travaillent sur les mêmes données synchronisées, on peut considérer qu’il s’agit de Cloud Computing. Profitez de 2 To à vie de stockage en ligne avec pCloud En savoir plus Le matériel Cloud De plus en plus d’appareils sont entièrement orientés vers le Cloud. C’est le cas des Chromebooks de Google. Il s’agit d’ordinateurs portables proposant juste assez de stockage local pour faire tourner Chrome OS, le système d’exploitation basé sur le navigateur Chrome de Google. Les applications, les fichiers multimédias et le stockage de ces ordinateurs sont tous basés sur le Cloud. Le ChromeBit quant à lui est une petite barre permettant de transformer n’importe quel écran doté d’un port HDMI en un ordinateur sous Chrome OS. Bien sûr, sans connexion internet, ces appareils deviennent strictement inutiles. C’est le principal problème de Chrome OS à l’heure actuelle. Avant le Chromebook, d’autres appareils étaient destinés à fonctionner uniquement avec internet. C’était le cas du NIC (New Internet Computer), du Netpliance iOpener, et du 3Com Ergo Audrey. Ces ordinateurs sans stockage local furent commercialisés dans les années 90. Ils se heurtèrent aux limites techniques de l’époque, notamment en termes de débit. Aujourd’hui, la connexion internet est suffisamment rapide pour rivaliser avec la connexion à un disque dur local. C’est pourquoi le Cloud prend aujourd’hui son envol. SUR LE MÊME SUJET

Responsive Netflix clone built using Next.js & Tailwind CSS. Uses TMDB API to fetch Movie/series information.

This project is a school project aimed at learning and practicing various Git and GitHub concepts, such as branches, merges, rebases, commits, and more.

this is an evolution of a netflix clone made by me earlier in this repository. Netflix 2.0

No description available

A Netflix 2.0

No description available

Netflix 2.0 is built using Next.js 13, TypeScript and TailwindCSS, Firebase and Stripe

No description available

Netflix 2.0

🎬 Welcome to Netflix 2.0! 🎥 Experience the ultimate streaming platform with Netflix 2.0! 🍿✨

No description available

A netflix-inspired movies app project

No description available

Movix is a responsive movie app built with React JS and SCSS. It offers a beautiful layout and a variety of features. With Movix, users can easily explore TV shows and movies .

See App Live

TypeScript | Next.js file system routing | TailwindCSS custom class | Heroicons | Next.js Link | React (+ hooks) | TMDB API | SSR | Material-UI | react-player | Recoiljs for state management | Firebase | atomic design | next-transpile-modules | react-hot-toast | Cloud Firestore | Stripe

Version of the website Netflix with movie trailers

Netflix clone -React,tailwind css,node js,express js,mongodb,firebase