Searching txt.sour.is

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

Snikket: Security notice: Snikket not affected by CVE-2024-3094
A security vulnerability was intentionally added to a widely used open-source
project known as ‘xz’. This project is packaged in many operating systems, and
a lot of software depends upon it. The vulnerability has been assigned the
identifier CVE-2024-3094.

Systems with the vulnerable package may allow an attacker to gain unauthorized
access to the system via SSH, if your system’s SSH server was linked to the
affected packages.

Thankfully, the vulne 
 ⌘ Read more

​ Read More

“Cloudflare loses 22% of its domains in Freenom .tk shutdown”
Reading about Freenom and .tk domains brings back memories: The first domains I registered were free .tk domains because I was too cheap to pay for domains as a high school student and also had no credit card to do so. ⌘ Read more

​ Read More

See Who Sent You a Link in Safari on iPhone, Mac, iPad
The latest versions of Safari for Mac, iPhone, and iPad, support a handy feature that allows you to quickly identify who sent you a particular link or webpage that you have open in the browser. This ‘sent from’ link feature is useful if you engage in a lot of exchanging of URLs between friends, coworkers, 
 Read More ⌘ Read more

​ Read More

Beau Lamarre-Condon: ‘Blood’ found near home linked to alleged killer cop
Police searching for the bodies of a TV star and his boyfriend Luke Davies and Jesse Baird have found blood near a home linked to alleged cop killer Beau Lamarre-Condon. ⌘ Read more

​ Read More

Could the ‘Middle Corridor’ offer a secure trade route that bypasses the Red Sea?
The so-called “Middle Corridor”, a trade route that would link Chinese and European markets through Central Asia and the Caucasus, was the focus of the 5th Balkans and Black Sea Forum held on Thursday 15th of February. Delegates at the conference promoted the Middle Corridor as an opportunity for a stable trade route amid escalating tensions 
 ⌘ Read more

​ Read More

