the other thing that’s a problem is that that web authority is conceived of in terms of web origins and domain names, not in terms of namespaces or uri prefixes. dns as it is currently used enshrines organizations over people. if you want long lived links that resist link rot, you need to pick a domain name and stick with it, and this has an upkeep cost. orgs can more easily manage this upkeep cost, people have a harder time with it.
=> More informations about this toot | View the thread
i have to conclude that the biggest barrier to entry to the personal web, aside from obtaining access to hosting, is the expectation that every page on a website has to look the same, be styled the same, have the same navigation menu, and so on. it’s just so much easier to write the html for a page once, and then never update it again. the very instant you introduce an expectation of retroactive consistency, you now require a site generator or a build system. that’s a big ask!
=> More informations about this toot | View the thread
I must not consume brainrot. Brainrot is the mind-killer. Brainrot is the little-death that brings total obliteration. I will face the brainrot. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the brainrot has gone there will be nothing. Only I will remain.
=> More informations about this toot | View the thread
people really misunderstand the "80-20 rule" a lot, i'm realizing. it's got nothing to do with "doing 80% of the work" or "covering 80% of the use cases". the 80-20 rule (pareto principle) is that 80% of the effects can be attributed to 20% of the causes. so if you are looking for an "80% solution", this then means you are only solving 20% of the problem space.
the remaining 80% unsolved stuff might be just "edge cases" that only matter 20% of the time, but those cases can be the most insidious
=> More informations about this toot | View the thread
idle thought: morality is a function of values. different people have different values and thus morality is necessarily relative. to say that something is "good" is a statement that encodes your values into it. good things are good, but only to you. to someone else, good things can be bad. people with common values can build structures that encode those values, but this in turn excludes anyone who disagrees. don't pretend that universal good exists. what matters is who is building the structures
=> More informations about this toot | View the thread
lemme apply to these 0 jobs real quick… “new jobs are still available” my ass
=> More informations about this toot | View the thread
linkedin moment
=> More informations about this toot | View the thread
“clearly you never played with the mastodon api” is perhaps the funniest thing you could say to me while being confidently wrong about how the api works at a fundamental level. buddy. i wrote the documentation. i might have in fact actually played with the api a bit
=> More informations about this toot | View the thread
this isn't enough to get me to use kde but i am kinda jelly that seemingly the only way to have working drag-and-drop between an archive manager and a file manager is to use ark + dolphin
=> More informations about this toot | View the thread
gonna spend tonight doing some desktop maintenance i think
=> More informations about this toot | View the thread
hitting 1.66TB used out of 1.81TB on my desktop, might be time to unsync some stuff soon-ish >_>
=> More informations about this toot | View the thread
btw my Wii friend code is 7364 3317 6417 6050
=> More informations about this toot | View the thread
2007 is eternal
=> View attached media | View attached media | View attached media | View attached media
=> More informations about this toot | View the thread
currently, my answer is "object storage to store the content + metadata store to describe the logical objects"
is there a better way? idk, but that's it, that's all i got rn
the object storage can be serialized to a filesystem of arbitrary files (even just text files), and the metadata store can be serialized to a bunch of RDF graphs (filesystem hierarchy mostly irrelevant but yeah you can just import an entire folder and subtree)
this seems convenient enough?
=> More informations about this toot | View the thread
the takeaway really, is that if we want the content to be replicable and manageable by some user(s), then it needs to be put into some data store, and it is exactly that data store that i am trying to model. the data model needs to support lossless serialization into whatever convenient format some person might ask for or need. i don't think "sql data dump" is an ideal export format, and i don't think "a really big json file" is ideal either. i want something that can be split up into atoms.
=> More informations about this toot | View the thread
but just as we can inline text content, we can also separate it and link to it, we can stick it into object storage and address it as that literal text. and we can then arbitrarily package and wrap it into whatever containers or as many layers of containers as we care to do so. we could take some plaintext content and wrap it in some HTML template that itself gets wrapped in what eventually becomes an HTML document which itself gets wrapped in an HTTP message. this is more or less how we do rn.
=> More informations about this toot | View the thread
and you can of course unwrap those layers of containers of head+body as well. when there's nothing left to unwrap or extract, that leaves you with some base atomic content, which may be just some plain text.
i argue that this is not meaningfully different than, say, a png file. it's just that text is often inlined into the presentation layer. we don't go about browsing the metadata and then linking to the content, we just stick the content directly into the same view as the metadata...
=> More informations about this toot | View the thread
entirely natural, of course -- HTML is most often used to serialize documents that are browsed on the Web. but for the most part, that's all presentational stuff! if you removed it, you would lose aesthetics, but the core of the message is only some certain part, that can be extracted and handled on its own. the rest of it is just part of the view or (re)presentation.
i've talked before about how you can combine body content with header metadata and get a document that can itself be body,
=> More informations about this toot | View the thread
the area where my thinking seems to differ from most of what i've seen so far is that i don't make a real distinction between text and binary anymore. content is content. so this implies that the object storage is not just for media, but for everything, including text files. but the thing is that content should be strictly content. what most people get "wrong" with HTML for example is that they require an entire structural wrapper, which is itself wrapping not just a body but also a header
=> More informations about this toot | View the thread
i think honestly what i want out of a storage solution is to like maybe upload stuff to some kind of object storage and then separately have a graph database or rdf quad store for the metadata. but i’m wondering if it can be made simpler without losing the ability to handle any general use case, or if this is as simple as it gets
(a filesystem is the wrong level of abstraction, i’m interested in logical handling of objects which may or may not have content that is either binary or text)
=> More informations about this toot | View the thread
=> This profile with reblog | Go to trwnh@mastodon.social account This content has been proxied by September (3851b).Proxy Information
text/gemini
