I dropped my FairPhone 5 from a bicycle on unwelcoming pavement at good speed. Broke the camera glasses, the screen protector, the carry case and the back cover. It looked positively destroyed and my first thought was “yay, it’s repairable”. Repairing was easy enough and aside from some war wounds on the side of the case (scratches) it’s as good as new. I’m glad I got this phone.

Aside from being repairable, I also appreciate the e/OS support.

I’m also waiting for this to move some 500 repositories from GitHub to a realistic federated alternative. I follow up from a distance but don’t see much movement on ForgeFed for ForgeJo. Did I miss something?

Battery temperature management seems to be a key limiting factor.

At least a few years ago, and likely still, the reasons and conditions under which the barrier layers in the battery degrade were not super well understood. Heat seems to be a key contributing factor and charging a battery quickly warms up the battery and I suppose not fully evenly within a cell. Not knowing the complete extent of this makes the early LEAF’s lack of actively cooled battery a reasonable choice. Before that, the batteries of earliest Prius cars held up way longer than expected.

Like with a phone: heat and cold is not super awesome for the battery. It seems heat is especially bad for longevity.

Mate, I’m not sure you’re making a convincing argument for remote cooperation here. When OP said sometimes, that is clearly the majority of cases in your book but I do read that differently.

Be kind and think of the other people in the conversation. If you want remote to work then act in a way that shows it does work.

Either case, best of luck in pushing for remote work! Cheers

I grew up online and there are people I’ve never met in person whom I can work with no problem. I have never had the need to see someone in person for work myself, but the click isn’t there for everyone.

I dislike generational thinking and this argument seems to play on those lines; I have seen some people working better remote and some working better partially in person regardless of their generation or background. Younger people are more fluent in working remotely but not everyone wants that full-time and sometimes it doesn’t work out too well either. Often working in the office is the worst so let’s make/keep remote the default.

My personal opinion is that we should do everything online which can be online and that people who need to work in person should do their best to cater for working online. It helps with climate and can help work/life balance.

Any form of communication gap is a shared gap. Both sides have to cater to make the conversation work. If OP needs face-to-face then that must be taken into account. If you want that conversation to happen you’d better care for their needs as much as they’ll care for yours. OP may have extensive experience in working with people and may have seen this need on their own end and likely on the other end too. Perhaps even only on the other end. On the spectrum of cooperation I’m sure there will be cases where it helps and perhaps even be necessary. I believe it’s a small subset of situations.

By all means, try to stay constructive and learn from others. Whatever they have learned in the past likely applies to our new ways in another form. I would like it if we could keep improving remote.

I don’t think Xerox invented the computer mouse. It was first drawn out by Douglass Engelbart and presented to the public in the 1968 presentation “Augmenting the Human Intellect” (you can watch it on the present day, it was recorded).

It was my understanding (which I did not verify) that this was picked up by Xerox and others and that windowing systems evolved from there on with Xerox leading towards Desktop Publishing.

This must be from another timeline. Sorry for the inconvenience, please skip.

User focused applications running on my own internet accessible infrastructure fully based on open standards and interoperable with the Fediverse… Yes please

I’m looking forward to play with this.

Short-haul can hopefully be handled by improved battery tech. Long-haul would need even lighter batteries so it’s less likely to work or will take longer.

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.

Wow. So Global Aviation puts as much carbon in the air every year from a fossil fuel source which we can’t put back than the unique and terrible wildfires Canada had in 2023.

We sure need to fly less!

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.

Water also needs a substantial amount of energy to evaporate, hence it will sip some heat from the environment around it when it evaporates. Combined with the good thermal conductivity of steel, the bridge cools off.

You get a similar effect when walking out of a hot shower. The hot water evaporates and cools you down.

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.

https://github.com/mu-semtech/sparql-parser contains an EBNF parser for SPARQL, an LL(1) language. You might be able to borrow code, not sure how well it translates to scheme. GitHub asked me to log in to see the gist so I’d have to have a peek later.

sparql-ast folder contains the relevant bits regarding the parsing.

Nice script. What is the reason to toggle the brightness?