Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/02/2025 in all areas

  1. The main thing I miss about "older" goods was the in-built design decisions, for repair-ability. I think, by the time I was born, food stuff had already started declining in quality. There was already information that farming soil was nutritionally depleted, in the 1940's. Clothing was certainly still better, but likely worse than what had previously existed. One of the more notable tragedies is the decline in vehicle quality. If I could pick the era of quality, for a vehicle, it would probably land between the 40's to the mid or late 70's (something with a manual transmission). I think Amazon, as a focus for product decline, high-lights some areas of well deserved and needed attention. There are variables, existing in that scenario, that really only apply to Amazon. I think Amazon's methodology is just one example, of over all trends. In some markets there is very little option, for quality. In others, quality is only advertised/available where it is likely to be afforded. It seems to me that the decline in quality is an attempt to retain spending; this in the face of climbing inflation. If quality products replaced affordable ones the state of things would be more apparent, to the common individual. Instead, we see an increase in housing, some foods, energy, and transportation. With this increase we also see an increase in wages (depending on where you live), but this increase is "not" proportional to market inflation. There are different methods of offsetting (at least perceptually) the disproportional increase in these financial variables. At the grocer, consumers may have noticed the increase in meat and egg prices (maybe a little with dairy). But, that increase does not enough express the actual inflation versus quality of product ratio. The quality of the meat and eggs has decreased, while their price still increased. If you look outside, of the common grocer, these products are even more expensive; in the case of meat four times higher, when previously being nearer to equivalent. The increase in the cost of oats, as another example, is less dramatic. But that cost is offset by methods of growing. The use of pesticides is increased, to speed up the oat drying process. By this practice, the yield "per season" gained enough to offset the consumer unit cost. It kinda looks like (despite making more money, by transitioning to inferior products) that the overall goal is to slant consumer perspective, on the actual state of inflation. Some product actually remains at stable prices, helping secure a perspective of stability. Gasoline is a great example of this, as it's pricing gets lots of attention.
    1 point
  2. Support for EJS is now implemented in yt-dlp master branch. https://github.com/nicolaasjan/yt-dlp/releases/tag/2025.11.01.082330
    1 point
  3. To me, these two statements contradict each other. Not at all. UXP browsers are evolving, but many old extensions are not. Conclusio ultima: These old extensions must be adapted or can otherwise no longer be used. Same applies to old, complete themes which are no longer compatible.
    1 point
  4. Not tested by me: https://greasyfork.org/en/scripts/454587-youtube-always-loop-playlists
    1 point
  5. When using the TURBOLAUNCHER script, you are automatically using the "long", full version of the VORAPIS V3 userscript. The TURBOLAUNCHER script is a launcher which processes and launches the actual VORAPIS V3 userscript. The advantage is for example the processing which is first done before finally loading the complete script for execution in the browser. That's why @UCyborg could execute the replaceALL command before then using this modified version of the userscript locally. So in the end, you are always using the script Vorapis.user.js, only in different variants depending on the code inside the launcher script. Another advantage is that you are always using the most recent version of the VORAPIS V3 userscript without the need to manually modify it. As long as the browser or the userscript have not been fixed, the modified TURBOLAUNCHER 2.1.0.0 userscript is currently the best option for using the VORAPIS V3 frontend in UXP browsers in terms of the already reported issues.
    1 point
  6. I never got the remaining time displayed on the video player. How would that normally work? Usually, I only get the time already elapsed and the total time. I should mention that I am never signed in to my Google Account when playing YT videos in New Moon 28. Edit: I found a working script to retrofit the remaining time on the video player in New Moon 28: https://greasyfork.org/en/scripts/19120-youtube-remaining-time
    1 point
  7. Due to my hardware specs, I can't run 1080p videos on my Windows XP computer, neither in browsers nor in external players. My comment refers to medium qualities up to 480p. But I also use this extension or a script version of h264ify to ensure avoiding unwanted codecs. And I disabled too demanding codecs via prefs.
    1 point
  8. For using this modified script, the @updateURL should be removed as the modification will be overwritten again with the next script update. I use the original script to receive regular updates and to see how the script develops. And all videos I tried to play worked without any problems in New Moon 28. No crashes and no resets after a few seconds as it was before. In any case, YouTube videos are working fine again in UXP browsers and especially in New Moon 28.
    1 point
  9. You didn't follow the discussion. The search box issue only appears when using the VORAPIS V3 frontend and not the original YT interface.
    1 point
  10. You didn't read the previous posts: https://msfn.org/board/topic/185966-my-browser-builds-part-5/?do=findComment&comment=1273128 https://msfn.org/board/topic/185966-my-browser-builds-part-5/?do=findComment&comment=1273143 https://msfn.org/board/topic/185966-my-browser-builds-part-5/?do=findComment&comment=1273152 Long story short. I have already identified the cause of the issue. It is an old bug already fixed in more recent Firefox versions, identified by @roytam1 who will try to fix it if possible.
    1 point
×
×
  • Create New...