217.246.0.0/15 is listed on the Policy Block List (PBL) Outbound Email policy of Deutsche Telekom AG for this IP range DTAG-DIAL17 Deutsche Telekom advises against accepting e-mail from dialup IPs. We provide these IP addresses dynamically to our customers for internet access. Proper e-mail delivery should use dedicated servers, which is why attempts of e-mail delivery from dialup-ranges generally can be traced to compromised computers or other misuse. For further information in english and german please visit: postmaster.t-online.de Wir raten davon ab, E-Mails von Dialup-IPs entgegenzunehmen. Die Deutsche Telekom stellt Kunden diese IPs für den Internetzugang dynamisch zur Verfügung. Eine ordnungsgemäße E-Mail-Zustellung sollte ausschließlich über dedizierte Server erfolgen, da anderweitige Einlieferungen generell auf kompromittierte Rechner zurückzuführen sind. Weitere Informationen finden Sie auf unserer Website: postmaster.t-online.de

The whole damn point of yt-dlp is to download videos from sites, which, according to the lies of the organized crime (aka pirates aka content mafia), is “piracy”. yt-dlp literally exists, to circumvent the artificial scarcity and imaginary monopolism schemes of such criminals, especially when they are state-sponsored by rogue regimes that support them. So what the hell is this?? This is like a VPN going “We’re blocking tianmen-square-trush.org, because China banned it”. You might as well call the project dead by suicide after schizophrenia.

doodstream is blocked, since it's known to host pirated content.

This hasn't yet been scheduled, but we're tracking it on our backlog as something we want to do this year. A few months ago, we arranged for additional capacity to address items like this that have waited for so long. Now that additional capacity is available, it's just a matter of scheduling based on relative priority. We're anxious to get this one done, and I hope to soon have a clearer date to post here.

No it doesn't. I've simply told SvelteKit to ignore the type error from credentials missing. If there's some other issue or missing feature it's not blocked by this. That being said, I wouldn't mind getting this change in

I don't believe the sprockets and sprockets-rails maintainers (actually it's up to the Rails maintainers, see rails/rails#28430) currently consider it broken. (I am not a committer/maintainer on any of those projects). So there is no point in "waiting for someone else to fix" it; that is not going to happen (unless you can change their minds). You just need to figure out the right way to use sprockets 4 with rails as it is.

In the meantime, people do seem to appreciate a developer spending 2 minutes to reply to comments on old issues, just so they’re not ignored and to manage expectations.

I don't understand why this isn't being considered a bigger deal by maintainrs/the community. Don't most Rails developers use SCSS? It's included by default in a new Rails app. Along with sprockets 4. I am mystified how anyone is managing to debug CSS in Rails at all these days, that this issue is being ignored makes sprockets seem like abandonware to me, or makes me wonder if nobody else is using sprockets 4, or what!

Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?

Any idea @AaronLasseigne if this is mergeable?

a triager would be very welcome; someone that can ask follow-up questions on issues, create test cases for the problems, and so on.

Show me good PRs, bug triaging, documentation fixes, whatever and you're a candidate if you ask for it.

Can this be merged please, this fixes a problem I have

Preview/beta release (I wish @hperrin allows it to pull request it here)

I agree, it would be great to join forces and speed up development... Svelte really needs one safe material library option.

Maybe @hperrin would be able to make an appearance and select a few additional maintainers to help out.

Furthermore, how come there's a PR open since 3 months, at what seems to be the authoritative repo for Svelte?

Identify your user agents When deploying software that makes requests to other sites, you should set a custom User-Agent header to identify the software and provide a means to contact its maintainers. Many of the automated requests we receive have generic user-agent headers such as Java/1.6.0 or Python-urllib/2.1 which provide no information on the actual software responsible for making the requests.

But maybe this PR should still be merged until he finds time for that?

Sorry this sat for so long!

TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.

So in theory, one could imagine an organization that produces a different kind of document. Instead of a license for the source code, they would provide a way to say uh, let’s go with “Open Development Certified.” Projects could then submit for certification, they’d get accepted or rejected.