From Newsgroup: comp.lang.vhdl

I wrote on
Sat, 22 Feb 2025 21:12:58 +0100
-
|----------------------------------------------------------------------|
|"Dear all, |
| |
|Today LinkedIn is showing a good post about SystemVerilog. LinkedIn is| |claiming that that post is 1 week old." | |----------------------------------------------------------------------|

Dear all,

I should had written that Frans Skarman started that LinkedIn
thread. Sorry!

|--------------------------------------------------------------------------| |""and differeneces in some details of execution are to be expected between| |different simulators""" | |--------------------------------------------------------------------------|

I confess that I introduced this misspelling "differeneces". Sorry again!

LinkedIn does not run a satisfactory search engine. So LinkedIn forced me
to scroll for too many minutes to find that thread by Frans Skarman.

"!

This page is having a problem

Try coming back to it later.


You could also:

* Open a new tab

* Refresh this page

Error code: Out of Memory

Refresh"
said Microsoft Edge after tens of minutes of scrolling when scrolling
through 4 months of LinkedIn reactions with Task Manager showing the top
four memory users being:
"msedge.exe [. . .] 462,168 K [. . .]
msedge.exe [. . .] 246,280 K [. . .]
msedge.exe [. . .] 66,248 K [. . .]
explorer.exe [. . .] 61,628 K [. . .]"
in a computer with 8 gigabytes while Resource Monitor said "39% Used
Physical Memory". Waiting minutes and clicking refresh lost what I
scrolled through by reverting to today's reactions.

(So I closed Microsoft Edge and rebooted Windows. Then I saw that
Microsoft Edge lost months of browsing history. Another reboot seemed to
get this browsing history back.)

"Why do people do this?!
Honestly, I don't really know. This is one of those mysteries that might
never get solved. Oh, there is one lead: it seems to be generated mostly (exclusively?) by Windows systems. Really, who would have thought?"
says
HTTPS://WWW.ueber.net/who/mjl/projects/bomstrip
by Mechiel Lukkien.

Search engines failed to find that LinkedIn thread. LinkedIn does not
forbid me from republishing to USENET what I say therein:
"Dear Doctor Saptarshi Sarkar, PhD: Read the news:comp.lang.vhdl and news:comp.arch.fpga USENET newsgroups and "VHDL Answers to Frequently
Asked Questions" be Ben Cohen - HTTPS://ACCU.org/bookreviews/2004/gloster_1292/
"
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.vhdl

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.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.lang.vhdl

(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

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 uploaded them to HTTP://Gloucester.Insomnia247.NL/Scholastica_or_LinkedIn_connivance/LinkedIn_comments_by_myself/

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. HTTP://Gloucester.Insomnia247.NL/Scholastica_or_LinkedIn_connivance/2025-12-30g_Thanks_to_Paul_Colin_Gloster_for_flagging_said_Barrister_Ben_Keith.pdf
--- Synchronet 3.21a-Linux NewsLink 1.2