Jump to content

My Browser Builds (Part 3)


Recommended Posts


New NewMoon 27 Build!

32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211211-153837ef4-xpmod.7z
32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211211-153837ef4-xpmod-sse.7z
32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211211-153837ef4-xpmod-ia32.7z

64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20211211-153837ef4-xpmod.7z

source repo: https://github.com/roytam1/palemoon27

repo changes since my last build:
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - pointer style (4cbc8f697)
 - Bug 1173858 - Part 1: Add log module for layout. r=dholbert Add a log module for use by layout. An analog to NS_WARN_IF_FALSE is provided that has the same behavior as NS_WARN_IF_FALSE: it's debug only and emits a message prefixed with '[pid] WARNING', includes the condition being checked, file name and line number. (3aabc4c8f)
 - Bug 1173858 - Part 2: Use LAYOUT_WARN_IF_FALSE to silence some verbose layout warnings by default. r=dholbert (2a7efec8f)
 - Bug 1173858 - Part 3 - Reindent blocks that we've converted to use LAYOUT_WARN_IF_FALSE. r=dholbert (1460ed697)
 - pointer style (72daf612c)
 - Bug 1063147: Clarify comments about extensible strings. DONTBUILD r=jandem (036b9c9b4)
 - Bug 1145882 - Part 2/2 - Add -v and --version. r=evilpie (8b2d03df1)
 - Bug 1001975 - Enable -Wuninitialized warnings as errors. r=glandium (b74ec63bb)
 - Bug 1183480 - Return old timeout value in setScriptTimeout(), r=bholley. (295a9098a)
 - Bug 1155393 - Port the -Wno-inline-new-delete option from configure.in to the JS configure script; r=dholbert (a2ad6fafc)
 - ad bug component (94bcaa0a1)
 - NO BUG - Fix reStructuredText warnings (584b0b97a)
 - missing parts of Bug 895248 - Move --enable-stdcxx-compat in build/unix/mozconfig.linux (814b5d8fb)
 - style and namespaces (9f6bb417d)
 - Bug 1136046 - Increase maximum capacity of js::HashMap and HashSet r=luke (bf1f96bc6)
 - pointer style (5ac65529a)
 - pointer style (f5623e2b7)
 - Bug 1139570: JS GDB pretty-printer: Add a pretty-printer for js::InterpreterRegs. DONTBUILD r=ttromey (1c642e7fe) (90fdf91e1)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1181392 part 1 - Remove use of IsFinishedTransition from Animation::CanThrottle; r=dbaron (a1460a571)
 - Bug 1181392 part 2 - Remove use of IsFinishedTransition from Animation::ComposeStyle; r=dbaron (69363e99a)
 - Bug 1181392 part 3 - Remove use of IsFinishedTransition in KeyframeEffectReadOnly; r=dbaron (41b1dc12d)
 - Bug 1181392 part 4 - Remove use of IsFinishedTransition from nsLayoutUtils; r=dbaron (4ce9c8a90)
 - Bug 771367 - Refactor GetAnimationContent and GetAnimationCollection into CommonAnimationManager to hide atom and pseudo-element voodoo. r=bbirtles (699c8ae54)
 - Bug 1181392 part 5 - Remove use of IsFinishedTransition from AnimationCollection::HasAnimationOfProperty; r=dbaron (fb261816f)
 - Bug 1181392 part 6 - Remove use of IsFinishedTransition from nsTransitionManager::StyleContextChanged; r=dbaron (1a2241272)
 - Bug 1181392 part 7 - Remove use of IsFinishedTransition from nsTransitionManager::ConsiderStartingTransition; r=dbaron (9b6e7f322)
 - Bug 1181392 part 8 - Remove use of IsFinishedTransition from nsTransitionManager::PruneCompletedTransitions; r=dbaron (3f31365ac)
 - Bug 1181392 part 9 - Remove use of IsFinishedTransition from nsTransitionManager::FlushTransitions; r=dbaron (77374c339)
 - Bug 1181392 part 10 - Remove KeyframeEffect::IsFinishedTransition; r=dbaron (6db3a358b)
 - Bug 1188251 part 1 - Remove transitions cleanup from FlushTransitions; r=dholbert (3c0da49eb)
 - Bug 1188251 part 2 - Check if a tick can be throttled in FlushAnimations using Animation::CanThrottle; r=dholbert (a1bdf30da)
 - Bug 1188251 part 3 - Add AnimationCollection::RequestRestyle; r=dholbert (9a4c3fc6d)
 - Bug 1188251 part 4 - Move throttling checks to AnimationCollection::RequestRestyle; r=dholbert (da289d243)
 - Bug 1188251 part 5 - Move some assertions from FlushTransitions to RequestRestyle; r=dholbert (e41698092)
 - Bug 1188251 part 6 - Unify FlushAnimations and FlushTransitions; r=dholbert (2ac375897)
 - Bug 1188251 part 7 - Move WillRefresh to CommonAnimationManager; r=dholbert (df81a5ce3)
 - Bug 1188251 part 8 - Remove call to Animation::Tick from CheckAnimationRule; r=dholbert (c7a0409b7)
 - Bug 1188251 part 9 - Request restyles from Animation::Tick; r=dholbert (d0695155c)
 - Bug 1061364 - Don't force transitions to refresh their style rule; r=dbaron (d6c6003d4)
 - remove restyle on refresh (85a3c522c)
 - Bug 1188251 part 10 - Remove throttling from EnsureStyleRuleFor; r=dholbert (726ce1c87)
 - Bug 1188251 part 11 - Add RestyleType::Layer; r=dholbert (c7602af18)
 - Bug 1188251 part 12 - Use RestyleType::Layer in UpdateCascade; r=dholbert (3a7639c8d) (32ae2dd91)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1194028 - Part 1: Implement Animation NotifyEffectTimingUpdate and KeyframeEffect SetTiming. r=bbirtles (ebdf90981)
 - Bug 1194028 - Part 2: Use KeyFrameEffect SetTiming. r=bbirtles (770edf4ab)
 - Bug 1187804 - Annotate fixed-position layers with the scroll id of the scroll frame that they are fixed with respect to. r=mattwoodrow (b37b8a9e6)
 - Bug 1209471 - Fix group used for Array.concat result, r=jandem. (fa0aba56d)
 - missing tests of Bug 1183623, redirect keyup events to keydown target when focus shifts from chrome to content in-between (15634dd01)
 - Bug 1183623, redirect keyup events to keydown target when focus shifts from chrome to content in-between, r=smaug (7316efd4f)
 - pointer style (daaa76131)
 - Bug 1155238: use RelengAPI-based Tooltool server. r=coop (9501de0ac)
 - Bug 1140182: JS GDB pretty-printers: Implement pretty-printer for js::AbstractFramePtr. r=sfink (02228c34e)
 - Bug 1139535: In js/src/gdb: Remove workaround for 2012 GDB bug. DONTBUILD r=sfink (7e08a0070)
 - Bug 1140179: Adapt to new JSObject structure, which indirects through the ObjectGroup. DONTBUILD r=sfink (9c93cf5f8)
 - Bug 1141032: fix = instead of == in an assert in NativeRegexpMacroAssembler.cpp; r=h4writer (f07efb736)
 - Bug 1137573 - OdinMonkey: Generalize alignment analysis to handle adds with multiple uses r=luke a=ryanvm (0c437d56c)
 - spacing (6938ecef8)
 - Bug 1151326 - Don't inline yields in legacy generators in Baseline. r=shu (89b09ea28)
 - pointer style (12437a045)
 - Bug 1151634 - Patch a valid return address for debug mode OSR from exception handler when profiling is enabled. (r=jandem) (0453d85b7)
 - pointer style (3e4a597ca)
 - Pointer style (d0e273439)
 - pointer style (ec0540b7c) (eb5953764)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 865222 - Add MOZ_GUARD_OBJECT_NOTIFIER_PARAM to JSAutoCompartmentand JSAutoNullableCompartment; r=efaust (97d89fcd7)
 - Bug 1131325 - Move system country code from nsIGfxInfo2 to a more appropriate location. r=aklotz,smichaud (afb055f6b)
 - Bug 1192456 - Use perfect forwarding for DispatchWrapper rather than explicit move and copy constructors. r=terrence (bd30eb21e)
 - Bug 1155726 - OdinMonkey: add new cache failure code for when storage initialization fails (r=janv) (60fb4de2a)
 - Bug 1155292 - Add a check for properties found on non-native prototypes during Ion caching, r=jandem. (6864981f7)
 - pointer style (28c86a2d7) (618cb9622)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - pointer style (73474b840)
 - Bug 1152784 - Be more robust about possible intermediate wrappers in IsFrameId. r=bz (fb81861cc)
 - pointer style (c0b667212)
 - Bug 1180123 (part 1) - Report the size of the saved stacks sets. r=fitzgen. (e6c3a9609)
 - Bug 1180123 (part 2) - Minor nursery report fixes. r=terrence. (172525db9)
 - Bug 1181175 - Use RDTSC for Performance Monitoring instead of getrusage. r=jandem (b970bf5f1)
 - Bug 1190436 - Part 1: Use more smart pointers in XPConnect. r=gabor (c80d65dee)
 - Bug 1190436 - Part 2: Use an early return in XPCConvert::JSObject2NativeInterface. r=gabor (ef2123643)
 - Bug 1161491 - schedulePreciseGC should use the normal GC triggering mechanisms, r=mccr8 (42cdfa847)
 - pointer style (8a147bec5)
 - Bug 1155773 - Remove gotos from XPCConvert::NativeArray2JS(). r=bholley (a8858d358)
 - Bug 1164061 - WebRTC - move TMMBR behind pref r=jesup (36ba20713)
 - Bug 1164061 - Backout signaling unittest changes for tmmbr r=jesup (f2fbd86be)
 - Bug 1165520: Negotiate rtcp-fb r=jesup (449edaa83)
 - Bug 1165129: Allow JS to reorder codecs in a local answer. Also means that we'll take the ordering more seriously when we see multiple codecs in a remote answer. r=jesup (c1ab58747)
 - Bug 818640 - Test that using dynamic payload types < 96 works. r=mt (dfa3418cf)
 - Bug 952145: Rollback support r=mt, r=smaug (28182262b)
 - code style (ecaf69b5a)
 -  Bug 1187773 - Don't include heapapi.h from js/public. r=jorendorff (40179ec4e)
 - pointer style (f6e3d0610)
 - Bug 1196590 - Don't assume that objects without shapes are unboxed plain objects, r=jandem. (75cd29b7b)
 - Bug 1194430 - Always mark the global jitcode table during major GCs. (r=djvj) (772e96665)
 - Bug 1036574 - Revert horrible workaround in baseline IC for magic arg callee. (r=me) (b5f11337a)
 - spurious spaces (80b22a36a) (d7187c26b)