IOL HAT: Enhancing Smart Sensor Integration for Raspberry Pi and Industrial Applications.
Pinetek Networks is set to launch the IOL HAT on Crowdsupply soon, a versatile solution designed for integrating industrial sensors into single-board computer-based projects, such as the Raspberry Pi. This device facilitates data exchange with smart SDCI sensors and actuators, adhering to the IEC 61131-9 standards, commonly referred to as IO-Link. There will be two [
 
 ⌘ Read more

​ Read More

Twtxt spec enhancement proposal thread đŸ§”

Adding attributes to individual twts similar to adding feed attributes in the heading comments.

https://git.mills.io/yarnsocial/go-lextwt/pulls/17

The basic use case would be for multilingual feeds where there is a default language and some twts will be written a different language.

As seen in the wild: https://eapl.mx/twtxt.txt

The attributes are formatted as [key=value]

They can show up in the twt anywhere it is not enclosed by another element such as codeblock or part of a markdown link.

​ Read More

Twtxt spec enhancement proposal thread đŸ§”

Adding attributes to individual twts similar to adding feed attributes in the heading comments.

https://git.mills.io/yarnsocial/go-lextwt/pulls/17

The basic use case would be for multilingual feeds where there is a default language and some twts will be written a different language.

As seen in the wild: https://eapl.mx/twtxt.txt

The attributes are formatted as [key=value]

They can show up in the twt anywhere it is not enclosed by another element such as codeblock or part of a markdown link.

​ Read More
In-reply-to » (#fytbg6a) What about using the blockquote format with > ?

@sorenpeter@darch.dk this makes sense as a quote twt that references a direct URL. If we go back to how it developed on twitter originally it was RT @nick: original text because it contained the original text the twitter algorithm would boost that text into trending.

i like the format (#hash) @<nick url> > "Quoted text"\nThen a comment
as it preserves the human read able. and has the hash for linking to the yarn. The comment part could be optional for just boosting the twt.

The only issue i think i would have would be that that yarn could then become a mess of repeated quotes. Unless the client knows to interpret them as multiple users have reposted/boosted the thread.

The format is also how iphone does reactions to SMS messages with +number liked: original SMS

​ Read More
In-reply-to » (#fytbg6a) What about using the blockquote format with > ?

@sorenpeter@darch.dk this makes sense as a quote twt that references a direct URL. If we go back to how it developed on twitter originally it was RT @nick: original text because it contained the original text the twitter algorithm would boost that text into trending.

i like the format (#hash) @<nick url> > "Quoted text"\nThen a comment
as it preserves the human read able. and has the hash for linking to the yarn. The comment part could be optional for just boosting the twt.

The only issue i think i would have would be that that yarn could then become a mess of repeated quotes. Unless the client knows to interpret them as multiple users have reposted/boosted the thread.

The format is also how iphone does reactions to SMS messages with +number liked: original SMS

​ Read More
In-reply-to » (#fytbg6a) What about using the blockquote format with > ?

I’m also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)

This will then make it possible to also “repost” stuff from other platforms/protocols.

The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.

​ Read More

Fix Step Count in Health App Updating Slowly on iPhone
If you’re the type of person who likes to keep track of their daily step count by using iPhone as a step counter, it is frustrating when the iPhone Health app step counter does not update as frequently as you’d like. Additionally, there are some challenges that are linked to specific step counts, and many 
 Read More ⌘ Read more

​ Read More

Seeing a video like this from Jeff Geerling about the MNT Reform Laptop, I am both amazed and puzzled. It’s probably a cool project to work on such an open hardware and source project as a hobby. And it’s great that there’s still the alternative to proprietary hardware. But has this any other use than just being a toy for people that have more than a thousand bucks to spend on such a thing? Especially given that it’s the opposite of powerful. Thinking about it more, the only thing that comes to mind are people wh 
 ⌘ Read more

​ Read More

Cost-efficient $39.90 Travel Router with Dual GbE Ports and Flexible Storage Options
Recently, SeeedStudio introduced the LinkStar-H28K-0408, a compact, pocket-sized router that offers advanced connectivity options. This device is equipped with Dual Gigabit Ethernet ports for high-speed internet access and includes a versatile USB Type-C port with Power Delivery support, enhancing its usability and convenience for various applications. Differing from the LinkS 
 ⌘ Read more

​ Read More

How to Delete a Threads Account Without Leaving Instagram
When Threads debuted from Meta (FaceBook), it was intricately linked to Instagram, and initially when you went to delete or deactivate a Threads account, it had the unfortunate side effect of also deleting the related Instagram account. But that is no longer the case. Now you can choose to delete a Threads account without impacting 
 [Read More](https://osxdaily.com/2023/12/31/how-to-delete-a-threads-account-without-le 
 ⌘ Read more

​ Read More

Nintendo ĐżĐŸŃ‚Ń€Đ”Đ±ĐŸĐČала ŃƒĐŽĐ°Đ»ĐžŃ‚ŃŒ ĐœĐ”ĐŸŃ„ĐžŃ†ĐžĐ°Đ»ŃŒĐœŃ‹Đč ПК-ĐżĐŸŃ€Ń‚ The Legend of Zelda: Link‘s Awakening DX
Đ•ĐłĐŸ ŃŃ‚Ń€Đ°ĐœĐžŃ†Đ° ĐœĐ° itch.io ужД ĐœĐ”ĐŽĐŸŃŃ‚ŃƒĐżĐœĐ°.

Image

⌘ Read more

​ Read More

It is a pleasure to work with the help system of Borland’s Turbo C++ 3.0 on DOS. The descriptions are clear and concise. There are short and simple examples. Pretty much every help page is cross-refenced and those links can be clicked.

​ Read More

“HTML compression on popular websites”
Danny van Kooten did an interesting experiment and checked the top 10 thousand websites whether they are compressing their HTML. About 8% of them do not apply any kind of compression, resulting in many terabytes of unnecessary transmitted data, not helping to save energy. ⌘ Read more

​ Read More

When Apple built MacOS
 for Solaris and HP-UX. In 1994.
Listen now (16 mins) | Back in 1994, Apple released the Macintosh Application Environment for UNIX. And it was kind of amazing. Read the full article (with links to documentation and screenshots) at The Lunduke Journal: https://lunduke.locals.com/post/4812552/remember-when-apple-built-a-mac-os-running-on-top-of-solaris-and-hp-ux-seriously-it-happened ⌘ Read more

​ Read More

Isode: M-Link 19.4 Limited Release
M-Link 19.4 provides a very significant update and in particular provides the M-Link User Server product. It also provides M-Link MU Server, M-Link MU Gateway and M-Link Edge.   It does not provide M-Link IRC Gateway, which remains M-Link 17.0 only.

M-Link 19.4 Limited Release is provided ahead of the full M-Link 19.4 release. M-Link 19.4 Limited Release is fully supported by Isode for production deployment. There is one significant difference with a standard Isod 
 ⌘ Read more

​ Read More

How to Download a Mac App from Github?
A ton of open source software is available on Github, and many Mac applications are often available to download for free through the Github service as well. And if you read websites like this one and many others in the Apple and tech world, you’ll often find links to neat software projects on Github. One 
 Read More ⌘ Read more

​ Read More

How to Download a Mac App from Github?
A ton of open source software is available on Github, and many Mac applications are often available to download for free through the Github service as well. And if you read websites like this one and many others in the Apple and tech world, you’ll often find links to neat software projects on Github. One 
 Read More ⌘ Read more

​ Read More

Today I’ve been working on something that I’ve really missed, and that is clickable links in the desktop client, finally figured out how they work. So now you can click on them and it opens the browser. I need to clean it up before I commit it.

Image

​ Read More

No hello
Thanks to Tim HĂ„rek Andreassen, I finally have a link I can send my coworkers whenever they send me a “Hi”, “Do you have some time?”, “Can I call you?” instead of asking their question right away or even just mentioning the topic. And there’s also a German version, great! ⌘ Read more

​ Read More

If you haven’t already noticed (though why would you?), I have finally merged my homepage into my blog. Why? Well, I believe it doesn’t make much sense to keep them separate. My homepage had only a few pages, and elements such as my “About Me” page and collections of things I use are well-maintained on my blog as well. Some pages were also deleted during this process, but I made an effort to preserve links where possible. ⌘ Read more

​ Read More

I need to do a big rewrite on how the yarn desktop client handles the status widgets, this is because I want links and such, and to do that I have to rewrite the status message code, it takes a bit if time to do it, but I kinda know what to do - I just need to dive in and get it done. Been thinking about it for a while, I think it’s time to get started on it. Also makes the code much cleaner then what it is now.

​ Read More

Isode: Icon-PEP 2.0 – New Capabilities
Icon-PEP is used to enable the use of IP applications over HF networks. Using STANAG 5066 Link Layer as an interface.

Image

Listed below are the changes brought in with 2.0.

Web Management

A web interface is provided which includes:

  • Full configuration of Icon-PEP
  • TLS (HTTPS) access and configuration including bootstrap with self signed certificate and ide 
 ⌘ Read more

​ Read More

Ditching Pocket Premium: Streamline link saving with Telegram
For the past two years, I’ve been using Pocket to save links that I want to revisit later. However, as my yearly subscription is about to expire, I’ve started thinking about finding a free alternative that offers the features I actually use, without paying for unnecessary extras. ⌘ Read more

​ Read More

This whole twitter thing got me motivated to code on the yarn desktop client.
Currently working on adding support for links in the post, so that you can open and view the links that are in the statuses.

​ Read More

Ditching Pocket Premium: Streamline link saving with Telegram
For the past two years, I’ve been using Pocket to save links that I want to revisit later. However, as my yearly subscription is about to expire, I’ve started thinking about finding a free alternative that offers the features I actually use, without paying for unnecessary extras. ⌘ Read more

​ Read More

An official FBI document dated January 2021, obtained by the American association “Property of People” through the Freedom of Information Act.

This document summarizes the possibilities for legal access to data from nine instant messaging services: iMessage, Line, Signal, Telegram, Threema, Viber, WeChat, WhatsApp and Wickr. For each software, different judicial methods are explored, such as subpoena, search warrant, active collection of communications metadata (“Pen Register”) or connection data retention law (“18 USC§2703”). Here, in essence, is the information the FBI says it can retrieve:

  • Apple iMessage: basic subscriber data; in the case of an iPhone user, investigators may be able to get their hands on message content if the user uses iCloud to synchronize iMessage messages or to back up data on their phone.

  • Line: account data (image, username, e-mail address, phone number, Line ID, creation date, usage data, etc.); if the user has not activated end-to-end encryption, investigators can retrieve the texts of exchanges over a seven-day period, but not other data (audio, video, images, location).

  • Signal: date and time of account creation and date of last connection.

  • Telegram: IP address and phone number for investigations into confirmed terrorists, otherwise nothing.

  • Threema: cryptographic fingerprint of phone number and e-mail address, push service tokens if used, public key, account creation date, last connection date.

  • Viber: account data and IP address used to create the account; investigators can also access message history (date, time, source, destination).

  • WeChat: basic data such as name, phone number, e-mail and IP address, but only for non-Chinese users.

  • WhatsApp: the targeted person’s basic data, address book and contacts who have the targeted person in their address book; it is possible to collect message metadata in real time (“Pen Register”); message content can be retrieved via iCloud backups.

  • Wickr: Date and time of account creation, types of terminal on which the application is installed, date of last connection, number of messages exchanged, external identifiers associated with the account (e-mail addresses, telephone numbers), avatar image, data linked to adding or deleting.

TL;DR Signal is the messaging system that provides the least information to investigators.

​ Read More

An official FBI document dated January 2021, obtained by the American association “Property of People” through the Freedom of Information Act.

This document summarizes the possibilities for legal access to data from nine instant messaging services: iMessage, Line, Signal, Telegram, Threema, Viber, WeChat, WhatsApp and Wickr. For each software, different judicial methods are explored, such as subpoena, search warrant, active collection of communications metadata (“Pen Register”) or connection data retention law (“18 USC§2703”). Here, in essence, is the information the FBI says it can retrieve:

  • Apple iMessage: basic subscriber data; in the case of an iPhone user, investigators may be able to get their hands on message content if the user uses iCloud to synchronize iMessage messages or to back up data on their phone.

  • Line: account data (image, username, e-mail address, phone number, Line ID, creation date, usage data, etc.); if the user has not activated end-to-end encryption, investigators can retrieve the texts of exchanges over a seven-day period, but not other data (audio, video, images, location).

  • Signal: date and time of account creation and date of last connection.

  • Telegram: IP address and phone number for investigations into confirmed terrorists, otherwise nothing.

  • Threema: cryptographic fingerprint of phone number and e-mail address, push service tokens if used, public key, account creation date, last connection date.

  • Viber: account data and IP address used to create the account; investigators can also access message history (date, time, source, destination).

  • WeChat: basic data such as name, phone number, e-mail and IP address, but only for non-Chinese users.

  • WhatsApp: the targeted person’s basic data, address book and contacts who have the targeted person in their address book; it is possible to collect message metadata in real time (“Pen Register”); message content can be retrieved via iCloud backups.

  • Wickr: Date and time of account creation, types of terminal on which the application is installed, date of last connection, number of messages exchanged, external identifiers associated with the account (e-mail addresses, telephone numbers), avatar image, data linked to adding or deleting.

TL;DR Signal is the messaging system that provides the least information to investigators.

​ Read More

Isode: M-Link 19.4 Limited Release
M-Link 19.4 provides a very significant update and in particular provides the M-Link User Server product. It also provides M-Link MU Server, M-Link MU Gateway and M-Link Edge.   It does not provide M-Link IRC Gateway, which remains M-Link 17.0 only.

M-Link 19.4 Limited Release is provided ahead of the full M-Link 19.4 release. M-Link 19.4 Limited Release is fully supported by Isode for production deployment. There is one significant difference with a standard Isod 
 ⌘ Read more

​ Read More

I deleted my Twitter account a long time ago, but sometimes I still used Nitter to search Twitter or we linked tweets. I decided to stop that and removed Nitter from my home server and added “twitter.com” to the deny list at NextDNS. There are too many reasons to list here. ⌘ Read more

​ Read More
In-reply-to » Working on showing attached images in the desktop client, it worked on first try. Now I need to fix the scale and alignment - but cool that it works already!

@prologic@twtxt.net They have some markdown support that you can use, but I have not looked into that yet, I might check on that for clickable links in label.
I now just get all the attached links in each post, check for direct links to images, download them and show them as in the screenshot.

​ Read More

“the secret list of websites”
Chris Coyier wrote a post mentioning a Washington Post article that analyzed which websites Google used to train its AI model. And it seems that both my blog and my website (I think I should merge them one day) are used. ⌘ Read more

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

I’m not super a fan of using json. I feel we could still use text as the medium. Maybe a modified version to fix any weakness.

What if instead of signing each twt individually we generated a merkle tree using the twt hashes? Then a signature of the root hash. This would ensure the full stream of twts are intact with a minimal overhead. With the added bonus of helping clients identify missing twts when syncing/gossiping.

Have two endpoints. One as the webfinger to link profile details and avatar like you posted. And the signature for the merkleroot twt. And the other a pageable stream of twts. Or individual twts/merkle branch to incrementally access twt feeds.

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

I’m not super a fan of using json. I feel we could still use text as the medium. Maybe a modified version to fix any weakness.

What if instead of signing each twt individually we generated a merkle tree using the twt hashes? Then a signature of the root hash. This would ensure the full stream of twts are intact with a minimal overhead. With the added bonus of helping clients identify missing twts when syncing/gossiping.

Have two endpoints. One as the webfinger to link profile details and avatar like you posted. And the signature for the merkleroot twt. And the other a pageable stream of twts. Or individual twts/merkle branch to incrementally access twt feeds.

​ Read More

I will release the sourcecode for the desktop client tonight. I will put it on github (sorry to anyone who prefer other places), but the reason is that I do not want my own git to be open for public. So I’ll put it on github where I have all my other public projects. I have to write the readme, then add some info on the login page (link to source etc), then it’s ready to release with the current features. I then hope others will give it a try and use it if they want :) I also have many other features I need to implement, but all the main features that makes it usable has been implemented, so I’m very pleased with it (And I use it all the time now).

​ Read More

** week notes **
Some things of note, links mostly:

First and foremost, I found a suitable pinboard replacement in link hut! Shout outs to my buddy Bruno for the tip.

Here’s a bookmarklet I wrote to make it a bit more ergonomic for how I like to roll,

 javascript
javascript:(<span class="hljs-function"><span class="hljs-keyword">function</span> (<span class="hljs-params"></span>) </span>{
  <span class="hljs-keyword">const</span> tags = prompt(<span class="hljs-string">'A space separated list of tags.' ... ⌘ [Read more](https://eli.li/2023/03/31/week-notes)

​ Read More
In-reply-to » Posting from c++, fltk GUI.

I have cleaned up the timeline a bit, I like this much more.
I use the markdown text now, instead of the ‘text’ field in the json file, looks much cleaner.
I can work with this. One thing that I want to sort out next is the way the nicknames and url is shown.
Also links in posts should be clickable - not sure if the current labels support that, but I’ll try and figure it out somehow. Anyways - latest screenshot is attached here.. :)

Image

​ Read More

RT by @mind_booster: No Ăąmbito do 20Âș aniversĂĄrio da Convenção de Salvaguarda do PatrimĂłnio Cultural Imaterial, Ă© amanhĂŁ lançada a campanha Wiki Loves Living Heritage. Vejam como assistir ao lançamento no link:
https://meta.wikimedia.org/wiki/Event:Wiki_Loves_Living_Heritage/Wiki_Loves_Living_Heritage_launch_event #Patrimonioimaterial #Portugal @cultura_pt

No Ăąmbito do 20Âș aniversĂĄrio da Convenção de Salvaguarda do PatrimĂłnio Cultural Imaterial, Ă© amanhĂŁ lançada a campanha Wiki Loves Living Heritage. Vejam 
 ⌘ Read more

​ Read More

mox Mail Server
I currently use Purelymail for email. It’s very cheap and does everything I need (“purely email”). I’m also happy that I’m free of all the headaches of having a good IP reputation and setting everything up so that my mail doesn’t end up in junk folders. ⌘ Read more

​ Read More
In-reply-to » @lyse flawed is the right word, no harsh at all. Good reading, and thanks for supporting the possibility of convincing @prologic to switch to a database! :-D :-P

Like, check it out. That link to DRY? It doesn’t render as a link in the webapp. However, it does render as a link, and works fine, in Goryon. I’ve seen before that Markdown tables render fine in Goryon but not in the webapp. They ought to behave as similarly as possible, right? So just in this small interaction there are three discrepancies between how the mobile app and webapp render Markdown.

​ Read More

Here is how platforms die: first, they are good to their users; then they abuse their users to make things better for their business customers; finally, they abuse those business customers to claw back all the value for themselves. Then, they die. Pluralistic: Tiktok’s enshittification (21 Jan 2023) – Pluralistic: Daily links from Cory Doctorow

​ Read More

H3: Instead of C3
[Updated with correct Gemlog link.]

A version of this was posted on on 2023-01-06 but I thought it might
also fit here. Go to my gemlog for somewhat more personal takes and
see what I publish first. IPv6 only!

gemini://gem.hack.org/mc/log/

As long-time readers know I have participated in the Chaos
Communication Congress (C3) in Germany every year since 2008.

Since C3 was cancelled this year I thought I’d arrange a very small
conference of my own. I would at least try to gather some friends and
acquaintances 
 ⌘ Read more

​ Read More

@prologic@twtxt.net @movq@www.uninformativ.de this is the default behavior of pass on my machine:

Image

I add a new password entry named example and then type pass example. The password I chose, “test”, is displayed in cleartext. This is very bad default behavior. I don’t know about the other clis you both mentioned but I’ll check them out.

The browser plugin browserpass does the same kind of thing, though I have already removed it and I’m not going to reinstall it to make a movie. Next to each credential there’s an icon to copy the username to the clipboard, an icon to copy the password to the clipboard, and then an icon to view details, which shows you everything, including the password, in cleartext. The screencap in the Chrome store is out of date; it doesn’t show the offending link to show all details, which I know is there because I literally installed it today and played with it.

​ Read More

I posted about GoToSocial, but another Mastodon-alternative and Fediverse software, Takahē, seems to make fast progress and has some unique features like support for multiple domains or multiple identities per user. I haven’t tried running it yet, but it looks promising! ⌘ Read more

​ Read More
In-reply-to » Trying to wrap my head around webfinger..

so in effect it would look something like this:

---
subject: acct:me@sour.is
aliases:
  - salty:me@sour.is
  - yarn:xuu@ev.sour.is
  - status:xuu@chaos.social
  - mailto:me@sour.is
---
subject: salty:me@sour.is
aliases:
  - acct:me@sour.is
links:
  - rel:    self
    type:   application/json+salty
    href:   https://ev.sour.is/inbox/01GAEMKXYJ4857JQP1MJGD61Z5
    properties:
        "http://salty.im/ns/nick":    xuu
        "http://salty.im/ns/display": Jon Lundy
        "http://salty.im/ns/pubkey":     kex140fwaena9t0mrgnjeare5zuknmmvl0vc7agqy5yr938vusxfh9ys34vd2p
---
subject: yarn:xuu@ev.sour.is
links:
  - rel: https://txt.sour.is/user/xuu
    properties:
        "https://sour.is/rel/redirect": https://txt.sour.is/.well-known/webfinger?resource=acct%3Axuu%40txt.sour.is
---    
subject: status:xuu@chaos.social
links:
   - rel: http://joinmastodon.org#xuu%40chaos.social
     properties:
        "https://sour.is/rel/redirect": https://chaos.social/.well-known/webfinger?resource=acct%3Axuu%40chaos.social
---
subject: mailto:me@sour.is
...

​ Read More
In-reply-to » Trying to wrap my head around webfinger..

so in effect it would look something like this:

---
subject: acct:me@sour.is
aliases:
  - salty:me@sour.is
  - yarn:xuu@ev.sour.is
  - status:xuu@chaos.social
  - mailto:me@sour.is
---
subject: salty:me@sour.is
aliases:
  - acct:me@sour.is
links:
  - rel:    self
    type:   application/json+salty
    href:   https://ev.sour.is/inbox/01GAEMKXYJ4857JQP1MJGD61Z5
    properties:
        "http://salty.im/ns/nick":    xuu
        "http://salty.im/ns/display": Jon Lundy
        "http://salty.im/ns/pubkey":     kex140fwaena9t0mrgnjeare5zuknmmvl0vc7agqy5yr938vusxfh9ys34vd2p
---
subject: yarn:xuu@ev.sour.is
links:
  - rel: https://txt.sour.is/user/xuu
    properties:
        "https://sour.is/rel/redirect": https://txt.sour.is/.well-known/webfinger?resource=acct%3Axuu%40txt.sour.is
---    
subject: status:xuu@chaos.social
links:
   - rel: http://joinmastodon.org#xuu%40chaos.social
     properties:
        "https://sour.is/rel/redirect": https://chaos.social/.well-known/webfinger?resource=acct%3Axuu%40chaos.social
---
subject: mailto:me@sour.is
...

​ Read More
In-reply-to » Trying to wrap my head around webfinger..

@xuu@txt.sour.is that doesn’t seem to fit the spirit of the spec, at least by my read (I could be wrong obv). The example on Wikipedia’s webfinger page,

{
	"subject": "acct:bob@example.com",
	"aliases": [
		"https://www.example.com/~bob/"
	],
	"properties": {
		"http://example.com/ns/role": "employee"
	},
	"links": [{
			"rel": "http://webfinger.example/rel/profile-page",
			"href": "https://www.example.com/~bob/"
		},
		{
			"rel": "http://webfinger.example/rel/businesscard",
			"href": "https://www.example.com/~bob/bob.vcf"
		}
	]
}

and then the comparison with how mastodon uses webfinger,

{
    "subject": "acct:Mastodon@mastodon.social",
    "aliases": [
        "https://mastodon.social/@Mastodon",
        "https://mastodon.social/users/Mastodon"
    ],
    "links": [
        {
            "rel": "http://webfinger.net/rel/profile-page",
            "type": "text/html",
            "href": "https://mastodon.social/@Mastodon"
        },
        {
            "rel": "self",
            "type": "application/activity+json",
            "href": "https://mastodon.social/users/Mastodon"
        },
        {
            "rel": "http://ostatus.org/schema/1.0/subscribe",
            "template": "https://mastodon.social/authorize_interaction?uri={uri}"
        }
    ]
}

suggests to me you want to leave the subject/acct bit as is (don’t add prefixes) and put extra information you care to include in the links section, where you’re free to define the rel URIs however you see fit. The notion here is that webfinger is offering a mapping from an account name to additional information about that account, so if anything you’d use a "subject": "acct:SALTY ACCOUNT_REPRESENTATION" line in the JSON to achieve what you’re saying if you don’t want to do that via links.

​ Read More
In-reply-to » Trying to wrap my head around webfinger..

@prologic@twtxt.net That was exactly my thought at first too. but what do we put as the rel for salty account? since it is decentralized we dont have a set URL for machines to key off. so for example take the standard response from okta:

# http GET https://example.okta.com/.well-known/webfinger  resource==acct:bob
{
    "links": [
        {
            "href": "https://example.okta.com/sso/idps/OKTA?login_hint=bob#",
            "properties": {
                "okta:idp:type": "OKTA"
            },
            "rel": "http://openid.net/specs/connect/1.0/issuer",
            "titles": {
                "und": "example"
            }
        }
    ],
    "subject": "acct:bob"
}

It gives one link that follows the OpenID login. So the details are specific to the subject acct:bob.

Mastodons response:

{
  "subject": "acct:xuu@chaos.social",
  "aliases": [
    "https://chaos.social/@xuu",
    "https://chaos.social/users/xuu"
  ],
  "links": [
    {
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://chaos.social/@xuu"
    },
    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://chaos.social/users/xuu"
    },
    {
      "rel": "http://ostatus.org/schema/1.0/subscribe"
    }
  ]
}

it supplies a profile page and a self which are both specific to that account.

​ Read More
In-reply-to » Trying to wrap my head around webfinger..

@prologic@twtxt.net That was exactly my thought at first too. but what do we put as the rel for salty account? since it is decentralized we dont have a set URL for machines to key off. so for example take the standard response from okta:

# http GET https://example.okta.com/.well-known/webfinger  resource==acct:bob
{
    "links": [
        {
            "href": "https://example.okta.com/sso/idps/OKTA?login_hint=bob#",
            "properties": {
                "okta:idp:type": "OKTA"
            },
            "rel": "http://openid.net/specs/connect/1.0/issuer",
            "titles": {
                "und": "example"
            }
        }
    ],
    "subject": "acct:bob"
}

It gives one link that follows the OpenID login. So the details are specific to the subject acct:bob.

Mastodons response:

{
  "subject": "acct:xuu@chaos.social",
  "aliases": [
    "https://chaos.social/@xuu",
    "https://chaos.social/users/xuu"
  ],
  "links": [
    {
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://chaos.social/@xuu"
    },
    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://chaos.social/users/xuu"
    },
    {
      "rel": "http://ostatus.org/schema/1.0/subscribe"
    }
  ]
}

it supplies a profile page and a self which are both specific to that account.

​ Read More

Trying to wrap my head around webfinger..

my first thoughts about it were that a subject of acct:me@sour.is would have a listing of rel’s for the different accounts that are related to me (ie. yarn, salty, twitter, mastodon, etc
)

but maybe my thinking is at the wrong level.. that each of those accounts would be on a subject level and the rels are describing different aspects of that account. so i would have salty:acct:xuu@sour.is, twitter:acct:xuu, mastodon:acct:xuu@chaos.social, yarn:acct:xuu@ev.sour.is and then i could have a main acct:me@sour.is that links them together as aliases.

I found okta will do something similar with its accounts to show as okta:acct:user@domain so maybe I am on to something?

​ Read More

Trying to wrap my head around webfinger..

my first thoughts about it were that a subject of acct:me@sour.is would have a listing of rel’s for the different accounts that are related to me (ie. yarn, salty, twitter, mastodon, etc
)

but maybe my thinking is at the wrong level.. that each of those accounts would be on a subject level and the rels are describing different aspects of that account. so i would have salty:acct:xuu@sour.is, twitter:acct:xuu, mastodon:acct:xuu@chaos.social, yarn:acct:xuu@ev.sour.is and then i could have a main acct:me@sour.is that links them together as aliases.

I found okta will do something similar with its accounts to show as okta:acct:user@domain so maybe I am on to something?

​ Read More

Anyone know what this might be about?

[1134036.271114] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x880000 action 0x6 frozen
[1134036.271478] ata1: SError: { 10B8B LinkSeq }
[1134036.271829] ata1.00: failed command: WRITE FPDMA QUEUED
[1134036.272182] ata1.00: cmd 61/20:10:e0:75:6e/00:00:11:00:00/40 tag 2 ncq 16384 out
                          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[1134036.272895] ata1.00: status: { DRDY }
[1134036.273245] ata1: hard resetting link
[1134037.447033] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1134038.747174] ata1.00: configured for UDMA/133
[1134038.747179] ata1.00: device reported invalid CHS sector 0
[1134038.747185] ata1: EH complete

​ Read More

RT by @mind_booster: JĂĄ estĂĄ publicada a lista de autores portugueses que entram hoje em #DomĂ­nioPĂșblico. Podem consultar aqui https://blog.wikimedia.pt/2023/01/01/dia-do-dominio-publico-2022-2/
No dia 6 de janeiro, hĂĄ um evento organizado pela @wikimediapt Biblioteca Nacional e @ANSOL Link no mesmo site. Se puderem, partilhem!
href=”https://txt.sour.is/search?q=%23PublicDomain
”>#PublicDomain**
JĂĄ estĂĄ publicada a lista de autores portugueses que entram hoje em #DomĂ­nioPĂșblico. Podem consultar aqui [blog.wikimedi 
 ⌘ Read more

​ Read More

“AirTags Expose Dodgy Postal Industry”
Last year, YouTuber MegaLag tried to send several AirTag-ged packages from Germany to North Korea with DHL. But instead of arriving there, they were either misrouted to South Korea or ended up in China. In a new video, he further researches the reasons and also takes a look at DHL’s sorting center in Frankfurt at their invitation. Very interesting! ⌘ Read more

​ Read More

Bunny AI
Bunny.net joined the AI hype and created “Bunny AI” (docs), AI images created on the edge. I tried it out, because it’s currently free during the preview, but somehow I don’t find the generated images aesthetic or I’m just to stupid to write better prompts. I guess the Bunny developers also need some distraction from time to time, because they are working hard on S3 support for Bunny Storage for years already. 🐰 ⌘ Read more

​ Read More

Forgejo
A few weeks ago, it came to light that Gitea has been owned by a for-profit Gitea Ltd. for several months. The lack of transparency has disturbed the trust of many contributors and users. That’s why Codeberg (a German based non-profit association - disclaimer: I am a member of the association) has now started a soft fork: Forgejo. ⌘ Read more

​ Read More

DeepL Write
I’m a big fan of DeepL for translations. Before trying to write more blog posts directly in English to improve my skills, I wrote many blog posts in German and then translated them. The texts were probably better than my non-native English. ⌘ Read more

​ Read More

“Bloggers, Dump Your Twitter Card Tags”
It’s crazy to think how much bandwidth is being used by metadata tags. Every company wants to invent it’s own new system. Wouter Groeneveld gives a brief overview and recommends getting rid of them (for the most part). I agree with him completely. The only one of these systems that my blog supports is Microformats, which is quite popular among the IndieWeb community. ⌘ Read more

​ Read More

Android vs iOS: Which spies on you more?
Watch now (25 min) | (This is a classic video originally produced back in 2018. It is presented here exactly as it originally was – including original ad spots. Many of the details discussed (links, stats, etc.) may have changed in the years that followed.) Which mobile operating system spies on you the most? Android or iOS? In other words: Does a Google-powered Android
 ⌘ Read more

​ Read More
In-reply-to » Atom vs. RSS: https://mckinley.cc/blog/20221109.html

@mckinley@twtxt.net Thank you! I didn’t even know about signing and encrypting XML documents. Right, RSS is a little bit messy.

Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between <id> and <link>. I always want my URL also to be my ID, so I have to duplicate that – unnecessarily in my opinion.

Also, never found a good explanation why I should add <link rel="self" 
 /> to my feeds. I just do, but I don’t understand why. The W3C Feed Validation Service says:

[
] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.

This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn’t make sense to me.

Also, I just noticed that I reference the http://purl.org/rss/1.0/modules/syndication/ namespace, but don’t use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I’m doing.

Your article made me reread the Atom spec and I found out, that I can omit the <author> in the <entry> when I specify a global <author> at <feed> level. Awesome! Will do that as well and thus reduce the feed size.

​ Read More

I was inclined to let this go so as not to stir anything up, but after some additional thought I’ve decided to call it out. This twt:

Image

is exactly the kind of ad hominem garbage I came to expect from Twitterℱ, and I’m disappointed to see it replicated here. Rummaging through someone’s background trying to find a “gotcha” argument to take credibility away from what a person is saying, instead of engaging the ideas directly, is what trolls and bad faith actors do. That’s what the twt above does (falsely, I might add–what’s being claimed is untrue).

If you take issue with something I’ve said, you can mute me, unfollow me, ignore me, use TamperMonkey to turn all my twts into gibberish, engage the ideas directly, etc etc etc. There are plenty of options to make what I said go away. Reading through my links, reading about my organization’s CEO’s background, and trying to use that against me somehow (after misinterpreting it no less)? Besides being unacceptable in a rational discussion, and besides being completely ineffective in stopping me from expressing whatever it is you didn’t like, it’s creepy. Don’t do that.

​ Read More