Sfner @sfner@awoo.space

@typhlosion @byte
[+]
(forgot to add last message: all base claims are publicly readable, but claims can contain encrypted claims in its message)

Instead of propagating changes, some devices would prefer fetching changes and entering a low-power mode. Battery-powered devices like phones, for example.

Disallowing writing custom user-patchable server code might end up like ZeroNet, but there's the "application handles interoperability" caveat from Linked Open Data to also avoid. [+]

@typhlosion @byte
[+]
When designing the data and application layers, I reached other conclusions.

Instead of splitting "Identity" "Networking" and "Content" into different provider boxes, I thought like "everything is a file" and settled at "everything is a claim". A base "NULL claim" that points towards some hard-coded behavior (like pypy, it's Rpy built-ins and cpython reimplementation as py scripts) would provide the required bootstrapping.

[+]

@typhlosion @byte
[+]
After working with an oldschool internet enthusiast, I could finally understand why university professors compared internet with telephone system: IP is basically a telephone system with a fixed size. It carries over a lot of flaws, which includes all the means for arbitrarities from any part (censorship included). I can imagine some ways to aglutinate computers, but I'm still not sure if it would scale well and still fit within the constraints of an arduino.

[+]

@typhlosion @byte nice to read some opinions on a similar idea I had. While dabbling a bit with OpenFlow SDN, I had one problem: I needed a representation of a computer, to know that I'm reaching the same host twice and beyond.

Computers can have dual-ethernet, wifi, bluetooth, 5G modems and other outgoing interfaces that all use Internet Protocol. Look at your phone and wonder what happens if you used Bluteooth PAN, WiFi and 4G all at the same time. In the end, I needed a mesh protocol.

[+]

@elise Ragnarock might be a good try

@Zauberin in my honest opinion, it compares to telegram.

@typhlosion notepad++
People will say they're nostalgic, but [...]. If they do, then mission accomplished: you've annoyed them

@Mareepy I just wash it with liquid soap for hands but I'm not sure if it's the best way

@elise how was your discovery process?

@elise I have something like that set up to run daily at midnight, along other backup routines x_x

@Azure I use "Unhook" for that: https://addons.mozilla.org/pt-BR/firefox/addon/youtube-recommended-videos/
Not mobile-compatible, though :(

@noiob me, 7 years later: "you're too slow!"

@noiob that curved progress bar is pretty amazon-looking, isn't it?

@noiob sounds like integer scaling with lower N pixels of the square turned off.
E.g.: 320x240 interlaced signal upscaled 4x to 1280x960 and with zero-indexed lines line%4==3 (3, 7, 11, 15, 19, ..., 955, 959) being completely shut down, line%4==0 being updated every even (frame_no%2==0) frame and going black otherwise, line%4==1 being updated every frame, and line%4==2 being updated every odd frame (frame_no%2==1) and going black otherwise. This way you'd get really intense CRT feelings.

@noiob that's not just on iOS, but on pretty much every android release too, which is the result of an interface contract that doesn't get honored between OS releases that re-implements stuff all the time and leaves for the app developers to figure out a cross-vendor-compatible and cross-version-compatible way their app can be rewritten in this implementation hell. Apple is less worse for developers because cross-vendor-compatibility isn't an issue.