- ported changes from mozilla upstream:
 - Bug 1181175 - Telemetry for finding out how often our process is rescheduled to another CPU. r=jandem, r=bsmedberg
 - Bug 1181175 - Get rid of test_compartments.js. r=yoric
 - and fix js configure winver (153837ef4)

  • Like 3
Link to comment
Share on other sites

New regular/weekly KM-Goanna release:
https://o.rthost.win/kmeleon/KM76.4.5-Goanna-20211211.7z

Changelog:

In-tree changes:
- app: don't set DEBUG, fix linking with newer goanna3 (7c323631)

Out-of-tree changes:
* update Goanna3 to git dd0f21a90...153837ef4:
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - pointer style (4cbc8f697)
 - Bug 1173858 - Part 1: Add log module for layout. r=dholbert Add a log module for use by layout. An analog to NS_WARN_IF_FALSE is provided that has the same behavior as NS_WARN_IF_FALSE: it's debug only and emits a message prefixed with '[pid] WARNING', includes the condition being checked, file name and line number. (3aabc4c8f)
 - Bug 1173858 - Part 2: Use LAYOUT_WARN_IF_FALSE to silence some verbose layout warnings by default. r=dholbert (2a7efec8f)
 - Bug 1173858 - Part 3 - Reindent blocks that we've converted to use LAYOUT_WARN_IF_FALSE. r=dholbert (1460ed697)
 - pointer style (72daf612c)
 - Bug 1063147: Clarify comments about extensible strings. DONTBUILD r=jandem (036b9c9b4)
 - Bug 1145882 - Part 2/2 - Add -v and --version. r=evilpie (8b2d03df1)
 - Bug 1001975 - Enable -Wuninitialized warnings as errors. r=glandium (b74ec63bb)
 - Bug 1183480 - Return old timeout value in setScriptTimeout(), r=bholley. (295a9098a)
 - Bug 1155393 - Port the -Wno-inline-new-delete option from configure.in to the JS configure script; r=dholbert (a2ad6fafc)
 - ad bug component (94bcaa0a1)
 - NO BUG - Fix reStructuredText warnings (584b0b97a)
 - missing parts of Bug 895248 - Move --enable-stdcxx-compat in build/unix/mozconfig.linux (814b5d8fb)
 - style and namespaces (9f6bb417d)
 - Bug 1136046 - Increase maximum capacity of js::HashMap and HashSet r=luke (bf1f96bc6)
 - pointer style (5ac65529a)
 - pointer style (f5623e2b7)
 - Bug 1139570: JS GDB pretty-printer: Add a pretty-printer for js::InterpreterRegs. DONTBUILD r=ttromey (1c642e7fe) (90fdf91e1)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1181392 part 1 - Remove use of IsFinishedTransition from Animation::CanThrottle; r=dbaron (a1460a571)
 - Bug 1181392 part 2 - Remove use of IsFinishedTransition from Animation::ComposeStyle; r=dbaron (69363e99a)
 - Bug 1181392 part 3 - Remove use of IsFinishedTransition in KeyframeEffectReadOnly; r=dbaron (41b1dc12d)
 - Bug 1181392 part 4 - Remove use of IsFinishedTransition from nsLayoutUtils; r=dbaron (4ce9c8a90)
 - Bug 771367 - Refactor GetAnimationContent and GetAnimationCollection into CommonAnimationManager to hide atom and pseudo-element voodoo. r=bbirtles (699c8ae54)
 - Bug 1181392 part 5 - Remove use of IsFinishedTransition from AnimationCollection::HasAnimationOfProperty; r=dbaron (fb261816f)
 - Bug 1181392 part 6 - Remove use of IsFinishedTransition from nsTransitionManager::StyleContextChanged; r=dbaron (1a2241272)
 - Bug 1181392 part 7 - Remove use of IsFinishedTransition from nsTransitionManager::ConsiderStartingTransition; r=dbaron (9b6e7f322)
 - Bug 1181392 part 8 - Remove use of IsFinishedTransition from nsTransitionManager::PruneCompletedTransitions; r=dbaron (3f31365ac)
 - Bug 1181392 part 9 - Remove use of IsFinishedTransition from nsTransitionManager::FlushTransitions; r=dbaron (77374c339)
 - Bug 1181392 part 10 - Remove KeyframeEffect::IsFinishedTransition; r=dbaron (6db3a358b)
 - Bug 1188251 part 1 - Remove transitions cleanup from FlushTransitions; r=dholbert (3c0da49eb)
 - Bug 1188251 part 2 - Check if a tick can be throttled in FlushAnimations using Animation::CanThrottle; r=dholbert (a1bdf30da)
 - Bug 1188251 part 3 - Add AnimationCollection::RequestRestyle; r=dholbert (9a4c3fc6d)
 - Bug 1188251 part 4 - Move throttling checks to AnimationCollection::RequestRestyle; r=dholbert (da289d243)
 - Bug 1188251 part 5 - Move some assertions from FlushTransitions to RequestRestyle; r=dholbert (e41698092)
 - Bug 1188251 part 6 - Unify FlushAnimations and FlushTransitions; r=dholbert (2ac375897)
 - Bug 1188251 part 7 - Move WillRefresh to CommonAnimationManager; r=dholbert (df81a5ce3)
 - Bug 1188251 part 8 - Remove call to Animation::Tick from CheckAnimationRule; r=dholbert (c7a0409b7)
 - Bug 1188251 part 9 - Request restyles from Animation::Tick; r=dholbert (d0695155c)
 - Bug 1061364 - Don't force transitions to refresh their style rule; r=dbaron (d6c6003d4)
 - remove restyle on refresh (85a3c522c)
 - Bug 1188251 part 10 - Remove throttling from EnsureStyleRuleFor; r=dholbert (726ce1c87)
 - Bug 1188251 part 11 - Add RestyleType::Layer; r=dholbert (c7602af18)
 - Bug 1188251 part 12 - Use RestyleType::Layer in UpdateCascade; r=dholbert (3a7639c8d) (32ae2dd91)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 1194028 - Part 1: Implement Animation NotifyEffectTimingUpdate and KeyframeEffect SetTiming. r=bbirtles (ebdf90981)
 - Bug 1194028 - Part 2: Use KeyFrameEffect SetTiming. r=bbirtles (770edf4ab)
 - Bug 1187804 - Annotate fixed-position layers with the scroll id of the scroll frame that they are fixed with respect to. r=mattwoodrow (b37b8a9e6)
 - Bug 1209471 - Fix group used for Array.concat result, r=jandem. (fa0aba56d)
 - missing tests of Bug 1183623, redirect keyup events to keydown target when focus shifts from chrome to content in-between (15634dd01)
 - Bug 1183623, redirect keyup events to keydown target when focus shifts from chrome to content in-between, r=smaug (7316efd4f)
 - pointer style (daaa76131)
 - Bug 1155238: use RelengAPI-based Tooltool server. r=coop (9501de0ac)
 - Bug 1140182: JS GDB pretty-printers: Implement pretty-printer for js::AbstractFramePtr. r=sfink (02228c34e)
 - Bug 1139535: In js/src/gdb: Remove workaround for 2012 GDB bug. DONTBUILD r=sfink (7e08a0070)
 - Bug 1140179: Adapt to new JSObject structure, which indirects through the ObjectGroup. DONTBUILD r=sfink (9c93cf5f8)
 - Bug 1141032: fix = instead of == in an assert in NativeRegexpMacroAssembler.cpp; r=h4writer (f07efb736)
 - Bug 1137573 - OdinMonkey: Generalize alignment analysis to handle adds with multiple uses r=luke a=ryanvm (0c437d56c)
 - spacing (6938ecef8)
 - Bug 1151326 - Don't inline yields in legacy generators in Baseline. r=shu (89b09ea28)
 - pointer style (12437a045)
 - Bug 1151634 - Patch a valid return address for debug mode OSR from exception handler when profiling is enabled. (r=jandem) (0453d85b7)
 - pointer style (3e4a597ca)
 - Pointer style (d0e273439)
 - pointer style (ec0540b7c) (eb5953764)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - Bug 865222 - Add MOZ_GUARD_OBJECT_NOTIFIER_PARAM to JSAutoCompartmentand JSAutoNullableCompartment; r=efaust (97d89fcd7)
 - Bug 1131325 - Move system country code from nsIGfxInfo2 to a more appropriate location. r=aklotz,smichaud (afb055f6b)
 - Bug 1192456 - Use perfect forwarding for DispatchWrapper rather than explicit move and copy constructors. r=terrence (bd30eb21e)
 - Bug 1155726 - OdinMonkey: add new cache failure code for when storage initialization fails (r=janv) (60fb4de2a)
 - Bug 1155292 - Add a check for properties found on non-native prototypes during Ion caching, r=jandem. (6864981f7)
 - pointer style (28c86a2d7) (618cb9622)
