I had to read the overview and it looks nice. It reads like IPFS without some of the challenging cruft. Well written!

IPFS seemingly works small scale but not large scale. What makes tenfingers handle millions of files and petabytes of data better than IPFS? Perhaps that is not the goal. In what way do you think the tech scales? Why will discovery of the node which has the data be short?

I want to ask for benchmarks but you can't do a full benchmark without loads of resources.

I'm not actively looking but please do share references! Other people may read this and they may want to know too. Perhaps I'll jump back in the rabbit hole at some point too 😁

Exactly. The Semantic Web is broader than Solid but Solid is great for personal apps.

Say you buy a smartphone. The specifications of the smartphone likely belong elsewhere than in a Solid Personal Online Datastore, but they can be pulled in from semantic data on the product website. Your own proof of purchase is a great candidate for a Solid POD, as is the trace of any repairs made to it.

These technologies are great to cross the barriers between applications. If we'd embrace this, it would be trivial to find the screen protector matching your exact smartphone because we'd have an identifier to discover its type and specifications. Heck, any product search would be easier if you could combine sources and compare with what you already have.

The sharing tech exists. Building apps works also. Interpreting the information without building a dedicated interface seems lacking for laymen.

IPFS would replace Content Delivery Networks in present day.

It would also allow you to host software and other content from your own network again without the constraints modern Internet Service Providers pose on you to limit your self-hosting capabilities.

If applications are built for it, it could serve as live storage for your applications too.

We ran ipf-search. In one of the experiments we could show that a distributed search index on ipfs-search, accessible through JavaScript is likely feasible with the necessary research. Parts of the index would automatically be hosted by clients who used the index thus creating a fairly resilient system.

Too bad IPFS couldn't get over the technical hurdles of limiting connection setup time. We could get a fast (ElasticSearch based) index running and hosted over common web technologies, but fetching content from IPFS directly was generally rather slow.

The semantic web and social linked data. We could have applications share data without depending on big tech, but rather based on application standards.

It can be used today and gains traction but I wouldn't mind it going faster. Especially the interoperable personal app space could use some love and attention.

To be honest, I didn't know by heart what we stated exactly. It says "Open source". When we ask we may well say "like a GitHub handle".

For people without much experience it can all be a bit daunting. They'll know about GitHub and it helps them identify what we're hoping to see. By now I expect links to open source work in a CV due to the nature of our company but it's not a requirement.

It's a balancing act in getting the right hints in a vacancy for people in the know and providing enough info for people who don't know yet.

GitHub wasn't all that bad years ago and it's easy seeing this find their way in HR forms and taking as long to be removed again. I certainly wouldn't shun entering a CodeBerg/GitLab/selfhosted url in a form where I should enter a GitHub handle.

We also ask for a GitHub handle but when one supplies Codeberg or GitLab it's seen as very positive. Might not be the case for standard HR though.

Belgian here. It's about money and racism. Flanders (north) makes more money and has a higher employment rate. The separatist movement aims to put Flanders' wealth first.

Foreigners are perceived to threaten our way of life and are perceived to cost money too. Vlaams Belang has been rather controversial in their statements earlier with a new young team creating some uproar. Both claim to benefit the Flemish citizen and will create better jobs with higher incomes.

Far left also gained ground so we are becoming more polarised.

I'm not a legal expert, but this talks about "inability to fulfill a contractual obligation" rather than the refusal to do so.

I assume the problem is slightly different and it is mainly a problem of not being able to go after the money (perhaps at reasonable cost) if the travelers have it?

Mercedes's stars have been on springs for decades indeed. You can easily push them over (but make sure you put it back nicely). I think Rolls Royce's Spirit of Ecstasy pops back into the hood but I don't know how that works on impact.

I'm not sure either, but I'm happy it exists!

I own a 1973 Citroen DS Pallas 23ie with semi automatic gearbox. Few of these survived so it should be on the road. Yet "burning dinosaurs" doesn't sit right with me. Who do you preserve a car experience for if it will ruin them anyhow. The engine was never the DS's forté so an electric engine couod make a lot of sense, especially if you can simulate the feel.

As for hooning around, I guess it could be fun. It's been pointless fun on a track before. It would still be pointless fun. Perhaps it will feel a bit more empty.

I write my notes in org-mode. It's supported in many editors in a basic form, letting you add code snippets etc in an unobtrusive way. Using a well thought out format helps you in the long run.

I use this in Emacs, through which it lets me refer to emails, execute code snippets, attach related files, fetch content on/from remote servers, send off the debug session as an html email, ... Support will depend on your editor but even as raw text it works.

I don't use something specific to make non-code repeatable as you suggest here, but you could embed a test language in an org code block.

The syntax is straight-forward and exports to multiple external formats exist (eg: html).