#solid

traceroute landingpage ipvx

/ configedit / Leave a comment 
Start: 2024-02-05T15:36:45+0500
HOST: DNSChecker.org                                            Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ???                                                       100.0     3    0.0   0.0   0.0   0.0   0.0
  2.|-- 10.74.132.69                                               0.0%     3    0.5   0.7   0.4   1.1   0.4
  3.|-- 138.197.251.12                                             0.0%     3    0.8   8.2   0.8  23.0  12.8
  4.|-- 138.197.248.18                                             0.0%     3    0.9   0.7   0.6   0.9   0.1
  5.|-- nyk-b11-link.ip.twelve99.net (62.115.45.5)                66.7%     3    1.1   1.1   1.1   1.1   0.0
  6.|-- nyk-bb2-link.ip.twelve99.net (62.115.112.70)               0.0%     3    2.3   2.1   1.9   2.3   0.2
  7.|-- ldn-bb1-link.ip.twelve99.net (62.115.113.21)              33.3%     3   73.4  73.6  73.4  73.7   0.1
  8.|-- prs-bb1-link.ip.twelve99.net (62.115.135.25)               0.0%     3   80.2  79.8  79.5  80.2   0.3
  9.|-- prs-b3-link.ip.twelve99.net (62.115.118.59)                0.0%     3  111.7  90.6  79.9 111.7  18.3
 10.|-- ae5.sxb1-ibr-tarazed.bb.godaddy.com (80.239.192.122)       0.0%     3  143.3 106.0  85.4 143.3  32.3
 11.|-- ae7.fra10-cr-antares.bb.gdinf.net (87.230.115.2)           0.0%     3   91.0  91.4  91.0  92.0   0.6
 12.|-- ae2.cgn1-cr-nashira.bb.gdinf.net (87.230.114.4)            0.0%     3   90.3  90.3  90.3  90.3   0.0
 13.|-- po250.sr-left.cgn1.dcnet-emea.godaddy.com (87.230.114.79)  0.0%     3   92.8  92.8  92.7  92.9   0.1
 14.|-- ???                                                       100.0     3    0.0   0.0   0.0   0.0   0.0
 15.|-- wp633.webpack.hosteurope.de (5.175.14.155)                 0.0%     3   92.8  92.8  92.6  93.1   0.3

2024 (solidproject)

/ configedit / Leave a comment

Hallo liebe Peergroups.

nachdem die Jahresendwellen sich langsam wieder etwas gelegt haben, nun etwas Eigenwerbung.
Wir (4 Administratoren) haben ein Kollektiv gegründet.
Nun habe ich 12 Jahre in einer WfbM gearbeitet und muss weitere 8 Jahre schaffen.
Da das keine echte Perspektive ist, versuche ich eine halbe Solo-/Community-/Netz-Existenz zu gründen.
Die Familie ist wohlauf und auch meine Ex-Krebserkrankung hat sich in Luft aufgelöst.
Mein Home sind 17 Leute und behandelnde Professionelle gibt es mehr als genug.

Wir arbeiten daran, die Data-Silos überflüssig zu machen und den Usern (uns allen) die Rechte an ihren eigenen Daten zurückzugeben.
Wenn Du/Sie/Ihr also einen Fünfer für Datensicherheit und -souveränität übrighabt, bitte ich Euch, unter nachgenannter URL einen kleinen Obulus zu spenden.
Dies ist kein Ewing-Versorgungslink sondern für einen Server, der etwas mehr Netzgerechtigkeit schafft.
Bürokratische Hindernisse gibt es noch einige, aber die werden getacklet.

Seht Euch https://opencollective.com/meisdata/projects/teamid an.

Danke, thank you.

Dear peergroups.

now, after the years-end-eruptions have vanished, now a bit of advertising.
We (4 Admins) have founded an open collective.
I have worked 12 years in a print-office and have further 8 years to go.
Because this is no real perspective, where one can build a house on, I try to found a Solopreneur-/Community-/Web-existance.
The family is fine and healthy and the cancer is gone forever (thank God).
I live together with 16 people and Docs/Staff is around more than necessary.

We are trying to make the Data-Silos obsolete and to empower the Users (us all) and give them back the rights over their data.
This is not personal/egocentric but helps to flip the web right-side-up.
So if you can afford a fiver for data safety I ask you politely to donate a small amount under following URL.
There are still some bureaucratic hurdles but they are being tackled.

Have a look at https://opencollective.com/meisdata/projects/teamid .

Danke, thank you.

Intro

/ configedit / Leave a comment

Introduction

This document provides an overview of Solid, a framework designed to enhance data management on the web. Solid introduces a method for users to store and control their data separately from the applications they use.

Overview of Solid

*Data Management with Solid*

Solid enables users to store their personal data in online data stores, known as Pods. These Pods are controlled entirely by the user, who can grant or revoke access to applications as desired. This separation of data from applications allows for greater user autonomy over their personal information.

*Solid’s Technical Approach*

