gemini://gemini.techrights.org/irc-gmi/irc-log-050722.gmi

00:17 *psydroid2 has quit (Ping timeout: 2m30s)

00:26 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell

00:27 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell

00:58 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell

00:58 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell

01:02 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell

01:03 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell

03:19 *Despatche has quit (Quit: Read error: Connection reset by deer)

04:42 *Despatche (~desp@u3xy9z2ifjzci.irc) has joined #boycottnovell

05:50 Techrights-sec; Mention of the Unified Patent Court needs to be identified as such

05:50 Techrights-sec; so the acronym gets expanded. HTML has the <acronym title=""> element

05:50 Techrights-sec; or it can be spelled out the first time in each article so that it works

05:50 Techrights-sec; in Gemini as well

07:03 *DaemonFC has quit (Quit: Leaving)

09:18 schestowitz-TR; no DB issue since midday yesterday

09:35 Techrights-sec; what is the scope of the data in chart? Is it for one country or global?

09:46 schestowitz-TR; I fainted a little earlier

09:46 schestowitz-TR; seems node_revisions are used in blog posts

09:46 schestowitz-TR; I'm trying to assess how much was lost there

09:46 schestowitz-TR; and how much can be retrieved, e..g. from Google Cahce

09:47 schestowitz-TR; so far I found only many of my own blog posts missing

09:47 schestowitz-TR; data loss is kind of a big deal

09:47 schestowitz-TR; but... now I'm thinking

09:47 schestowitz-TR; no blog post in weeks

09:47 schestowitz-TR; so I wonder if I can take that table from an old DB dump

09:47 schestowitz-TR; then transplant it into the current and see if that goes

09:47 schestowitz-TR; I still want to see what else was lost

09:47 schestowitz-TR; I don't have many DB tools, but I reckon I could freeze writing to the site, take a DB dump

09:47 schestowitz-TR; then tke an old one, compare to it, and fill the gaps

09:52 schestowitz-TR; worse come to worse, I can roll back to 25thish, and that would mean giving up on the node after that, which are mostly links tol external sites anyay

09:52 schestowitz-TR; I want to study better what code_revision does, will check from sql> prompt soon

10:01 *psydroid2 (~psydroid@memzbmehf99re.irc) has joined #boycottnovell

10:02 Techrights-sec; drupal is over my head

10:02 Techrights-sec; what is the underlying cause of the corruptingtables?

10:03 schestowitz-TR; upside is, no alerts in almost 24 hours

10:03 schestowitz-TR; so it 'settled' better

10:03 schestowitz-TR; at the moment I try to assess how many node went missing

10:03 schestowitz-TR; and maybe I can readd them by hand

10:03 schestowitz-TR; with a new address (node)

10:03 schestowitz-TR; so far (noting to self./.. and yuou) I can onyl see about 10 blog posts missing, all mine

10:03 schestowitz-TR; I can retreive them in full from google chche

10:03 schestowitz-TR; that woluld be the faster "fix"

10:03 schestowitz-TR; albeit not before assuring myself the DB is ina stable, good state

10:03 schestowitz-TR; I remmebered that revisions are used SOMEWHERE

10:03 schestowitz-TR; seems it was blogs

10:03 schestowitz-TR; I can see 23 missing content blogs from me

10:30 schestowitz-TR; going back to 2010 I see some more missing blog posts

10:30 schestowitz-TR; so restoring mnaually, assuming qw value most the blogs/originals, is not the bext approach

10:30 schestowitz-TR; some of these might even be distro reviews

10:30 schestowitz-TR; I'll check now how that table works and whether it is feasible to graft or merge tables

10:30 schestowitz-TR; maybe nodes is just more of a virtual likst and revisions is what's important

10:39 schestowitz-TR; a) months ago (maybe 2) we had a simialr issue

10:39 schestowitz-TR; b) last working state was over a week ago, restoring new stuff by hand is a huge task

10:39 schestowitz-TR; c) not sure if the disk surface is the issue, mentioned again to kaniini

10:39 schestowitz-TR; d) this is the only DB stored on the VM, the others are remote

10:39 schestowitz-TR; e) if we were to revert back to old backup, amybe worth CMS work too

10:39 schestowitz-TR; f) from what I read "upgrading" drupal is no fun

10:39 schestowitz-TR; g) staying forever with this old DB and drupal is not good either

10:39 schestowitz-TR; h) with drupal, one approach is, clean install, new version

