Well it took some effort but now I can read Aftenposten from the terminal, with #Newsboat and #LynxBrowser.
Complications were:
=> More informations about this toot | More toots from ruario@vivaldi.net
News articles from a range of news sites tend to display very well in Lynx. The landing pages for them however are often hit and miss and this is where an RSS reader like Newsboat comes in because you get to skip the front page entirely. 😉
=> View attached media | View attached media
=> More informations about this toot | More toots from ruario@vivaldi.net
Ok, I repeated the export from Vivaldi and import into Lynx process for login cookies needed for e24.no now as well.
This definitely is the easiest way to deal with the complex login methods modern sites tend to use. Because once you are in, you are in. Then you don't have to worry about it any more.
=> More informations about this toot | More toots from ruario@vivaldi.net
@ruario
... until it times out or becomes invalid for some other reason.
=> More informations about this toot | More toots from leeloo@techhub.social
@leeloo True but for many of these sites if you go there regularly the login cookies just get renewed/updated.
I any case I don't mind repeating the process, so long as it is not often. Once or twice a year and I won't worry about it. More often… perhaps. 😉
=> More informations about this toot | More toots from ruario@vivaldi.net
@ruario
If it's a site you pay for, and you pay monthly (or have the option to pay monthly), I would expect them to expire after no more than a month.
If they get renewed without javascript? Hard to tell.
=> More informations about this toot | More toots from leeloo@techhub.social
@leeloo Yes Aftenposten is a paid site, with payments on a monthly basis. The main login cookie currently has an expiry date one set to Dec 14 2025, which would appear to be a year after I first logged into this session.
If I (or actually my wife) stops paying, I presume they just no longer accept that cookie for access to content.
As for getting renewed, yes we will see but other cookies the site issues are updating.
I'm not especially worried and expect it to work. But again, we'll see. 😉
=> More informations about this toot | More toots from ruario@vivaldi.net
@ruario
Of course you already checked the expiry date🧐🧑🎓 I didn't think of that.
=> More informations about this toot | More toots from leeloo@techhub.social
@leeloo If it fails or gets annoying I will submit a bug report to customer services about login issues and outline the whole process I used to view.
This will obviously not result in them fixing anything for me but it might get sent on to a dev and make them smile for a moment. 😂
=> More informations about this toot | More toots from ruario@vivaldi.net
@ruario
Or it may result in them making it harder for everyone else to try the same thing to avoid their marketing hell.
Danish newspapers collectively sued Google years ago for linking to individual articles, allowing people to avoid the marketing hell they call a front page.
=> More informations about this toot | More toots from leeloo@techhub.social
@leeloo Yeah I spent some time looking at all the cookies that are defined when you login with Vivaldi. What they are called and their values and dates. I was trying to work out what was the minium viable I should let through and then I realised:
So in the end I just copied them all over and let Lynx set and update any of them as it sees fit. However during this I was obviously paying some attention to the dates and stuff. 😉
=> More informations about this toot | More toots from ruario@vivaldi.net
@leeloo You have some with names like "_cmp_advertising" where it is fairly clear what they do. Like that one gets set when clicking though their cookie banner and agreeing or not to tracking by partners, having a value of 0 or 1.
It occurred to me that I should have that one to 0 to minimse other cookie requirements. But also even having it set at all (to 0 or 1) is likely a good idea because if if it is not set the site thinks I never gone through the cookie banner at all. Due to that they might eventually dump me out of the login session because they cannot decide what I have consented to.
And yes considerations like this does make this whole thing sound increasingly like a house of cards that will fall down around me… but on the other hand I do sort of think it might just work. 😜
=> More informations about this toot | More toots from ruario@vivaldi.net
@leeloo One nice thing I did discover just now when searching online for the cookie names that get stored is this page run by Schibsted (who own Aftenposten)
https://cookies.privacy.schibsted.com/reports/norway/aftenposten/cookies.html
What I can see from that list is that indeed the "id-jwt" cookie appears to be the main session/login cookie that allows access of content on Aftenposten. I can even confirm this by deleting all but that cookie . After doing so as a test I see that I can still access paid articles.
Some of the other cookies will then come back but at a bare minium I need this one. However, I will let a bunch of others remain … just to be sure.
=> More informations about this toot | More toots from ruario@vivaldi.net This content has been proxied by September (3851b).Proxy Information
text/gemini