- import changes from `dev' branch of rmottola/Arctic-Fox:
 - pointer style (73474b840)
 - Bug 1152784 - Be more robust about possible intermediate wrappers in IsFrameId. r=bz (fb81861cc)
 - pointer style (c0b667212)
 - Bug 1180123 (part 1) - Report the size of the saved stacks sets. r=fitzgen. (e6c3a9609)
 - Bug 1180123 (part 2) - Minor nursery report fixes. r=terrence. (172525db9)
 - Bug 1181175 - Use RDTSC for Performance Monitoring instead of getrusage. r=jandem (b970bf5f1)
 - Bug 1190436 - Part 1: Use more smart pointers in XPConnect. r=gabor (c80d65dee)
 - Bug 1190436 - Part 2: Use an early return in XPCConvert::JSObject2NativeInterface. r=gabor (ef2123643)
 - Bug 1161491 - schedulePreciseGC should use the normal GC triggering mechanisms, r=mccr8 (42cdfa847)
 - pointer style (8a147bec5)
 - Bug 1155773 - Remove gotos from XPCConvert::NativeArray2JS(). r=bholley (a8858d358)
 - Bug 1164061 - WebRTC - move TMMBR behind pref r=jesup (36ba20713)
 - Bug 1164061 - Backout signaling unittest changes for tmmbr r=jesup (f2fbd86be)
 - Bug 1165520: Negotiate rtcp-fb r=jesup (449edaa83)
 - Bug 1165129: Allow JS to reorder codecs in a local answer. Also means that we'll take the ordering more seriously when we see multiple codecs in a remote answer. r=jesup (c1ab58747)
 - Bug 818640 - Test that using dynamic payload types < 96 works. r=mt (dfa3418cf)
 - Bug 952145: Rollback support r=mt, r=smaug (28182262b)
 - code style (ecaf69b5a)
 -  Bug 1187773 - Don't include heapapi.h from js/public. r=jorendorff (40179ec4e)
 - pointer style (f6e3d0610)
 - Bug 1196590 - Don't assume that objects without shapes are unboxed plain objects, r=jandem. (75cd29b7b)
 - Bug 1194430 - Always mark the global jitcode table during major GCs. (r=djvj) (772e96665)
 - Bug 1036574 - Revert horrible workaround in baseline IC for magic arg callee. (r=me) (b5f11337a)
 - spurious spaces (80b22a36a) (d7187c26b)
- ported changes from mozilla upstream:
 - Bug 1181175 - Telemetry for finding out how often our process is rescheduled to another CPU. r=jandem, r=bsmedberg
 - Bug 1181175 - Get rid of test_compartments.js. r=yoric
 - and fix js configure winver (153837ef4)

* Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.

A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

  • Upvote 1
Link to comment
Share on other sites

For the time being ImgUr works if I am logged in. It is a conspiracy by the whole industry to keep us on the update cycle and buy new computers, and load them with Google spyware.

  • Like 1
Link to comment
Share on other sites

16 hours ago, IXOYE said:

Hi

Here is another streaming website that doesn't work at home since yesterday, with all uxp browsers from Roytam1:no:. The website odysee.com displays a blank page, but it works with 360chrome.
"https://odysee.com" which is under the control of Google.:thumbdown

 

Videos play fine under XP64 for me using both newmoon or serpent. Most sites play videos fine except bitchute.

odysee.JPG

Edited by tekkaman
Link to comment
Share on other sites

Odyssey works now in New Moon 28. But it showed a white page earlier this morning. Serpent shows an error page "Aw Shucks! Try refreshing the app to fix it."

Edited by j7n
Link to comment
Share on other sites

Hi

4 hours ago, tekkaman said:

Videos play fine under XP64 for me using both newmoon or serpent. Most sites play videos fine except bitchute.

This was a strange failure that displayed a blank page on launch on odysee.com on all Roytam1 uxp browsers, but inexplicably it worked on Windows 10 with Edge and especially with 360chrome browsers on Windows XP. Now it works again on uxp browsers, as if my original post about this problem was heard by the all-seeing eye on the internet.:ph34r:

Link to comment
Share on other sites

22 hours ago, NotHereToPlayGames said:

No!

It's an indication that your browser is outdated!  Nothing more than that, no "conspiracy" going on, no "hidden agenda" to 'block alternative media'!

outdated because it doesn't tow the google line? I disagree.

They are purposely breaking 3rd party browsers with layers they dont support.

shame

Link to comment
Share on other sites

6 hours ago, j7n said:

Odyssey works now in New Moon 28. But it showed a white page earlier this morning. Serpent shows an error page "Aw Shucks! Try refreshing the app to fix it."

same here but no changes made on my end

Link to comment
Share on other sites

25 minutes ago, kartel said:

outdated because it doesn't tow the google line? I disagree.

They are purposely breaking 3rd party browsers with layers they dont support.

shame

I can agree to that.  Mostly.

I thought at first that you were implying that Roytam's hidden agenda was to block alternative media.

But I still think there's another side to the coin.

Look at it this way - let's agree that "googleims" intentionally break 3rd party browsers, let's agree that "googleisms" is a way for Google to censor what they don't want us to see.

So how does that effect blocking alternative media?

Let's use "wings" to illustrate.

Let's agree that "googleims" is a LEFT WING way to "silence" the RIGHT WING.

So if I am the owner of a RIGHT WING "alternative media" website, why would I rely on "googleisms" (code provided by Google) KNOWING they don't work in 3rd party browsers?  Answer - I wouldn't!

The "conspiracy" really doesn't hold much water.  Nobody is FORCING the owner of the RIGHT WING website to use code from LEFT WING corporations.

The fact is, you can use "googletagmanager" and "googleanalytics" WITHOUT breaking 3rd party web browsers.

If the web site owner is too STUPID or LAZY to know how to do that, then they have nobody but themselves to blame that their website doesn't "work" in 3rd party web browsers.

But it also comes down to "market share".

Whether WE like it or not, the owner of any website KNOWS what browsers visit their website.

And whether WE like it or not, that owner sees 2 million visitors and the number of visiting via a 3rd party web browser can be counted on ONE HAND.

So, no!  That web site owner really doesn't need to bend over backwards for those count-on-one-hand visitors.

 

I guess that was more my point.  But anywhoo...  No skin off my back...

Edited by NotHereToPlayGames
  • Like 1
Link to comment
Share on other sites

These browsers are quite capable in fact. The ones with WASM support can run the whole f****** DOOM 3 engine inside and it won't hang it like many of the crap "websites" do.

They could send motion picture from the f****** moon over 50 years ago to much simpler TV sets, they could send picture to a web browser in 2021 that's only few years behind some stupid JavaScript bells and whistles.

If I can run a web app in the "outdated" browser that can send command to access controller to activate the output where the bomb has been wired instead of the alarm to BLOW s*** UP, then your ***** website could do something more interesting as well rather than waste CPU cycles.

Example of a more or less proper website:

http://motherf***ingwebsite.com/

Damn, I'm p***ed!

PS: I don't condone actually blowing s*** up.

It's a real problem for instance that some people can't use these browsers for stuff like banking anymore because of abuse of JavaScript some sites employ.

Edited by UCyborg
  • Like 2
Link to comment
Share on other sites

6 hours ago, NotHereToPlayGames said:

Let's [stipulate] that "googleisms" [are] a LEFT WING way to "silence" the RIGHT WING.

So if I am the owner of a RIGHT WING "alternative media" website, why would I rely on "googleisms" (code provided by Google) KNOWING they don't work in 3rd party browsers?  Answer - I wouldn't!

The "conspiracy" really doesn't hold much water.  Nobody is FORCING the owner of the RIGHT WING website to use code from LEFT WING corporations.

The fact is, you can use "googletagmanager" and "googleanalytics" WITHOUT breaking 3rd party web browsers.

If the web site owner is too STUPID or LAZY to know how to do that, then they have nobody but themselves to blame that their website doesn't "work" in 3rd party web browsers.

Well said! (BTW, one might point out that the (actual) left wing has plenty of problems with Google too.) But let me take (slight) issue with the following, as I think it leads to some interesting discussion:

6 hours ago, NotHereToPlayGames said:

But it also comes down to "market share".

Whether WE like it or not, the owner of any website KNOWS what browsers visit their website.

And whether WE like it or not, that owner sees 2 million visitors and the number of visiting via a 3rd party web browser can be counted on ONE HAND.

So, no!  That web site owner really doesn't need to bend over backwards for those count-on-one-hand visitors.

I think the problem there is the implication that a Webmaster must take special effort to keep their Web site compatible with older browsers. But that's not correct. Browsers are computer software, not mechanical devices; they don't just "wear out" and stop working without maintenance! All you have to do to keep a Web site compatible with older browsers is nothing! And the best part is, newer browsers will still work with the site too! That's exactly what I'd expect a "lazy" Webmaster to do!

Instead, someone has to take special effort to change a Web site in order to make it incompatible with older browsers. But why would a Webmaster do such a thing, even if the "cost" is only a few dozen users out of thousands? (Seriously, I doubt BitChute gets millions, but the point remains.) I think that usually, they don't! Instead, they lease time/storage from a server farm (at AWS?) that just installs all the latest "upgrades" for them as they come out. Of course those "upgrades" intentionally break compatibility with older browsers, forcing their visitors to either upgrade too (possibly to a new Windows version) or stop visiting - but like the old Grecian Formula 16 hair dye, it's so gradual the Webmasters don't even notice it!

20 hours ago, j7n said:

It is a "conspiracy" by the whole industry to keep us on the update cycle and buy new computers, and load them with Google spyware.

Right! Except it's not really a conspiracy - a secret agreement to do something illegal - so much as companies each acting in their own self-interest; i.e., to make as much money as possible. But even without any explicit agreements, it has the same result: the whole industry keeps us on the update treadmill, buying new, more powerful computers not to do more, but merely to run the latest bloatware that spends the majority of our PC's CPU cycles trying to convince us to part with our hard-earned dollars.

  • Like 4
  • Upvote 1
Link to comment
Share on other sites

3 hours ago, Mathwiz said:

All you have to do to keep a Web site compatible with older browsers is nothing! And the best part is, newer browsers will still work with the site too! That's exactly what I'd expect a "lazy" Webmaster to do!

Instead, someone has to take special effort to change a Web site in order to make it incompatible with older browsers.

I'll disagree, even if only to play Devil's Advocate.

I think the vast majority of the "internet" is basically like MSFN.

And I scroll all the way to the bottom and I see this  --  "© 2001 - 2021 MSFN" and "Powered by Invision Community".

Does the "owner" of MSFN rewrite code for this web site with the intentions of making it "heavier" or to make it only work on "newer" computers?  My answer is "heck no!".

But said "owner" will perform scheduled "maintenance" only to let "Powered by Invision Community" add whatever THEY think should be added.

Did the webmaster write code to prevent older computers from accessing the site?

Or was the webmaster simply performing "lazy maintenance" and did whatever "Powered by Invision Community" told them to do in order to increment the "copyright date"?

Granted, I've never "owned" a website.

I just don't think that "webmasters" really do the bulk of the "code", I think they use "modules" written by large corporations and they update those "modules" under the guise of "security", "Powered by Invision Community" sends the webmaster an email, "Please update your module, the previous module is vulnerable to security attacks."  And so the webmaster updates the "module".

Just to be Devil's Advocate.  I've never "owned" a website.

 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share



×
×
  • Create New...