Blubberbub

I'm not a huge fan of the reverse chronological timeline in #mastodon, because it is bad for threads and makes me read stuff in reverse order and question myself if I've seen a status already or not when scrolling down. So I made an attempt at creating a Mastodon client showing a chronological order:
https://mapeper.github.io/chrono-todon/
I kind of like it, but it only barely classifies as a proof of concept and will need a lot more work to be usable, which I will probably never get to.
#javascript #webdev

Habe jetzt schon mehrfach gehört, dass ein Problem von #emobility ist, dass die Leitungen zu den Häusern nicht ausreichen und deshalb erst die Stadtwerke neue legen müssen. Könnte das nicht "einfach" über den vorhandenen Herdanschluss und ein Lastabwurfrelais realisiert werden?
Laden, wenn der Herd aus ist wirkt auf mich wie eine sehr akzeptable Lösung/ein guter Kompromiss.
Oder übersehe ich da etwas?

I made a web version of the sea-surface-temperature anomaly plot, that was shared a lot a few days ago: https://mapeper.github.io/sea_surface_temperature_anomaly/

Automatically updates when new data becomes available from Climate Reanalyzer.
#dataviz #climatechange #climatecrisis #javascript

@bluestarultor@tech.lgbt @marcamos@front-end.social

There is an updated version, that offers improved algorithms, here: http://mapeper.github.io/jsColorblindSimulator/

Happy you find it useful.

@thoralf@ck.umrath.net
Another option might be `git stash; git pull --ff-only; git stash drop`.

Will still conflict if you pull a file that was newly created locally and remote at the same time, though, but that's probably unlikely.

Also make sure that you are not in any conflict or merging mode at the moment. (E.g. `git merge --abort`)

@Luca@vis.social You can revoke the access token by POSTing to /2/oauth2/revoke with token, client_id, token_type_hint=access_token in body. The app will then disappear from the settings and also should do so automatically if the token expires after some time.

@aixaves you can embed the css directly into the SVG file:

https://developer.mozilla.org/en-US/docs/Web/SVG/Element/style

You can even embed Javascript:
https://developer.mozilla.org/en-US/docs/Web/SVG/Element/script

Biggest problem is probably, that SVG files are not really sharable on social media.

@aixaves You might be able to achieve what you want with SVG and CSS. But these can only be viewed in (modern) browsers and you have to implement the toggling yourself with :hover or something like that.

My current hobby programming project got me into a math rabbit hole: I needed to calculate the shape of the intersection of the sRGB color-space with a Y-plane in the xyY space and couldn't find the answer online.

To solve it, I used symbolic math in #Python with #sympy for the first time. Was a lot of fun, despite some smaller hiccups.

The rendered notebook describing my solution is here: https://mapeper.github.io/sRGB_Y_section_in_xyY_space/ (⚠ comparatively large page)

So my math education wasn't useless after all! 🥳

@pleaseclap@urbanists.social @thomasw@toot.bldrweb.org @keyboardg@mastodon.social @eloquence@social.coop @Tibor@mastodon.social You can inspect the frontend JavaScript code quite easily and that shows, that the data does in fact go through his server.

@stof@ioc.exchange No, I mean CORS. Because the twitter API is on a different origin, a header is required to access it from a non-twitter domain in the browser. That header is missing. https://stackoverflow.com/a/35898961 You can access the twitter API from the browser by using a cors-proxy, that sets that header. (There are some available publicly, I think)

@Tibor@mastodon.social To me "All data stays in your browser" means, that there is no party that could get a hold on my data, even if it wanted to, so no 3rd party to trust. But there is, which I find misleading. If there would be a CORS header, one could use a "public client" and query the twitter API directly from the browser, truly keeping the data in the browser -but sadly the header is missing.

@Tibor@mastodon.social Isn't the claim "All data stays in your browser" kind of misleading? To me it looks like all the data and access tokens are passed through your server. Or am I missing something? The last time I checked, it wasn't possible to do this browser-only, because twitter was missing a simple CORS header 🙄.