3 ms·
IMHO: This is a broader economic problem, and should be addressed as such. We really need to get away from the idea that you should pay for digital media based
by CaptSpify 9y ago
IMHO: This is a broader economic problem, and should be addressed as such. We really need to get away from the idea that you should pay for digital media based on the time you receive said media.
I'd love to fund journalists, and reputable news-sites, but there are far too many for me to keep track of, and not enough time and interest. I'm not sure what the solution is, but doing things the old way, just because "we've always done it that way" is silly.
- dredmorbius 9y agoAny thoughts on the sort of system which might make this easier?
- CaptSpify 9y agoI don't have much, unfortunately. The Kickstarter/Patreon model seems to be doing well, but I'm not sure I see it as a good fit for taking over Journalism.
- dredmorbius 9y agoI'm working on a longer spec, but this is what's public for now: https://www.reddit.com/r/dredmorbius/comments/6bgowu/what_if_the_web_was_filesystemaccessible/ https://www.reddit.com/r/dredmorbius/comments/6bgowu/what_if...
- CaptSpify 9y agoI'm just glancing at this, as it's a lot to read through.... I see a few things that seem hand-wavy to me: > Advertising? Mostly stripped out. > Clickbait and malware sites? Dittos. How? I like those ideas, but I'm not seeing implementation details (It's possible I'm missing them, or misunderstanding other parts of the writeup). And this is more of a UX issue, but: I can foresee problems with people mistaking their local system for remote systems. Especially with doing some kind of recursive operation, example: grep -r "somestringhere" / I'm also not sure that our current filesystem setup is going to stick around, opposed to a tagging filesystem, or something similar. I've also never seen a filesystem that handled random disconnects well, and this would likely have a lot of them. But I'm being intentionally overly-critical. I like the idea, and it would give us a "closer" understanding of what we are accessing and how it's structured. Do you have a blog or something that for this?
- dredmorbius 9y agoThere's a repo and a very preliminary document. A key concept re disconects is that downloaded data stay downloaded. Ads: there are existing tools, e.g. uBlock, which are effective. Borrowing or reimplementing from these, including host/IP blocklists, page element logic, and other heuristics, buys much of the win. Distinguishing local v. remote ops is something to think about. This is in respects a tagged FS, but with yet more elements. Recognise this is prelim and very fluid: https://drive.google.com/drive/mobile/folders/1aJOIlyFMLzLrYVzCUKqR7j3PGqg3WhWj?sort=13&direction=a https://drive.google.com/drive/mobile/folders/1aJOIlyFMLzLrY...
- dredmorbius 9y agoAlso: do you have any specific concerns on local vs. off-site actions? Most of these will refer to searches, though there are also Web requests (e.g., from links or through docs). Here the local/remote distinction is much the same as for any browser, with the distinction that if you have fetched a document it remains referenced locally rather than remotely. Also, to be clear, the focus here is on document-oriented data, or stuff that acts as a document: audio, images, a specific video. Something that is created and remains constant after creation, by and large, as opposed to programmatic or dynamic data. Even much dynamic data -- say, a stream, is considered largely a set of static messages or status updates, arriving over time. Appreciate your thoughts: dredmorbius <at> protonmail <dot> com