10:39 schestowitz-TR; then import old nodes

10:39 schestowitz-TR; not sure if users can also be imported, comments etc.

10:39 schestowitz-TR; those things are complex

10:39 Techrights-sec; It's almost too earlyy to speculate about such things since even the OS

10:39 Techrights-sec; upgrade is not set yet

11:04 *psydroid2 has quit (connection closed)

11:05 *psydroid2 (~psydroid@memzbmehf99re.irc) has joined #boycottnovell

11:08 *psydroid2 has quit (connection closed)

11:08 *psydroid2 (~psydroid@memzbmehf99re.irc) has joined #boycottnovell

12:25 schestowitz-TR; I did a lot of thinking while you were offline. One option (mentioned in passsing in main IRC channel is)

12:26 schestowitz-TR; make the existing site "legacy", lock it down, read only, no ssh access etc. in case DB breaks, we can restore from backup as it no longer changes anyway. There are many pros, some cons

12:27 schestowitz-TR; rss feeds can all be redirected via apache, tuxmachines-old is a legacy locked-down machine

12:28 schestowitz-TR; when, using a subdomain we make something like new.tuxmachines.org, build a new site there and maybe create accounts for the contributors in tuxmachines (old) in the new one

12:28 schestowitz-TR; of note: I think our last major DB disaster was April 12th, I see that before rerstarting from backup then too node_revisions table was impacted

12:29 schestowitz-TR; to start off the new site I can manually migrate all nodes from the past week, such that when we revert back to a backup nothing is lost per se

12:44 Techrights-sec; ack #######################################

12:44 Techrights-sec; maybe scan the whole thing with wget and make static pages that way and then

12:44 Techrights-sec; just archive the database and such offline?

12:44 Techrights-sec; so then static pages would remain (and could be the target of some

12:44 Techrights-sec; redirection rules in the Apache configutaiton file) and the moving parts would

12:44 Techrights-sec; get turned off and set aside

12:47 schestowitz-TR; that would be a groklaw-type 'archive'

12:47 schestowitz-TR; with a lot of missing stuff

12:47 schestowitz-TR; also, that's hundreds of thousands of files

12:47 schestowitz-TR; which are connected in several ways, e.g. to images in another CMS

12:47 Techrights-sec; no, with the right settings wget can get everything there

12:47 Techrights-sec; the crawling process would take a lot of time

12:47 schestowitz-TR; I was thinking, we can redirect many bits to the "new" site

12:47 schestowitz-TR; and in due course the old site will be accessed a lot less

12:47 schestowitz-TR; than it can be archived

12:47 schestowitz-TR; in due course

12:58 schestowitz-TR; tidying up my mind a bit, let me break it down like this

12:58 schestowitz-TR; a) longterm plan = static for old site

12:58 schestowitz-TR; b) migrate users to new site and cms (to be determined)

12:58 schestowitz-TR; c) restoring DB and carrying on as usual not an option, it keeps us entrapped with a rotting stack (just a quick, short-teyrm 'fix')

12:58 schestowitz-TR; d) new cms can have other contribs added (not many of them, we can do this manually)

12:58 schestowitz-TR; e) any time old site breaks just restore from backup, it's not changing anyhow

12:58 schestowitz-TR; f) in light of "news deserts" we can readjust with another CMS, like Techrights did with frequent batches and TOC at the top

12:59 schestowitz-TR; g) a properly chosen CMS can buy us another decade, in due course stories from 2005ish aren't accessed much, can be made static

12:59 schestowitz-TR; or gradually copied over to the "new" CMS, URL scheme should not be too hard to write rules for

12:59 schestowitz-TR; h) I contacted kaniini, said you'd be happy to chip in for billable time

12:59 schestowitz-TR; I don't know what OS or CMS to use, depends on the so-called 'use case' of the site (multi-user, many updates, news stories)

13:03 schestowitz-TR; any updates, news stories)

13:03 schestowitz-TR; i) (letters easier for referencing) the old site does not need regular backups or open ssh port, it can be accessed when needed via

13:03 schestowitz-TR; HV; if it has technical issues we can revert back to working stats quickly, later we can figure out content migration or making

13:03 schestowitz-TR; it all static, this machine is already calles tuxmachines-old, it is presumed "legacy", we just just never goit around

13:03 schestowitz-TR; to making tuxmachines-new or tuxmachines (don't think about migrating drupal 6 to another drupal... based on my research...

13:03 schestowitz-TR; it's fools's errand)

