webcomponents
nitter
webcomponents | nitter | |
---|---|---|
34 | 950 | |
4,313 | 9,645 | |
0.2% | - | |
4.4 | 5.3 | |
3 months ago | about 1 month ago | |
HTML | Nim | |
GNU General Public License v3.0 or later | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webcomponents
- "open-stylable" Shadow Roots ยท Issue #909 ยท WICG/webcomponents
-
Web Components Eliminate JavaScript Framework Lock-In
It's not all that shiny. Web components have global names (you should pretty much apply a prefix/namespace if you want to work with others) and managing multiple version of the same component in the same page is an issue in any non trivial codebase (either use a different name per version or fix all breaking changes at once during the upgrade, unless the draft about scoping web elements became standard https://github.com/WICG/webcomponents/blob/gh-pages/proposal... )
-
HTML Web Components
I've recently just started playing with Web Components without a build environment. Meaning, no npm, no bun, no webpack, etc, and no dependencies; in typescript. Intellij can autocompile down to js and the browser view injects a small onchange handler for live updates when developing. So far no problems.
The only thing holding web components back seems to be HTML Modules; being able to link to a .html file instead of a .js file to import a web component. Because of this if you want to use templates or anything more complicated you need to do the ugly inject of .innerHtml = `...`, which I thought would be a problem but the IDE parses the template string very nicely. It would be great to make a component in HTML and any javascript you would put in a tag. It seems like there a lot of bureaucracy involved in getting HTML Modules out the door since its been eight years.<p><a href="https://github.com/WICG/webcomponents/blob/gh-pages/proposals/html-modules-explainer.md#high-level-summary">https://github.com/WICG/webcomponents/blob/gh-pages/proposal...</a>
-
Lit 3 Release Announcement
We're trying to advocate for greater flexibility in cross-component styling. One proposal is "open styleable shadow-roots" which would be an opt-in to let styles from above a component to apply to it's shadow root. I think this would help migration in situations where app teams are currently using global stylesheets.
Feedback and support of the need for something like this would help a lot: https://github.com/WICG/webcomponents/issues/909
-
Things you forgot because of React
))
Part 1.
> I honestly believe that 90% of the dislike for WC comes from the name "connectedCallback". If they'd named it "onCreate" or something, everyone would be using it
Of course not. None of the criticism towards Web Components ever mentions "connectedCallback", or how it should be named differently.
Do you know the actual reason so few are using them? Let's skip the atrocious not-really-high-level not-really-low-level imperative API that they offer.
How about:
- 13 years after introduction they still need 20 more specs to try and patch just some of the holes in their original design: https://w3c.github.io/webcomponents-cg/2022.html
- Shadow DOM is infecting every spec so that the actual useful specs like Scoped CSS have to be delayed almost indefinitely to try and figure out how to work with this abomination of a design
To quote the report linked above, "many of these pain points are directly related to Shadow DOM's encapsulation"
- The amount of specs that are required to make them work, barely, and be "good web citizens". And the amount of APIs.
Oh, you want your custom input to a) be able to send its data in a form, and b) be accessible to a label outside of your component? Well, there's a separate API for a) and there's some separate future API for b). And meanwhile your custom button won't be able to submit your form, sorry, it's a 4-year old issue with no solution: https://github.com/WICG/webcomponents/issues/814
And all that despite the fact that there are already a dozen specs covering web components, and dozens more on their way.
- Web Components ar HTMLElement. It means you cannot use them inside SVGs.
This is impossible:
-
Building a Front End Framework; Reactivity, Composability with No Dependencies
The lit-plugin in for VS Code offers syntax highlighting, jumpt-to-definition, etc: https://marketplace.visualstudio.com/items?itemName=runem.li...
Prettier already supports HTML in html`` strings, likewise, CSS.
> Is there a way in Lit to write the templates in regular HTML rather than a string?
This would require a compiler. You would need to load the HTML into the JS module graph and JS can't do that yet, though there is a proposal for it: https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
Template in HTML also have the problem of the data not being in scope as it is in JS, and there not being an expression language. So you ned up having to re-implement a lot of JS embedded into the HTML syntax, which then preferences a compiler-based approach to make fast. It turns out to be a lot simpler to embed HTML in JS.
-
I am experimenting with Typescript. Is this way of defining a constructor considered normal or an abomination?
It's more than just sugar now. You can't even write web components functionally: https://github.com/WICG/webcomponents/issues/587
-
Declarative Shadow DOM
gzip/brotli handles this very well, but it still is text to parse through.
Some form of declarative CSS module scripts would help a lot. A feature request for that here: https://github.com/WICG/webcomponents/issues/939
- risk of accessible components
-
Templating in HTML
In the past I've seen this one:
https://github.com/WICG/webcomponents/blob/gh-pages/proposal...
Perhaps there are more recent versions.
I liked the spirit of the proposal, but never studied it.
nitter
-
Mobile Ad Blocker Will No Longer Stop YouTube's Ads
Don't use Youtube without going through a proxy like Invidious [1] or Newpipe
Don't use {site} Search without going through a proxy like SearxNG [2]
Don't use TwiXXer without going through a proxy like Nitter - this has gotten more difficult lately but it still works as long as you feed the daemon some registered accounts. Video does not work at the moment but that seems to be fixable.
Don't use Reddit without going through a proxy like libreddit [4]
Start noticing the pattern? Maybe it is time to start producing promotional posters:
The only thing to come between you and ADS could be a proxy / ADS. I'ts just not worth the risk
ADS / New rules for a sane net / Sane net protects you, your partner and your community
A proxy here and a filter there, ADS nowhere
The more you tighten your grip, ${site}, the more viewers will slip through your fingers
[1] https://github.com/iv-org/invidious
[2] https://github.com/searxng/searxng
[3] https://github.com/zedeus/nitter
[4] https://github.com/libreddit/libreddit
- Nitter over IPFS or Torrent
-
Neural Network Diffusion
https://nitter.esmailelbob.xyz/liuzhuang1234/status/17601959...
(bit of trial and error from https://github.com/zedeus/nitter/wiki/Instances)
-
X blocks Taylor Swift searches after fake AI videos go viral
I assume this is why Nitter got slammed and is on the verge of breaking.
https://github.com/zedeus/nitter/issues/1154
- Nitter Shutting Down
-
Nitter Is Dead
The creator of the project left this comment an hour ago:
https://github.com/zedeus/nitter/issues/1155#issuecomment-19...
(HN removed the deep link to the specific comment from the title)
-
Something peculiar in my 2yo's bedroom led me to a revelation about our universe
Most of the time you can just replace twitter.com with nitter.net or nitter.it but when these instances are down or blocked you can use other instances listed here: https://github.com/zedeus/nitter/wiki/Instances
But as the other commenter said Libredirect is the way to go: https://libredirect.github.io/
-
YouTube is loading slower for users with ad blockers yet again
Use a Youtube proxy like Invidious [1], problem solved and you get to subscribe to channels without telling the Beast about your interests. Add Sponsorblock (which supports Invidious) to get rid of any in-stream advertising which remains and you'll be transported back to those hallowed times of yore when men were men, women were women and advertising was something you found in newspapers. Youtube will try to make this harder just like Xitter is trying to make it harder to use proxies like Nitter [2].
[1] https://github.com/iv-org/invidious
[2] https://github.com/zedeus/nitter
-
Nitter.net Has Disappeared
njal.la restored nitter.net, and replied with their reasons: https://github.com/zedeus/nitter/issues/1150#issuecomment-18...
tbh I can totally understand why they acted this way.
- Cloudflare CEO responds to viral termination video
What are some alternatives?
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
fritter - A privacy-friendly Twitter frontend for mobile devices
WHATWG HTML Standard - HTML Standard
NewPipe - A libre lightweight streaming front-end for Android.
custom-elements - All inclusive customElements polyfill for every browser
libreddit - Private front-end for Reddit
shoelace-css - A collection of professionally designed, every day UI components built on Web standards. SHOELACE IS BECOMING WEB AWESOME ๐๐๐
nitter-instances - Automated uptime monitoring of Nitter instances.
design-reviews - W3C specs and API reviews
Invidious - Invidious is an alternative front-end to YouTube
eureka - Lucene-based search engine for your source code
Mastodon - Your self-hosted, globally interconnected microblogging community