The technical foundation of Solid is based on principles of Social Linked Data (SoLiD), facilitating the interconnectivity of data across different platforms and applications. The emphasis is on data portability and interoperability within a secure framework.

Concept of a Web Operating System

*Solid’s Role*

While Solid contributes to the broader idea of a web-based operating system by enabling the modular use of web applications, the focus remains on its function as a data management framework. The notion of a web operating system is a broader concept, one of many potential applications of the Solid protocol.

*Application Diversity and User Choice*

Solid encourages a diverse ecosystem of client-side applications. This variety provides users with the flexibility to choose applications based on their specific needs and preferences, without being limited by data storage constraints.

Security and Privacy in Solid

*Data Control and Privacy*

One of Solid’s key features is its emphasis on user-controlled data privacy. Users have the authority to manage who can access their data, enhancing privacy and data security on the web.

Solid in the Web Ecosystem

*Integration with the Web*

Solid is designed to function within the existing web ecosystem, complementing and enhancing current web standards. Its focus is on user data management rather than redefining the web infrastructure.

Conclusion

Solid represents a structured approach to data management on the web. It provides a framework for user-controlled data storage and application interoperability, contributing to the development of a more user-centric web experience.

© Melvin Carvalho 2023-11-23

: —- thumbsup —- :

2023-10-19 v7

/ configedit / Leave a comment
v7.0.0
New features
The minimum supported Node version is now v18.
Account management and everything related to it have been drastically changed, see the usage documentation for an overview of the new features, and the architecture documentation for an overview of the new structure. On a default server, the entry point for everything related to accounts is http://localhost:3000/.account/. Creating an account now requires multiple steps, but allows you to have multiple pods or WebIDs for 1 account. The architecture has been updated to be more easily extensible.
Pod seeding has been updated to account for the new account management, with an updated CLI parameter –seedConfig, see the updated documentation for more details.
Migration was added to update account data automatically from previous versions. See below for more details.
Due to the changes in account management, setup has been removed completely. The *-no-setup.json configurations have been renamed to *-root.json to indicate their focus on the root container.
The StaticAssetHandler can now be used to link static pages to containers. This can be used to set a static page for the root container of a server. See the /config/app/init/static-root.json config for an example.
Data migration
Old internal data will need to be migrated. When starting the server for the first time after updating the version, this will happen automatically. A prompt will be shown to confirm. It is advised to first backup the internal data in case something goes wrong. When using the filesystem backend with default storage options, these can be found in the .internal folder.
Only account data will be migrated, other internal data such as OIDC sessions and notification subscriptions will be removed as how they are stored has changed as well. This means existing tokens and sessions will be invalidated and users will have to log in again. Notifications will have to be resubscribed to for the same reason.
This migration step is based on how storage is defined in the configurations provided in this repository. If you made drastic changes to how internal data is stored, you might need to have a look at the app/init/migration/v6.json configuration.
In case the prompt causes issues, it can be skipped automatically with the –confirmMigration CLI option.
Configuration changes
You might need to make changes to your v6 configuration if you use a custom config.
The @context needs to be updated to https://linkedsoftwaredependencies.org/bundles/npm/@solid/community-server/^7.0.0/components/context.jsonld.
The following changes pertain to the imports in the default configs:
There is a new identity/oidc import set that needs to be added to each config. Options are default.json and disabled.json.
There is a new static-root.json import option for app/init, setting a static page for the root container.
There is a new initialize-root-pod.json import option for app/init, initializing a pod in the root.
There are more identity/handler options to finetune account management availability.
There is a new set of imports storage/location to determine where the root storage of the server is located.
The app/setupand identity/registration imports have been removed.
There is a new ldp/handler/disabled.json import to disable the LDP API.
The following changes are relevant for v6 custom configs that replaced certain features.
All configurations that had a reference to setup have been updated.
/app/init/* imports have changed. Functionality remained the same though.
All imports that define storages have been updated with new storage classes.
/http/notifications/base/storage.json
/storage/keyvalue/storages/storages.json
All identifiers containing the string "WebHook" have been renamed to instead use "Webhook" to be consistent with the notification type.
/identity/* configurations have drastically changed due to the account management update.
/http/static/default.json has been updated to allow easier overriding of the static resources.
Interface changes
These changes are relevant if you wrote custom modules for the server that depend on existing interfaces.
The AppRunner functions to create and start the server now take a singular arguments object as input.
Most of the key/value related storages had their constructors changed to allow more values.
EncodingPathStorage has been removed and its functionality split up over Base64EncodingStorage and ContainerPathStorage. HashEncodingPathStorage has similarly been replaced by introducing HashEncodingStorage.
All classes with the name WebHook* have been renamed to Webhook* to be consistent with the corresponding notification type.
Most classes related to the IDP have been changed.
All classes related to setup have been removed.
The StaticAssetHandler has bene updated to support the new functionality.
SeededPodInitializer has been renamed to SeededAccountInitializer.
WebIdAdapterFactory has been renamed to ClientIdAdapterFactory.
view raw gistfile1.txt hosted with ❤ by GitHub