Main

related bits

0

processing priority

4

site type

3 (personal blog or private political site, e.g. Blogspot, Substack, also small blogs on own domains)

review version

11

html import

20 (imported)

Events

first seen date

2024-08-13 09:44:11

expired found date

-

created at

2024-08-13 09:44:00

updated at

2026-03-10 11:15:39

Domain name statistics

length

28

crc

9706

tld

2211

nm parts

0

nm random digits

0

nm rare letters

0

Connections

is subdomain of id

13642151 (wordpress.com)

previous id

0

replaced with id

0

related id

-

dns primary id

0

dns alternative id

0

lifecycle status

0 (unclassified, or currently active)

Subdomains and pages

deleted subdomains

0

page imported products

0

page imported random

0

page imported parking

0

Error counters

count skipped due to recent timeouts on the same server IP

0

count content received but rejected due to 11-799

0

count dns errors

0

count cert errors

0

count timeouts

3

count http 429

0

count http 404

0

count http 403

0

count http 5xx

0

next operation date

-

Server

server bits

server ip

-

Mainpage statistics

mp import status

20

mp rejected date

-

mp saved date

-

mp size orig

600288

mp size raw text

120028

mp inner links count

11

mp inner links status

20 (imported)

Open Graph

title

Working Memory

description

image

site name

Working Memory

author

updated

2026-02-01 20:24:45

raw text

Working Memory Skip to content Working Memory GraphQL is for silos GraphQL is booming. After Github released its GraphQL API it’s clear that many other services and developers are going to try to adopt the technology. It might have been a turning point. There are many things to like in GraphQL. For example, the typing system , the idea of having, at last, an effective schema mechanism connecting client and server, or the view of a unified data graph you can query. Many of those ideas are not new at all, but if GraphQL is able to finally make them popular and accepted by development teams, I would be very happy. However, there’s a main design problem with GraphQL that needs to be addressed: GraphQL is for building silos. This open issue in GraphQL Github’s repository shows the problem clearly. GraphQL exposes a single data tree, through a single end-point. All your data is captured in that single data space and cannot reference or be referenced from other GraphQL ...

Text analysis

redirect type

0 (-)

block type

0 (no issues)

detected language

1 (English)

category id

Other [en] (231)

index version

2025123101

spam phrases

0

Text statistics

text nonlatin

0

text cyrillic

0

text characters

65535

text words

17129

text unique words

2163

text lines

2233

text sentences

587

text paragraphs

255

text words per sentence

29

text matched phrases

27

text matched dictionaries

5

RSS

rss status

32 (unknown)

rss found date

2024-08-22 21:06:29

rss size orig

525358

rss items

10

rss spam phrases

0

rss detected language

1 (English)

inbefore feed id

-

inbefore status

0 (new)

Sitemap

sitemap status

30 (processing completed, results pushed to table crawler_sitemaps.ext_domain_sitemap_lists)

sitemap review version

2

sitemap urls count

23

sitemap urls adult

0

sitemap filtered products

0

sitemap filtered videos

0

sitemap found date

2024-08-14 12:49:46

sitemap process date

2026-03-10 11:15:39

sitemap first import date

-

sitemap last import date

-