13:09 schestowitz-TR; j) I lean towards avoidance of "modern" CMS for several reasons inc. complexity

13:09 schestowitz-TR; we don't need commenting so much, we don't want wiki, multi user a nice to have

13:09 schestowitz-TR; I'll discuss with rianne to understand potential for other workflows

13:09 schestowitz-TR; a contrib in tuxmachines has just added a VSCode story ... the sort of stuff I don't like... as there's no editorial review

13:09 schestowitz-TR; and that can put people off

13:12 schestowitz-TR; I am going to brainstorm, while also loooking at existing CMSs

13:12 schestowitz-TR; publishing html manually, by hand, would not work well

13:12 schestowitz-TR; maybe the "new" tuxmachines can also have gemini presence? can't harm, can it?

13:13 Techrights-sec; it would be a nice plus for the new CMS to support Gemini out of the box

13:13 Techrights-sec; but not essential

13:13 schestowitz-TR; the content in the gemini page, however, would be just quotes and then WWW link

13:14 Techrights-sec; as at worst Gemini can be retrofitted via a scraper :/

13:14 Techrights-sec; there's not much there for Gemini on TM though

13:14 Techrights-sec; and as you point out the links are to the WWW (http / https)

13:14 Techrights-sec; so it would be only the quotes which might be of value there

13:23 schestowitz-TR; given "news desserts"

13:23 schestowitz-TR; hehe, deserts

13:23 schestowitz-TR; maybe editorial style too can change, esp. as new links about the same theme/stories arrive

13:23 schestowitz-TR; so far we've used comments in drupal to make "updates"

13:23 schestowitz-TR; but the comments were not made for this purpose

13:23 schestowitz-TR; so we are clearly using the wrong approach

13:23 schestowitz-TR; wait, here's a radical idea

13:23 schestowitz-TR; since most stories are just some quote and a link

13:23 schestowitz-TR; we could run the site as gemini, maybe even self-hosted

13:23 schestowitz-TR; then, service it over your nginx gateway

13:23 schestowitz-TR; with some decorative stuff like rss feeds on top

13:23 schestowitz-TR; for multimedia files it can reach out to the "old" site, to lower bandwidth

13:23 schestowitz-TR; links.tuxmachines.org

13:23 schestowitz-TR; news.tuxmachines.org

13:23 schestowitz-TR; over gemini and https

13:23 schestowitz-TR; this way we also add https support

13:23 schestowitz-TR; the "syntax" is then just gemtext, the storage is plain text files

13:23 schestowitz-TR; the theme is your perl program

13:23 schestowitz-TR; grabing a file here and there, via css styling

13:24 schestowitz-TR; agate or simialr can be set up on a new vm running alpine

13:24 Techrights-sec; there's the bottleneck :(

14:14 schestowitz-TR; just had a long chat with rianne

14:14 schestowitz-TR; we can replicate the looks of tuxmachines but without drupal as CMS

14:14 schestowitz-TR; for rss feeds some kind of CMS would still be highly essential

14:14 schestowitz-TR; watgching hugo videos

14:14 schestowitz-TR; ok, so hugo has config file

14:14 schestowitz-TR; it hosts images and pages locally

14:14 schestowitz-TR; some of the themes are nice

14:14 schestowitz-TR; it uses markup

14:14 schestowitz-TR; editing would be changing the files or adding files, e.g. over ssh/fish://

14:14 schestowitz-TR; lots of shithub there

14:14 schestowitz-TR; adding about 50 files per day and then finding which one to edit to add updates to it would be hard

14:15 schestowitz-TR; hugo seems OK for small sites that do not change much

14:15 Techrights-sec; yes it basically manages a database (if I understand correctly) which

14:15 Techrights-sec; exports a mirror site from it

14:15 Techrights-sec; how large could Hugo scale out to? Is there a better static site generator

14:15 Techrights-sec; for sites with a great many posts?

14:19 schestowitz-TR; rianne thinks the gemini proxy of TR is too geeky

14:19 schestowitz-TR; like "not attractive", zero images

14:19 schestowitz-TR; I need something where I can easily add domain/node/mynumberofchoice

14:19 schestowitz-TR; starting with numbers that correspond to the old site as in the future we can merge them

14:19 schestowitz-TR; then, it needs to make rss feed for the latest additions

14:19 Techrights-sec; there should be no images but CSS improvements are a good idea

14:25 schestowitz-TR; tuxmachines is registered until at least 2027

