Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 27 06:08
    User @Mitzi-Laszlo unbanned @in1t3r
  • May 23 06:49
    @Mitzi-Laszlo banned @in1t3r
  • May 16 09:49
    @Mitzi-Laszlo banned @mediaprophet
  • Feb 01 22:04
    User @melvincarvalho unbanned @namedgraph_twitter
  • Feb 01 21:49
    @melvincarvalho banned @namedgraph_twitter
Tim Berners-Lee
@timbl
It is reasonable to host apps made by the same person in the same domain. As you are trusting that person I suppose. Unless you give the two apps different access. Then they each have to be on different domains
That design is forced on us by the browser Same Origin Policy
Sarven Capadisli
@csarven
@Mitzi-Laszlo @RubenVerborgh Is there more context to https://github.com/solid/information/pull/116/files#diff-e3711c4fe4b7ab04e3bc3ad73b11a8abR10 ? Is the intention to gather more "blog" applications or is there an undisclosed criteria for an application that's not built yet?
Ruben Verborgh
@RubenVerborgh
Ah no it's basically my undergrad students being assigned the task to build a blog app on Solid
Sarven Capadisli
@csarven
Cool.
Bonus point: demonstrate consuming of data created by another application :)
Jeff Zucker
@jeff-zucker
@Otto-AA the per-orign localStorage cache is working now in solid-rest-browser
tjhorton
@tjhorton
Where can I ask a fundamental newbie question such as: why distribute data instead of creating a coop to own and control data, and sell memberships in it? (solve data ownership with ownership rather than technology). Food for thought, or indigestion (sorry)?
Ghost
@ghost~57bc59d440f3a6eec060e93b
Better yet, support overpayments and.change the available solutions for those who do some sort of.work online, then use transactional incomes to ensure no one needs to sell personal data whatsoever... Billions of people, trillions of things, shouldn't take much to get an hourly wage for good work... other than the investment required to make the technology needed for said new forms of taxable revenue option. Obviously, the issues people had since exodus in trying to get paid for old types of work, like that of a stonemason, are now fairly well resolved. Perhaps the problem is that we need to bring about a global web strike!
Arne Hassel
@megoth_twitter
@tjhorton I would suggest searching https://forum.solidproject.org/ for existing threads, or create a new thread if noone fits your interest ^_^
gitter is a bit difficult to follow when discussions get lengthy
Ghost
@ghost~57bc59d440f3a6eec060e93b
Should say, micropayments, not overpayments. So many jobs to do, there's a glut of jobs, no shortage of them. Just a complete lack of suitable financial instruments and related support infrastructure.
Floor price for a micropayment should be as low as possible, incorporating the cost of the energy consumed to support it.
Ghost
@ghost~57bc59d440f3a6eec060e93b
https://digiconomist.net/bitcoin-energy-consumption won't work. I've been working to figure how how to share the revenue sourced from say, a 2c app, across hundreds of contributors providing thousands of hours work, to.make it happen, who say, want to get paid $50 per hour (only), for having done the work (a very basic example), then the app might be made free, via an approach I called last year, software as a utility...
Noting, many models can be defined using rdf / semweb goodness...
Mitzi László
@Mitzi-Laszlo
@tjhorton here's a talk on why you should control your data https://www.youtube.com/watch?v=eiFBljkGWAc&t=42s personal data control is both a legal and technical so one does not exclude the other, they complement and strengthen each other
Kris Chen
@kristophor
hello guys
just wondering anyone working on solid apps locates in Toronto want to be Toronto meetup speaker
tjhorton
@tjhorton
@Mitzi-Laszlo I'm as concerned as you are for both legal and technical. Please reference my link above.
tjhorton
@tjhorton
My point is that a data coop solves both legal and technical aspects without splintering the data. Consolidation does not equate to exploitation, if we own the consolidator (a standard legal coop).
Arne Hassel
@megoth_twitter
And nobody should stop you in trying to create that co-op
Maybe Solid can be part of that even, it is about social linked data after all
The focus here is on developing Solid into becoming what it can become - a decentralized ecosystem where people control their data
And all of the services and innovations we hope for to be part of that
In any case, I think at the center of it should be interoperability - services able to work on the same set of data, giving people more choices in how they consume and produce their data
Tim Berners-Lee
@timbl
I had a chat recenntly with a lawyer who hd been heavily involved in the uk Coop which in nowadays mostly food shops but at one point was many things. He thought that looking at coop legal systems for Solid data storage could be a good idea.
Julian Cole
@Julian-Cole
@timbl interesting! something I was thinking of is that I'd like to see local libraries have more involvement in open services that support features in the solid core app set that should be available to everyone for free.
Mark Hughes (happybeing)
@theWebalyst
Anyone around to think about a node packaging issue with me? I'm trying to build a module that has a circular dependency, i.e. a fork of solid-auth-client, where: solid-auth-client -> safenetworkjs -> rdflib -> solid-auth-client. I don't think this can work, but would love to hear if there's a way to do this.
Mark Hughes (happybeing)
@theWebalyst
Would it be possible to make rdflib external to safenetworkjs (so bundling leaves it unresolved) and have solid-auth-client provide rdflib for safenetworkjs to pick up? I don't know if that even makes sense, but I see that rdflib seems to do something like this when building a browser bundle, but not for this reason (here).
Tim Berners-Lee
@timbl
NPM should manage the circular dependenctybut I am not an expert
webpack also
Mark Hughes (happybeing)
@theWebalyst
Thanks Tim. I get a memory allocation error during the webpack bundling, which doesn't happen if I break the circle so I'm thinking it's related. I have found some suggestions on StackExchange so have things to try.
Arne Hassel
@megoth_twitter
I thought NPM should handle that as well, but if method foo in package A is calling method bar in package B, and method bar is calling method foo, you might get a circular dependency that never exits - that isn't the case here, is it?
Mark Hughes (happybeing)
@theWebalyst
I'm not 100% sure so am going to use my sophisticated debugging technique of prodding and poking until it works [cough].
Jeff Zucker
@jeff-zucker
@theWebalyst that particular use of external in the webpack (rdflib sets solid-auth-cli to null) basically says - rdflib depends on solid-auth-cli so include it but if we're building the browser version of rdflib, use solid-auth-client and forget solid-auth-cli exists ... Overall effect is we get one on the command line and one in the browser but never both.
same here with the prodding and poking until ... :-)
Mark Hughes (happybeing)
@theWebalyst
Thanks Jeff, I see the null thing is probably not helpful for this. I shall poke :grin:
Fabian Cook
@fabiancook
@theWebalyst within your module, maybe completely leave out the rdflib dependency, and instead of a dev/peer dependency, then have provided at runtime
Mark Hughes (happybeing)
@theWebalyst
How would I do that?
Fabian Cook
@fabiancook
By doing this with us much as you can, you can reduce coupling... for example I have an fs compatible implementation provided to one of my modules via an options object...
// These are all the functions we utilise
// If a method requires a specific function that isn't provided
// then the method won't be available
export type FSCompatible = {
  unlink?: typeof fs.unlink,
  lstat?: typeof fs.lstat,
  chmod?: typeof fs.chmod,
  stat: typeof fs.stat,
  rmdir?: typeof fs.rmdir,
  readdir?: typeof fs.readdir,
  readFile?: typeof fs.readFile,
  writeFile?: typeof fs.writeFile
};

export type FSStoreOptions = {
  fs: FSCompatible;
}
It would require you to follow a model where you can pass that options object around though...
Mark Hughes (happybeing)
@theWebalyst
Thanks, I don't understand this. Can you link to the repo so I can see it in context?
I'm not sure if I'll have the flexibility to do something like this, but it will be useful to understand the design pattern regardless.
Mark Hughes (happybeing)
@theWebalyst
Cool, thanks very much!
Fabian Cook
@fabiancook
You'll see the same pattern throughout my projects
The reasoning behind this... I can now run an almost fully solid compatible implementation in the browser, in react native, and on the server, which can also be deployed in a serverless environment, no dependency on express, or node, or even having a persistent filesystem... if you wanted to just use your normal filesystem in node.js, fine, just pass the fs module no problem, if you want to use anywhere else, use hyperdrive