Groups | Search | Server Info | Login | Register
Groups > sci.electronics.design > #739841
| From | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> |
|---|---|
| Newsgroups | comp.arch.embedded, sci.electronics.design |
| Subject | Re: good post on LinkedIn |
| Date | 2026-01-29 14:26 +0000 |
| Organization | To protect and to server |
| Message-ID | <10lfqlq$3ji9g$1@paganini.bofh.team> (permalink) |
| References | <2983bc07-a132-6dc9-aef3-523789a027c1@Strand_in_London.Gov.UK> <5e0a38da-0e01-3cfa-3eec-cf3b29a5bb41@insomnia247.nl> <a466fba3-4f96-5968-faef-db94f1e721a5@insomnia247.nl> <10j77ll$12g8$1@paganini.bofh.team> |
Cross-posted to 2 groups.
I myself wrote on Fri, 02 Jan 2026 02:40:07 - |-----------------------------------------------------------------------------| |"I myself wrote: | ||---------------------------------------------------------------------------|| ||"Happy New Year! || || || ||This post is about more misadventures of LinkedIn ineptness. I || ||(incompletely) archived LinkedIn comments by me from October 2025 downto a || ||time which LinkedIn professes to be 2 years (ago). This unsatisfactorily || ||incomplete archiving took excessively long: i.e. 5 days! Namely December || ||6th; 7th; 8th; 9th; and 10th, 2025. || || || ||This incomplete archive consists of circa 470 comments in circa 387 || ||kilobytes. By contrast, it took me fewer than one day in November 2025 to || ||download 77 megabytes (34,889 posts) from news:alt.video.dvd.authoring || || || ||Many LinkedIn problems of || ||"! || || || ||This page is having a problem || || || ||Try coming back to it later. || || || || || ||You could also: || || || ||* Open a new tab || || || ||* Refresh this page" || ||happened during this December misadventure. || || || ||LinkedIn is so lame! || || || ||On New Year's Day 2026, LinkedIn repeatedly refused to show me comments by || ||me from more than 4 weeks previously." || ||---------------------------------------------------------------------------|| | | |LinkedIn made me lose circa 566 megabytes and many tens of minutes to | |download circa the last 4 weeks of LinkedIn comments by myself | |(excluding comments in this timeframe which LinkedIn stopped showing | |to me), and almost 2 hours to upload these downloaded backups. These | |four weeks of comments are not many comments but LinkedIn forces an | |author to lose excessive amounts of megabytes and time to save such | |personal data, or to lose such personal data. LinkedIn is | |unsatisfactory. | | | |[. . .] | | | |I also noticed on 01/01/2026 that LinkedIn restricted Microsoft Edge's | |feature of Print --> Printer --> Save as PDF to print to a single | |piece of paper (i.e. a tiny excerpt of weeks of comments) but LinkedIn | |used to let Microsoft Edge make big PDF files even as recently as | |Tuesday 30th December 2025. E.g. | |[. . .]" | |-----------------------------------------------------------------------------| Since 23/01/2026 I notice 2 new LinkedIn bugs which are not the same as the LinkedIn bugs which I detect over many years. So I thought such a bug might be temporary and might prevent LinkedIn from refusing to scroll through more than a month of comments, so this morning I managed to scroll down through circa 3 months of comments. LinkedIn is legally obligated to provide copies of comments, but LinkedIn acts illegally. If you want to back up comments which you uploaded to LinkedIn, then now might be the time to back them up. LinkedIn forced me to spend tens of minutes to scroll through circa 3 months of comments. I used Microsoft Edge to "Save as type: Webpage, complete", producing an 86-megabytes copy. I used Microsoft Egde to produce an unsatisfactory 249-page, 238-megabytes PDF copy (Print --> Printer --> Save as PDF). Sic. 238 megabytes versus 86 megabytes for only the same comments. Uploading this PDF version to Insomnia 24/7 took circa twenty minutes. Microsoft Edge took circa 12 minutes to produce this PDF file. Much worse problems related to Microsoft are alleged by e.g. HTTPS://wiki.ICEList.Is/index.php/LinkedIn and HTTPS://wiki.ICEList.Is/index.php/Microsoft (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
Back to sci.electronics.design | Previous | Next — Next in thread | Find similar
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-29 14:26 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 09:04 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-29 17:57 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 10:59 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 00:48 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 17:01 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 01:28 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 15:14 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 11:52 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:05 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 12:34 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:29 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 20:59 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 03:06 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-02 00:17 +1100
Re: Excel and accountants, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-01-31 23:21 +0000
Re: Excel and accountants, good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 16:22 -0800
Re: Excel and accountants, good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-02-01 02:13 +0000
Re: Excel and accountants, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 19:31 -0700
Re: Excel and accountants, good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 21:58 +0100
Re: Excel and accountants, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-02-01 14:36 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 03:56 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 15:23 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 14:36 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:31 +1100
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 14:59 +1100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 10:15 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 00:06 +1100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 13:43 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 02:18 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 08:04 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 03:51 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 09:46 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 20:00 +0000
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-30 22:49 +0100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 22:52 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:02 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 13:33 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 01:31 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 19:16 +0000
Re: history of Fortran, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-01-31 23:10 +0000
Sorry re history of Fortran, good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 23:25 +0000
Re: Sorry re history of Fortran, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-02-01 02:43 +0000
Re: Sorry re history of Fortran, good post on LinkedIn OrangeFish <OrangeFish@invalid.invalid> - 2026-02-01 18:00 -0500
Re: history of Fortran, good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 22:11 +0100
Re: history of Fortran, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-02-01 14:42 -0700
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:36 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 15:53 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:14 +1100
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-31 11:21 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:34 -0800
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-31 21:42 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 13:36 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:57 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 03:10 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-02 00:37 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 07:36 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-03 16:27 +1100
Re: good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 22:21 +0100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-31 09:00 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 15:45 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 14:26 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 13:53 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:25 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:41 -0800
Re: good post on LinkedIn Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-31 17:33 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 10:07 -0800
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 11:26 -0700
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 22:04 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 07:38 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-03 16:37 +1100
Re: good post on LinkedIn Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-30 15:06 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 11:55 -0800
Re: good post on LinkedIn wmartin <wwm@wwmartin.net> - 2026-01-30 11:27 -0800
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 18:54 -0800
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 23:26 -0700
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-31 09:22 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 02:50 -0700
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 04:36 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 09:24 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 09:56 -0700
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 10:05 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 14:22 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 19:09 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 22:16 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 22:27 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 03:40 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 22:46 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 15:20 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 08:44 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 17:13 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:55 -0800
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 08:15 -0800
csiph-web