14:25 schestowitz-TR; so whatever s/w we use, we'll be stuck with and spend a lot of time on for many years

14:25 schestowitz-TR; so I want to spend more time

14:25 schestowitz-TR; we could "roll out our own", but then any theme changes or sidebars or rss feeds would be hard

14:25 schestowitz-TR; it's like going back to the 'CMS' mindset of late 1990s

14:25 schestowitz-TR; has lots of shithub also

14:25 schestowitz-TR; ewww....ruby

14:25 schestowitz-TR; shithub modules

14:25 schestowitz-TR; closing window... not interested

14:28 Techrights-sec; I think one of the things to look for is whether it can be used collaboratively

14:28 Techrights-sec; by several editors or authors and doesn't just reside on some one person's own

14:29 schestowitz-TR; yes, then deployed or similar

14:29 schestowitz-TR; BTW, the same can be used later for Techrights

14:29 schestowitz-TR; but that's another story

14:29 schestowitz-TR; those things I saw (videos) are a step back

14:29 schestowitz-TR; they don't improve editing speed

14:29 schestowitz-TR; they improve performance (static)

14:29 schestowitz-TR; I also don't know what state they will be in within 10 years

14:29 schestowitz-TR; many 'static' site s/w perished

14:29 schestowitz-TR; as people flocked to CMS

14:29 schestowitz-TR; maybe I will do a video+article about all this at the end

14:32 schestowitz-TR; it's a shame that wordpress or drupal are out of the question already

14:32 schestowitz-TR; not just db back end but js front end and editors

14:32 schestowitz-TR; also, they move too fast, hence hard to maintain

14:32 schestowitz-TR; b2 (what wordpress is forked off) is obv. not an option either

14:32 schestowitz-TR; wordpress 1.0 and 1.2 were small and simple

14:32 schestowitz-TR; back then I'd upload images over sftp

14:32 schestowitz-TR; if we have another 166,000 nodes coming, starting with bloat that has a new release every month would be misguided

14:32 schestowitz-TR; "going witrh the flow..."

14:38 schestowitz-TR; there is no "CentOS" of wordpress or drupal, but they have some LTS versions to go into repos like Debian

14:38 schestowitz-TR; but moving between versions can be challenging and drupal is bloat

14:38 schestowitz-TR; inc. a burden on the user, like lots of stuff really should not be there

14:38 schestowitz-TR; iirc, phoronix coded its own

14:38 schestowitz-TR; or reused something

14:38 schestowitz-TR; I chatted with him before about replacing "id/number" in the URLs into something

14:38 schestowitz-TR; about the story, which he later implemented, poorly...

14:38 schestowitz-TR; mambo, joomla and that old family is a dead only like zope

14:38 schestowitz-TR; I reckon support for these is already terrible, hence itwire being so badly broken

14:50 Techrights-sec; the rewrite engine in Apache can do pattern matching so the URL scheme is

14:50 Techrights-sec; less important than one might think

14:50 Techrights-sec; A unique difference between old and new, even a tiny one, is sufficient

14:50 schestowitz-TR; they are microsoft nomada dn the site is sometimes broken

14:50 schestowitz-TR; they seem to have drowned in a mess

14:50 schestowitz-TR; the TM move, first in 18+ years, can hopefully tidy things up for us

14:50 schestowitz-TR; I'm thinking of the URL scheme at the moment

14:50 schestowitz-TR; to make continuity and avoid URL ambiguity for which we fused old and new together

14:50 schestowitz-TR; you cannot just say, let's go with wordpress but an old version

14:50 schestowitz-TR; it's the systemd scenario

14:50 schestowitz-TR; take it or least it (latst is saddles with with the vendor imposes)

14:50 schestowitz-TR; terrible UI for 'lamers'

14:54 Techrights-sec; /node/ is unnecessary as well as too long a single character or nothing

14:54 Techrights-sec; would be adequate

14:54 Techrights-sec; /n/[number]

14:54 Techrights-sec; as for SEO, that's always changing

14:55 schestowitz-TR; would you go with /node/[number]

14:55 schestowitz-TR; or change to something more 'SEO'-friendly like portion of title?

14:55 schestowitz-TR; the former would keep it shorter and more consistent with past years

14:55 schestowitz-TR; anything other than cms would make rss feed generation very difficult

14:55 schestowitz-TR; sadly, all the major ones bring with them bloat we do not want,

14:55 schestowitz-TR; and future versions more so

