Groups | Search | Server Info | Login | Register
Groups > comp.lang.vhdl > #5554
| From | Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> |
|---|---|
| Newsgroups | comp.lang.vhdl, comp.arch.fpga, comp.arch.embedded |
| Subject | Re: good post on LinkedIn |
| Date | 2026-01-01 18:52 +0100 |
| Organization | To protect and to server |
| Message-ID | <a466fba3-4f96-5968-faef-db94f1e721a5@insomnia247.nl> (permalink) |
| References | <2983bc07-a132-6dc9-aef3-523789a027c1@Strand_in_London.Gov.UK> <5e0a38da-0e01-3cfa-3eec-cf3b29a5bb41@insomnia247.nl> |
Cross-posted to 3 groups.
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.
Back to comp.lang.vhdl | Previous | Next — Previous in thread | Next in thread | Find similar
good post on LinkedIn Niocláisín Cóilín de Ghlostéir <Master_Fontaine_is_dishonest@Strand_in_London.Gov.UK> - 2025-02-22 21:12 +0100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <Spamassassin@irrt.De> - 2025-08-29 16:16 +0200
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-01 18:52 +0100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-02 01:40 +0000
csiph-web