Searching We Love Privacy Club

Twts matching #space
Sort by: Newest, Oldest, Most Relevant

asbjorn: “Morer mig over oprettelsesdato
”
Morer mig over oprettelsesdatoer pÄ listen over danske Mastodon instanser her: https://fedi.dk/Danske%20instanser.html

Man kan meget tydeligt se de to Elon-bÞlger i hhv. forÄret og efterÄret i Är.

NĂ„rh ja, og sĂ„ er der en eller anden lille tosset server der har vĂŠret her i flere Ă„r fĂžr da. ⌘ Read more

​ Read More

asbjorn: “Jeg har sat Nþrrebro.space til
”
Jeg har sat Nþrrebro.space til at bruge expressional.social’s mastodon relay.

Det kommer til at pĂ„virke vores fĂždererede feed (aka “Forenede tidslinje”), ved at flette med den tilsvarende feed fra nogle andre danske servere.

Tager gerne imod feedback, ifht. om hvorvidt vi bĂžr relaye - og med hvem.

Sig ogsĂ„ til hvis du lĂŠgger mĂŠrke til en forskel i den forenede tidslinje. Jeg gĂŠtter pĂ„ at det ikke kommer til at gĂžre sĂ„ meget. ⌘ Read more

​ Read More

asbjorn: “Der var en gang hvor jeg sendt
”
Der var en gang hvor jeg sendte velkomst-trut til alle nye brugere pÄ NÞrrebro.space - men de sidste par uger har der vÊret sÄ mange nye, at jeg ikke har kunnet fÞlge med

SĂ„ lad den her trut vĂŠre en hjertelig velkomst til alle, der for nyligt har fundet vej til fĂždiverset.

Vi er glade for, at i er her! đŸ€— ⌘ Read more

​ Read More

asbjorn: “Jeg synes at journalister og p
”
Jeg synes at journalister og politikere er sÊrligt slemme til det. Men det lyder ogsÄ fra alle mulige andre samfundslag, bÄde i privat og offentlig diskurs.

Jeg har da ogsĂ„ flere gange taget mig selv i at bruge vendingen “en russisk hacker” nĂ„r jeg egentlig mener “en fremmed cyberkriminel”.

Kan ikke helt finde ud af om det er geopolitisk retvisende, om det er bevidst anti-þstlig propaganda, eller om det bare er almindelig folkelig xenofobi
 ⌘ Read more

​ Read More

asbjorn: “Lad os lige fĂ„ afklaret at tyv
”
Lad os lige fÄ afklaret at tyveri ikke er det samme som efterligning.

Man kan ikke “stjĂŠle” en idĂ©, ligesom man ikke kan “stjĂŠle” en tanke eller en drĂžm.

Delte drĂžmme er bedre. Afskaf idĂ©grĂ„dighed i dag! ⌘ Read more

​ Read More

** uxn laboratory **
As I look to assembly nights 2, and think of trying my own take on it, I wanna have a cozy space ready to play with uxn.

The setup I’ve landed on is sort of inspired by plan9port.

Prepare the way
  • in home directory, create au directory
  • inu clone uxn and build it
  • add~/u/uxn/ to your path as $UXN
  • add$UXN/bin to your path
  • moving forward we’ll put any and all*.rom files into 
 ⌘ Read more

​ Read More

Launching GitHub Community: Powered by GitHub Discussions
Today, we’re launching GitHub Community, which brings together GitHub Community Forum, GitHub Education Forum, and product feedback into a free, in-product, single space for all user-to-user interactions. ⌘ Read more

​ Read More
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@movq@www.uninformativ.de @prologic@twtxt.net I just reread the spec and it seems to be even a bit outdated regarding machine-parsable conversation grouping. We long dropped the need to specify a whole hash tag with URL (#<hash url>), the simplified version without the URL (#hash) is enough.

The hash tag extension specification is kind of missing the same. However, I’m not sure if that short form is considered supported in general (as opposed to be a special case for subjects only) by the majority of the twtxt/yarn community.

Now the question arises, in order to keep things simple, should we even only allow the simplified twt hash tag for subjects and forbid the long version? This would also save quite a bit of space. The URL is probably not shown anyways in most clients. And if so, clients might rewrite URLs to their own instances. On the other hand, there’s technically nothing wrong with the long version in current parser implementations. And deprecating stuff without very good reason isn’t cool.

​ Read More