14:56 Techrights-sec; the rewrite engine in Apache can do pattern matching so the URL scheme is

14:56 Techrights-sec; less important than one might think

14:56 Techrights-sec; A unique difference between old and new, even a tiny one, is sufficient

14:56 Techrights-sec; /node/ is unnecessary as well as too long a single character or nothing

14:56 Techrights-sec; would be adequate

14:56 Techrights-sec; /n/[number]

14:56 Techrights-sec; as for SEO, that's always changing

15:01 Techrights-sec; sadly a CMS is almost necessary for RSS

15:01 Techrights-sec; static HTML could work but then templates would have to be used and

15:01 Techrights-sec; embedded metadata in the head element; a shell script or maybe at worst a short

15:01 Techrights-sec; perl script could do all that

15:06 schestowitz-TR; choosing a cms is scary if you intend to rely on it longer than the project might exist

15:06 schestowitz-TR; I still have two php-nuke sites

15:06 schestowitz-TR; checking ghost

15:07 Techrights-sec; yes, they can dry up and blow away or the developers can go weird like with WP

15:08 schestowitz-TR; already thinking how to techniacally prevent 404 when we make the switch

15:08 schestowitz-TR; for new nodes since recovered DB data it shoule be easy

15:08 schestowitz-TR; site/node/x -> newsie/node/x

15:08 schestowitz-TR; and I'll make statis copies of those pages, then copy across

15:08 schestowitz-TR; so no need to hurry

15:08 Techrights-sec; too early to worry about that; the new CMS must be decided first

15:10 schestowitz-TR; right, I've already set aside a working (I chedked) copy of 27062022 dump, which will then be the "factory reset" going forward

15:10 schestowitz-TR; when locking things down I'll also prevent editors adding new stuff

15:10 Techrights-sec; 2022-06-22 ?

15:10 Techrights-sec; 2022-06-27

15:17 schestowitz-TR; any backup after 28th I do not trust

15:17 schestowitz-TR; as there was an incident with node_revisions notes as producing some errors

15:17 schestowitz-TR; let's say that techrights was to follow with the same CMS, given that it needs RSS,

15:17 schestowitz-TR; so we need to assess the needs and then it's fewer CMS skills to deal with

15:17 schestowitz-TR; drupal and wordpress became "webapps"

15:17 schestowitz-TR; I think there are also phone "apps"

15:17 schestowitz-TR; you don't get to opt out of the "apps" part

15:20 *u-amarsh04 has quit (Quit: Konversation terminated!)

15:25 Techrights-sec; phone "apps" are undesirable

15:25 schestowitz-TR; just spoke to rianne

15:25 schestowitz-TR; she knoews drupal latest form work

15:25 schestowitz-TR; we support it

15:25 schestowitz-TR; and she knows how messy it can get with sec patches and conflicts

15:25 schestowitz-TR; it's also far more than needed for a news syndicator

15:27 *u-amarsh04 (~amarsh04@freenode-rmogvn.g0d7.dtdf.mc4289.IP) has joined #boycottnovell

15:27 *u-amarsh04 (~amarsh04@5tcc2vuaj9aks.irc) has joined #boycottnovell

15:37 schestowitz-TR; for the time being TM runs OK, but with missing old nodes, old OS etc.

15:37 schestowitz-TR; this is a good time to leave it behind

15:37 schestowitz-TR; the readers come via rss mostly

15:37 schestowitz-TR; so they would follow

15:37 schestowitz-TR; though I wonder, if you redirect from site/rss to othersite/rss would all news readers cope?

15:37 schestowitz-TR; afaik, apache manages this transparently enough

15:37 schestowitz-TR; the issue then might be, people have two different URLs for rss

15:37 schestowitz-TR; one of which a redirection

15:37 schestowitz-TR; and different domains

15:37 schestowitz-TR; but I reckon redirecting 'backwards' can always compensate for it

15:37 schestowitz-TR; as we control both ends

15:37 Techrights-sec; I'm not sure how RSS readers would handle redirection but if they are fully

15:37 Techrights-sec; HTTP compliant they will

15:44 schestowitz-TR; worst case scenario, as fall back every 5 mins we override what the "old" server returns by getting it from "new"

15:45 schestowitz-TR; or we do the delivery transparently from ool using apache, withour a redirection

16:00 schestowitz-TR; spoke to rianne again (out finding food)

16:00 schestowitz-TR; and we are generally hostile towarss drupal

