marado

twtxt.net

No description provided.

Recent twts from marado

O que se tira da novela do dia, óbvio mas que ninguém estå a apontar: 1) não se usam equipamentos de dados para manter dados privados; 2) usar whatsapp para coisas profissionais, estatais e/ou governamentais é profundamente errado, deve ser criticado e não pode ser normalizado.

​ Read More
In-reply-to » (#ersasha) @lyse Quite a few people do. It's not even that hard, as you can fill them retroactively - there's even tutorials, like this one: https://dev.to/codesandtags/how-to-generate-pixel-art-in-your-github-activity-2e6k

@lyse@lyse.isobeef.org cheating or not, now I’m actively resisting writing a “git timeline painter tool”!

​ Read More

“There is no ternary testing operation in Go”, “the language’s designers had seen the operation used too often to create impenetrably complex expressions”.

​ Read More

Tomorrow is “Record Store Day”, a date that I have been feeling as yearly losing its purpose, now focused on the US and UK markets, markets, with a focus on commercialism. Today I read FLUR’s newsletter - a Portuguese record store that this year decided not to celebrate RSD, with an extraordinarily well articulated text on what is wrong with RSD (and the ‘vinyl indistry’) lately. A shame the text isn’t published somewhere.

​ Read More
In-reply-to » Did you know that "Heartbeat biometric identification is considered to be very accurate and at a similar level to fingerprints or retina recognition"? Food for thought.

@prologic@twtxt.net it is collected, we just don’t know exactly what, how, where, what for or how long. A slightly tangential but good read about fitbit’s data collection here.

​ Read More
In-reply-to » Did you know that "Heartbeat biometric identification is considered to be very accurate and at a similar level to fingerprints or retina recognition"? Food for thought.

@prologic@twtxt.net yeah, or any fitbit
 measuring the heartrate is easy and cheap, and depending on the accuracy level it can be as cheap as
 well, PPG, and any phone with a camera and flashlight can do it. But only yesterday I connected the dots on my mind regarding the sort (and potential uses) of the data being collected as soon as someone tries out a new band or watch.

​ Read More

Did you know that “Heartbeat biometric identification is considered to be very accurate and at a similar level to fingerprints or retina recognition”? Food for thought.

​ Read More

The old kindle story of digital burning of Fahrenheit 451 had already shown the perils of using e-book platforms, but the recent IA lawsuit has highlighted a graver danger: with one click, in an instant and without anyone knowing, a vendor can (and does) “update” a book. It is not that new issues of Agatha Christie’s books will be sold “moderized” it is that suddenly you cannot go to your library and find an old/original version. Chilling.

​ Read More
In-reply-to » 👋 Q: How do we feel about forking the Twtxt spec into what we love and use today in Yarn.social in yarnd, tt, jenny, twtr and other clients? đŸ€” Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).

I am against the original idea of forking twtxt.txt into yarn.txt unless I see any technical reason or feature that would justify breaking compatibility - so far I don’t see one. But I agree in principle with @darch@neotxt.dk that maybe we can add something on the metadata of the feeds enumerating the extensions we use or
 I don’t know, something that will allow any twtxt user to know how to deal with any ‘yarnisms’ in the content of our twts (even if the only one that comes to my mind as needing explanation is the thread hashes - how to interpret them).

​ Read More
In-reply-to » Given the continued hostility of jam6 and buckket over Yarn'a use of Twtxt (even after several years! đŸ˜±) I am continuing to face hard decisions.

@darch@twtxt.net case in point, I used to twtxt images before using yarn or markdown tp do it - and markdown isn’t making twts like this any less readible.

​ Read More
In-reply-to » Given the continued hostility of jam6 and buckket over Yarn'a use of Twtxt (even after several years! đŸ˜±) I am continuing to face hard decisions.

@prologic@twtxt.net I’d actually not replace it with newlines but with a space or something like that, so there’s nothing breaking (twtxt output parsers or whatever, expecting only one line per twt).

​ Read More
In-reply-to » Given the continued hostility of jam6 and buckket over Yarn'a use of Twtxt (even after several years! đŸ˜±) I am continuing to face hard decisions.

@prologic@twtxt.net What I take out from this log is that buckets client is truncating twts when seeing one of those characters you use for newline: a PR fixing that should suffice. As for the rest, I see twtxt as meant to be a readable format, and I think yarn is not messing with that. Is someone doesn’t like yarn’s writing style (or anything else on any other feed) they can simply not follow them. I see no reason at all for yarn to change its underlying format away from twtxt.

​ Read More
In-reply-to » 💡 Quick 'n Dirty prototype Yarn.social protocol/spec:

@prologic@twtxt.net I probably would not use an yarn.social client/app that didn’t deal with twtxt (text) feeds - both “follow” them and “publish” them. But I suppose that it is possible to have a bidirectional converter between that json format and twtxt.

​ Read More