I don't know whether it's a Samsung browser update
or a site update,
...[end quoted excerpts]
https://en.wikipedia.org/wiki/Slashdot
...
The mobile interface, added after Slashdot was sold off, was never finished,
and lacks fundamental functionality, like account settings, anonymous posting,
choice of markup style (important because of above lack of UTF-8), etc.
No visible changes to the site have been made since the addition of the mobile
interface and rudimentary asynchronous functionality.
Comment numbers have declined to a tenth compared to its golden age.[100]
As of late Summer 2023, the registration mechanism for new users is disabled,
and manual requests via feedback email must be made.[101]
...
https://slashdot.org
...
America's regional state universities are experiencing steep enrollment declines,
triggering economic crises in the towns that depend on them, while flagship >universities continue to thrive.
...
...
Download for Android
https://www.torproject.org/download/#android
Get Tor Browser for Android.
Protect yourself against tracking, surveillance, and censorship.
Download .apk aarch64 >https://dist.torproject.org/torbrowser/14.5.2/tor-browser-android-aarch64-14.5.2.apk
Download .apk arm >https://dist.torproject.org/torbrowser/14.5.2/tor-browser-android-armv7-14.5.2.apk
Download .apk x86_64 >https://dist.torproject.org/torbrowser/14.5.2/tor-browser-android-x86_64-14.5.2.apk
Download .apk x86 >https://dist.torproject.org/torbrowser/14.5.2/tor-browser-android-x86-14.5.2.apk
...
Can some of you with access to a Samsung browser please try >>https://slashdot.org on a Samsung browser and some other
browsers?
clickbait . . . (maybe fun to test, but it's a jungle out there)
Can some of you with access to a Samsung browser please try https://slashdot.org on a Samsung browser and some other browsers?
I use a Samsung S24 and a Galaxy Tab. Until a few weeks ago, the
Samsung browsers used to render Slashdot like other browsers do.
Something changed; I don't know whether it's a Samsung browser update
or a site update, but it looks radically differnet now - and rather
harder to read, with tiny text. Pinch to zoom allows the text to be magnified, of course, but then the page has to be scrolled sideways
to read entire lines of text.
I'd just like to know why it is like it is. A solution would be
even better!
David Higton <[email protected]> wrote:
Can some of you with access to a Samsung browser please try
https://slashdot.org on a Samsung browser and some other browsers?
I use a Samsung S24 and a Galaxy Tab. Until a few weeks ago, the
Samsung browsers used to render Slashdot like other browsers do.
Something changed; I don't know whether it's a Samsung browser update
or a site update, but it looks radically differnet now - and rather
harder to read, with tiny text. Pinch to zoom allows the text to be
magnified, of course, but then the page has to be scrolled sideways
to read entire lines of text.
I'd just like to know why it is like it is. A solution would be
even better!
Looks fine to me, both in (Samsung) 'Internet' and (Google) Chrome.
Note however that <https://slashdot.org> is redirected to the mobile
site <https://m.slashdot.org>.
Frank Slootweg <[email protected]d> wrote:
David Higton <[email protected]> wrote:
Can some of you with access to a Samsung browser please try
https://slashdot.org on a Samsung browser and some other browsers?
I use a Samsung S24 and a Galaxy Tab. Until a few weeks ago, the
Samsung browsers used to render Slashdot like other browsers do.
Something changed; I don't know whether it's a Samsung browser update
or a site update, but it looks radically differnet now - and rather
harder to read, with tiny text. Pinch to zoom allows the text to be
magnified, of course, but then the page has to be scrolled sideways
to read entire lines of text.
Looks fine to me, both in (Samsung) 'Internet' and (Google) Chrome.
Note however that <https://slashdot.org> is redirected to the mobile
site <https://m.slashdot.org>.
Aha - that's it, thank you, Frank. For some reason my devices had
switched over to the mobile site. Once they're back to non-mobile,
I can read the site on my mobiles.
In message <[email protected]>
Frank Slootweg <[email protected]d> wrote:
David Higton <[email protected]> wrote:
Can some of you with access to a Samsung browser please try
https://slashdot.org on a Samsung browser and some other browsers?
I use a Samsung S24 and a Galaxy Tab. Until a few weeks ago, the
Samsung browsers used to render Slashdot like other browsers do.
Something changed; I don't know whether it's a Samsung browser update
or a site update, but it looks radically differnet now - and rather
harder to read, with tiny text. Pinch to zoom allows the text to be
magnified, of course, but then the page has to be scrolled sideways
to read entire lines of text.
I'd just like to know why it is like it is. A solution would be
even better!
Looks fine to me, both in (Samsung) 'Internet' and (Google) Chrome.
Note however that <https://slashdot.org> is redirected to the mobile
site <https://m.slashdot.org>.
Aha - that's it, thank you, Frank. For some reason my devices had
switched over to the mobile site. Once they're back to non-mobile,
I can read the site on my mobiles.
Something's fundamentally wrong there, isn't it?
Does Samsung's Internet web browser have an option to switch to or ask
for a desktop version of a web site?
As I recall, Samsung's Internet web browser supports extensions. If so,
are you using any that alter the UA header sent by that web client?
David Higton <[email protected]> wrote:
In message <[email protected]>
Frank Slootweg <[email protected]d> wrote:
David Higton <[email protected]> wrote:
Can some of you with access to a Samsung browser please try
https://slashdot.org on a Samsung browser and some other browsers?
I use a Samsung S24 and a Galaxy Tab. Until a few weeks ago, the
Samsung browsers used to render Slashdot like other browsers do.
Something changed; I don't know whether it's a Samsung browser update
or a site update, but it looks radically differnet now - and rather
harder to read, with tiny text. Pinch to zoom allows the text to be
magnified, of course, but then the page has to be scrolled sideways
to read entire lines of text.
I'd just like to know why it is like it is. A solution would be
even better!
Looks fine to me, both in (Samsung) 'Internet' and (Google) Chrome.
Note however that <https://slashdot.org> is redirected to the mobile
site <https://m.slashdot.org>.
Aha - that's it, thank you, Frank. For some reason my devices had
switched over to the mobile site. Once they're back to non-mobile,
I can read the site on my mobiles.
Something's fundamentally wrong there, isn't it?
Are you sure you are (now) using the non-mobile site?
Whether I enter slashdot.org or m.slashdot.org in the address bar, the
end result always is 'https://m.slashdot.org' (checked by tapping on the >address bar). So, I *cannot* use the non-mobile site, even if I want to.
OTOH, if (now) things for you, it's probably not worth (y)our while to
figure out what is (not) happening.
OTTH, we are techies who want to know/understand, aren't we!? :-)
In message <[email protected]>
Frank Slootweg <[email protected]d> wrote:
David Higton <[email protected]> wrote:
In message <[email protected]>
Frank Slootweg <[email protected]d> wrote:
David Higton <[email protected]> wrote:
Can some of you with access to a Samsung browser please try
https://slashdot.org on a Samsung browser and some other browsers?
I use a Samsung S24 and a Galaxy Tab. Until a few weeks ago, the
Samsung browsers used to render Slashdot like other browsers do.
Something changed; I don't know whether it's a Samsung browser update >> >> or a site update, but it looks radically differnet now - and rather
harder to read, with tiny text. Pinch to zoom allows the text to be
magnified, of course, but then the page has to be scrolled sideways
to read entire lines of text.
I'd just like to know why it is like it is. A solution would be
even better!
Looks fine to me, both in (Samsung) 'Internet' and (Google) Chrome.
Note however that <https://slashdot.org> is redirected to the mobile
site <https://m.slashdot.org>.
Aha - that's it, thank you, Frank. For some reason my devices had
switched over to the mobile site. Once they're back to non-mobile,
I can read the site on my mobiles.
Something's fundamentally wrong there, isn't it?
Are you sure you are (now) using the non-mobile site?
Yes. There's a link at the bottom of the page which is either "Mobile"
(if you're *not* using the Mobile view) or "Non-mobile" (if you *are*
using the mobile view) which switches to the other view. In Firefox
on my Linux box I can see the URL change.
Whether I enter slashdot.org or m.slashdot.org in the address bar, the
end result always is 'https://m.slashdot.org' (checked by tapping on the >address bar). So, I *cannot* use the non-mobile site, even if I want to.
See above.
OTOH, if (now) things for you, it's probably not worth (y)our while to
figure out what is (not) happening.
OTTH, we are techies who want to know/understand, aren't we!? :-)
Perhaps the default view setting is stored in a cookie. OTOH I've
told the site I don't accept cookies. Dunno.
VanguardLH <[email protected]> wrote:
Does Samsung's Internet web browser have an option to switch to or ask
for a desktop version of a web site?
Yes, although I can't get it to work logically. All my alterations back
and forth end up displaying the Desktop view now. The thing that *does* change the view is the "Mobile view"/"Non-mobile" link at the bottom of Slashdot's pages.
David Higton <[email protected]> wrote:
VanguardLH <[email protected]> wrote:
Does Samsung's Internet web browser have an option to switch to or ask for a desktop version of a web site?
Yes, although I can't get it to work logically. All my alterations back and forth end up displaying the Desktop view now. The thing that *does* change the view is the "Mobile view"/"Non-mobile" link at the bottom of Slashdot's pages.
Did you visit whatmyuseragent.com to see what UA string your web browser is sending to the server?
In Firefox Desktop, I can go into about:config to change what UA string it sends, so an extension is not needed to lie about what web client is
visiting a site. Firefox Android had about:config removed, so I'd have to use an extension in that one to send a different UA string.
I'd first check what UA string your web browser is sending to the server. That's the starting point to know what the server sees as your web client, and why it may make a decision to show a different view of their web site.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 714 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 138:44:39 |
| Calls: | 12,087 |
| Files: | 14,997 |
| Messages: | 6,517,398 |