16:00 schestowitz-TR; it's like missing a good change to escape bad rubbish

16:00 schestowitz-TR; and an overkill for what tuxmachines does

16:00 schestowitz-TR; and how often it does it

16:00 schestowitz-TR; I will carry on looking

16:01 Techrights-sec; I think the main thing to worry about is having the CMS be capable of having

16:01 Techrights-sec; several editors/authors working on the site.

16:03 schestowitz-TR; you can see some of the "oppular" ones, like "hacker" noise, are crude and ugly

16:03 schestowitz-TR; and have rss feed/s

16:03 schestowitz-TR; rianne says she liked the current looks of TM

16:03 schestowitz-TR; but it is built on very old "tech"

16:04 Techrights-sec; The current look is ok but I agree with her about the underlying technology

16:04 Techrights-sec; being a problem

16:07 schestowitz-TR; a lot of "solutions" are JS like vue.js or react

16:07 schestowitz-TR; (no, heck no!)

16:07 schestowitz-TR; redis, frameworks... think diaspora.. RoR

16:07 Techrights-sec; I'm not a fan of RoR or Ruby in general but have nothing major against it

16:10 schestowitz-TR; I am also thinking of how to 'innovate' beyond what we currenly have

16:10 schestowitz-TR; the main defficiency was a way to add updates to existing stories

16:10 schestowitz-TR; like additional related links

16:10 schestowitz-TR; what would be nice: them showing up as followups in rss feeds too, but marked accordingly

16:10 schestowitz-TR; LinuxReviews was using a wiki

16:10 schestowitz-TR; but became inactive, maybe cause the guy from sweden got a new job

16:25 schestowitz-TR; i still search and brainstorm

16:25 schestowitz-TR; but I cannot find anything better than what we have already

16:25 schestowitz-TR; it's like someone being forced to get something "news"

16:25 schestowitz-TR; despite knowing it's worse than the old thing

16:25 schestowitz-TR; this also depends on kaniini allocating another VM and IP

16:25 schestowitz-TR; though if it is light, I could get cheap hosting somewhere

16:25 *DaemonFC (~daemonfc@63wuxds8r77qk.irc) has joined #boycottnovell

16:26 Techrights-sec; static sites are light and could run from their own RPi even

16:26 Techrights-sec; the question would be on which machine the static site generator should

16:26 Techrights-sec; be accessible on

16:27 schestowitz-TR; for a very busy site hosting over copper with risk of outages is not the best

16:27 schestowitz-TR; susan used to host the site from home

16:27 schestowitz-TR; but it was smaller

16:31 Techrights-sec; a low-cost VPS would be best then; even with the same donor as now, going to

16:31 Techrights-sec; a static site generator would free up a lot of hardware

16:39 schestowitz-TR; I am learning in favour of static still

16:39 schestowitz-TR; but trying to see what to do for rss feeds

16:39 schestowitz-TR; even if it's just one main feed

16:39 Techrights-sec; the RSS feed generator could be part of the static site generators

16:52 schestowitz-TR; hugo supports rss, but managing it is no fun from what I can see

16:52 schestowitz-TR; I also don't trust github project

16:52 schestowitz-TR; they might not outlive their master

16:52 schestowitz-TR; I am not impressed by it, it's by hackers for hackers, and moreover cargo cult lovers who beg

16:52 schestowitz-TR; for stars from MICROSOFT shithub

16:52 schestowitz-TR; I don't think it has any "mass appeal" and if hackers find somethig better, it'll

16:52 schestowitz-TR; fall by the wayside

16:52 schestowitz-TR; like many others before it

16:52 schestowitz-TR; while I wrote about it before in Daily Links and TM I never looked very closely until today

16:52 schestowitz-TR; this can become the subject of future videos about CMS, bloat, shithub...

16:54 schestowitz-TR; with static cms you might think it's KISS, but they rely on you grabbing frameworks

16:54 schestowitz-TR; and who knows what Microsoft will do to these networks in the next 10 years

16:54 schestowitz-TR; remember nuke.NET

16:54 schestowitz-TR; or whatever that was called?

16:54 schestowitz-TR; .NET clone for php-nuke..

16:54 Techrights-sec; definitely; they could damage those quite suddenly in many ways and for many

16:56 schestowitz-TR; "crates" also (Rust)

16:56 schestowitz-TR; think npm, cran, cpan, and all those js things like node

16:56 schestowitz-TR; you rely on some "modules" or frameworks (pile of bloat) being there for you

16:56 schestowitz-TR; otherwise your code goes nowhere

16:56 schestowitz-TR; and if the OS does not support or will not suppor these, then one?

16:56 schestowitz-TR; new vm? new container?

16:59 schestowitz-TR; for some basic hello world programs you now need hundreds of MBs of frameworks

16:59 schestowitz-TR; with dubious sources

16:59 Techrights-sec; I have only very low opinions about "frameworks"; They are mostly busywork and

16:59 Techrights-sec; and end in themselves rather than a means to solve a larger task

17:04 schestowitz-TR; let me ask a "big question"

17:04 schestowitz-TR; should we maybe also consider the editorial style of tuxmachines?

17:04 schestowitz-TR; to present stories not just as second-hand linker

17:04 schestowitz-TR; but offer a sort of overview followed by links?

17:04 schestowitz-TR; os news is a bit like that

17:04 schestowitz-TR; os news moved to wordpress some years ago

17:04 schestowitz-TR; doctorow writing style in medium and that long page I really dislike, it's not pleasant to follow

17:05 Techrights-sec; I would defer to Rianne about that

17:05 Techrights-sec; TM has been fastest to aggregate most news stories

17:05 Techrights-sec; long format is fine and Doctorow is really good at it; though Medium is

17:05 Techrights-sec; an awful technology

17:06 schestowitz-TR; speed would hardly be impacted by editorial comments here and there

17:06 Techrights-sec; It takes a lot of time to write them in a useful and informative manner.

17:06 Techrights-sec; At least it does for me.

17:07 schestowitz-TR; true, and harder for rianne

17:08 Techrights-sec; I'd say the time to consider such changes would be after the technical changes

17:08 Techrights-sec; are settled in and have been in place for a while but again it should be

17:08 Techrights-sec; defered to Rianne since she has the most experience there

17:08 Techrights-sec; and has done all the work

17:08 Techrights-sec; TM has really flourished under her tenure and with your help

17:09 schestowitz-TR; I am just trying to justify going for bloated CMS

17:10 Techrights-sec; Even /I/ have sometimes found news items there before anywhere else

17:13 schestowitz-TR; I was just thinking that with wordpress we'd have some support from your gemini converters

17:13 schestowitz-TR; as the format is simple

17:13 schestowitz-TR; but as noted earlier, it's quote and them http/s link

17:13 schestowitz-TR; so maybe low appeal for geminauts

17:23 schestowitz-TR; 1) has to remind myself we do not get away from outdated CMS but bad DB and very old OS,

17:23 schestowitz-TR; so this is highly justified and well overdue

17:23 schestowitz-TR; 2) took a quick break, thought drupal was cms anyway, WP more for bloging, more simila

17:23 schestowitz-TR; to what TM is about, will just check a quick demo of the new WP 6.0

17:39 schestowitz-TR; good news, see latest scrollback

17:53 *DaemonFC has quit (Quit: Leaving)

18:12 schestowitz-TR; just logged into my wordpress.com account

18:12 schestowitz-TR; sod it, it's still terrible workflow

18:12 schestowitz-TR; spoonfeeding, unless I can find fallbacks...

18:12 schestowitz-TR; looking...

18:12 schestowitz-TR; ok, the code editor mode is not bad

18:12 schestowitz-TR; and would enable fast workflow too

18:12 schestowitz-TR; but it's DB-based

18:12 schestowitz-TR; hence, complexity

18:51 schestowitz-TR; rianne found lots of food

18:51 schestowitz-TR; toothpaste (colgate, simplest, 100gr) up from 67p or 69' to 89p

18:51 schestowitz-TR; we still have cakes and chemical cider for next tuesday

19:18 *techrights_guest|88 (~b9fda1ba@54n9xgft8g6u2.irc) has joined #boycottnovell

19:19 schestowitz-TR; I will probably write about the CMS situation in general only after migrating

19:19 schestowitz-TR; I'm still not sure what to use to manage

19:19 schestowitz-TR; but I just got epo leaks

19:19 schestowitz-TR; and focusing on this for now

19:19 schestowitz-TR; very happy we got reassuring words re new machine

19:19 schestowitz-TR; rianne and I poured out 10000s worth of work into it

19:19 schestowitz-TR; I did a lot of work on the theme/appearance in 2014

19:21 schestowitz-TR; https://nitter.it/BrideOfLinux/status/1544355425839190016#m

19:21 -TechrightsBN/#boycottnovell-Christine Hall (@BrideOfLinux): "Interesting: Global Dynamics of the Demise of Microsoft Windows (Now Down to 27%) https://buff.ly/3NKfEeB"|nitter.it

19:24 schestowitz; Flash report: Demonstration of Wednesday 29 June 2022 "The re-election package

19:24 schestowitz; On Wednesday 29 June, 180 colleagues demonstrated in front of the Isar building shortly after the start of the 171th session of the Administrative Council. The occupancy of EPO buildings is low. On average, the caterer serves 400 meals per day in the Pschorrhfe buildings and 100 in the Isar building.

19:24 schestowitz; On the agenda of the Council was the Mobility Package introducing seconded national experts posts for the delegations (national salary paid by the EPO + an allowance of +5.000 per month). The reform was conveniently tabled at a time the re-election of Mr Campinos was on the agenda and successfully guaranteed his re-election until 1 July 2028.

19:24 schestowitz; SUEPO hopes that the Council mandated Mr Campinos to faithfully conduct social dialogue from now on. Given the track record of Mr Campinos in terms of cuts on career and purchasing power, EPO staff should be concerned by his re-election.

19:24 schestowitz; A copy of the intervention made during the demonstration is annexed to this paper for those who could not attend the demonstration.

19:24 schestowitz; We need you to support us so that we can support you.

19:24 schestowitz; Read more here.

19:31 *techrights_guest|88 has quit (Quit: Connection closed)

19:41 Techrights-sec; what was the scope of that 27%? The whole world?

19:41 Techrights-sec; IIRC Einfeldt had commented that M$ cannot maintain monopoly rents and would

19:41 Techrights-sec; basically fall apart below 85%'

19:41 schestowitz-TR; now it says 26% - see this morning's post

19:49 Techrights-sec; global decline on that scale is important to note!

19:49 Techrights-sec; The government bailouts are certainly what's keeping it alive and gnawing at

19:49 Techrights-sec; the world's infrastructure. There are probably obscene bailouts associated

19:49 Techrights-sec; with what it's doing to Ukraine nowadays, too. Over a longer period, though,

19:49 Techrights-sec; I would guess that they get much of their money through buying and selling their

19:49 Techrights-sec; own stock and other forms of "financialization" and that their software

19:49 Techrights-sec; aggression is just a show for the surveillance, bailouts, and financialization

19:54 schestowitz-TR; first draft

19:54 schestowitz-TR; just amended it a lot

19:54 schestowitz-TR; I try to get it out asapo

19:54 schestowitz-TR; it really makes me angry

19:54 schestowitz-TR; how much worse if I actually WORKED there

19:54 schestowitz-TR; you can refresh

19:56 Techrights-sec; the animated letter is not useful or pleasant :(

19:56 Techrights-sec; it;s not possible to pause it or back it up or stop it from progressing

19:56 schestowitz-TR; right, I won't do this next time

19:56 schestowitz-TR; I just don't want to give away metadata

19:56 schestowitz-TR; the full letter is in text anyway

19:57 Techrights-sec; using images is ok just please not animated they flip by way too fast to be

19:57 Techrights-sec; readable even by fast eyes; better to just remove the GIF than to have it as it

19:57 Techrights-sec; currently is

19:58 schestowitz-TR; I am going to add text to say the full letter is below

19:58 schestowitz-TR; and won't do this next time

20:30 *psydroid2 has quit (Quit: Leaving)

20:30 *psydroid2 (~psydroid@memzbmehf99re.irc) has joined #boycottnovell

22:09 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell

22:10 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell

22:30 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell

22:30 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell

23:25 *scientes (~490bc725@54n9xgft8g6u2.irc) has joined #boycottnovell

23:53 *scientes has quit (Ping timeout: 2m30s)

IRC: #boycottnovell @ Techrights IRC Network: Tuesday, July 05, 2022

beginning of new day, July 5

1 AM, July 5

3 AM, July 5

4 AM, July 5

5 AM, July 5

7 AM, July 5

9 AM, July 5

10 AM, July 5

11 AM, July 5

noon, July 5

1 PM, July 5

2 PM, July 5

3 PM, July 5

4 PM, July 5

5 PM, July 5

6 PM, July 5

7 PM, July 5

8 PM, July 5

10 PM, July 5

11 PM, July 5

IRC: #boycottnovell @ Techrights IRC Network: Tuesday, July 05, 2022