(#vfxgqmq) @screem@twtxt.net I think there is value in cryptocurrencies as long as they have sufficient privacy protections. If you have someone’s Bitcoin or Ethereum address, you can see every transaction he’s ever been involved in. Not enough people know that.

The value is in being able to send a scarce resource to anyone on the planet, any time of the day, any day of the week, and have it received in 20 minutes. As long as privacy is preserved, I think it’s great.

It’s completely useless in the context of a chat service, though. The blockchain nonsense was part of the reason why I ditched Session, but it was mostly the Electron client.


#tawmrga

(#zdoe7hq) @screem@twtxt.net It is not a tough dilemma for me. A government has no right to perform mass surveillance on its citizens, treating everyone as if they were criminals. It starts with something we can all agree is reprehensible, and they say it stops there, but history tells us it never just stops there.

In addition, computers are really bad at their jobs. How many innocent people will be punished with a false positive? How many mothers will be punished for sending a photo of their newborn to the doctor?

I’m talking about punishment not only in the legal sense, but with the time, money, and worry associated with fighting legal punishment. Do you even trust your legal system enough that it will protect innocent people in these circumstances from having their lives ruined?

There are questions to be raised about the effectiveness of such a policy for its intended purpose but I’m running out of characters.

https://puri.sm/posts/internet-of-snitches/


#qfwasla

(#vfxgqmq) @prologic@twtxt.net It’s proof of stake, so you need to stake 15,000 units of their cryptocurrency $OXEN, worth $3118 US, to run a “full service node” and 3750 $OXEN ($779 US) to run a “shared node”. If I understand correctly, only “full service nodes” can route Session messages.

If you don’t have enough $OXEN, you can pool what you do have with other people and run a node that way.

TL;DR: Not very easy. To help route Session messages at all, you have to buy in to their cryptocurrency.

Sources:


#jus6b6a

i thought some amount of the death of hyper energy in my life was, like, being nearly thirty and not a teenager but i regret forgetting how much of that came from listening to hardstyle


#qowf7la

(#6cajjya) @brasshopper@twtxt.net Here’s what my thoughts are:

  • Someone needs to fiddle with the search engine’s codebase and improve it
  • Fix some performance issues and correctness
  • Add support for indexing mentions and feed authors of twts
  • Document how to use the query language really well
  • Provide results over both HTML and JSON

I think that would get us in a good place. Keeping the API as simple as hitting the search endpoint with ?q=... would suffice I think? 🤔


#f7n4d2a

(#hsouiwa) I guess the problem I really have, same with this whole Web3 Blockchain nonsense, is that we blur the lines between what is a centralised system, vs a decentralised system, vs a distributed system (sorry forked as we’re getting off topic…)

Does that make sense? 🤔 Even though it’s not too different from say you using my pod and trusting me, I feel its about making it as easy as possible to rely on your own infra if you so desired.

For example, I am quite sure you coudl run up your own Session node, hell even run up a Swarm of them (as they are called), but how easy is that to do? 🤔


#vfxgqmq

(#c4rokma) @eaplmx@twtxt.net Thanks bud 🤗

I’ve read the paper from Session and even played with it in the past 👌 I just wanted to point out something though, right there, not very far down:

Session utilises the decentralised Oxen Service Node Network to store
and route messages. This means that unlike P2P messaging applications
you can message Session users when they are offline.
This network consists of community operated nodes which are stationed
all over the world. Service nodes are organised into collections of small
co-operative groups called swarms. Swarms offer additional redundancy
and message delivery guarantees even if some service nodes become
unreachable. By using this network, Session doesn’t have a central point
of failure, and Session’s creators have no capacity to collect or store
personal information about people using the app.


#hsouiwa

(#6cajjya) @brasshopper@twtxt.net In which case I strongly believe a really good search engine and crawler is more suited to this, as it has the capability of self-discovering other feeds by crawling the entire space.

It works because of the inevitable “network effect”, for example: Say you were mentioned by a new person I’m interacting with for some reason or another, but you don’t follow them. Because you follow me, you get to know about this because of your connection with me.

A crawler can also discover this as well (and does).

Are you any good at Go btw? We have a search engine, but it needs a bit more work I think.


#duuosea

(#rfs6lza) The very fact that we continue to fucking store “Personal Identifiable Information” at all astounds me 😳 – Yes okay fine, there are commerce laws around “Know your customer” apparently, in which case, why da fuq do companies continue to store PII in the clear in databases and systems so easily hacked?! 🤦‍♂️ Encrypt it at rest FFS 🤣


#plc5n3q

(#6cajjya) In practise, almost no-one uses a Twtxt registry. I think it got bolted on to the spec as an “afterthought”, but required clients to add an implementation and use one or more registries, but which one? 😅 My personal opinion has always been to just rely on a search engine, of which there is one currently (needs some love), but hmmm not sure, this keeps coming up, regitries, but why? 🤔


#7wvpg6q

(#ybjlgha) @lyse@lyse.isobeef.org The specification just says:

Also note that a status may not contain any control characters.

Which is extremely vague, but U+0009 Horizontal Tabulation is in the C0 control code block

I’m sure 99% of twtxt parsers don’t treat additional tabs any differently. Even Buckket’s reference implementation includes additional tabs in the message. Although, in fairness, it doesn’t check for any for control codes.

Maybe we need a less ambiguous specification documenting how twtxt feeds are being written in the wild. Did you know that the comment convention is not a part of the original spec? I feel like it’s used everywhere, even among feeds that don’t use any Yarn extensions.


#ptugpdq

there isn’t a layer of abstraction that’s the “real” reasonable layer to know-all-the-way-down to. it’s entirely context-dependent. and given the context they actually work in, many Computer Men on the Internet would be better served by spending their time learning the higher and more human-interfacing layers better than bemoaning that the kids these days don’t appreciate SIMD or whatever


#7uno65q

this is not a function of the angle at which the photo was taken. no I do not really want a large vehicle still, I’m just saying I understand the arms race logic


#57utfhq

👋 Hey y’all Yarn.social and Twtxt users out there 🙇‍♂️ One of our sister projects we recently begun work on a few months ago this year (2022) is called Salty IM – Some of you may have heard of it, seen it, even played with it. If you haven’t do check it out! 🙏

I have written up an NL Net Funding Submission Proposal which you can find here (you will need to sign-in with either Github or your Gita login via git.mills.io).

I would appreciate any feedback, comments, criticisms as I would like to submit this before the Deadline of 1st Oct 2022. I an hopeful we can get a small funding amount to primarily build a great Mobile App experience for Salty Chat (the reference client) and place a number of (free) brokers around the globe for folks to use if they so wish 👌

Thank you! 🙏 #Salty.im #NLNet #Funding


#c4rokma

(#ybjlgha) I’m sorry, I didn’t explain this properly and that has led to a misunderstanding of my actual proposal. I was not intending for the title to be a special field unless the client explicitly understood my syndication format.

The original twtxt format specification gives no special meaning to the tab character, excluding the one that separates the timestamp from the text. I was under the impression that the tab character could appear in a twt so it would be interpreted as follows, replacing ␉ with a tab character.

2022-09-22T14:53:26-07:00␉Bringing Back a Useful Browser Feature With a Bookmarklet␉https://mckinley.cc/blog/20220922.html
#^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#|                        |
# ```- Timestamp             `- Message

Although, I just remembered that the tab character is technically a control code, so it shouldn’t be allowed.


#ujtlufa

they don’t advertise how unpleasant it is when you don’t brush out long hair for like two days and then you have to fix whatever happened inside your bun during that time


#vash2tq

my originally dibsed formulation was “Illuminaughty” which didn’t have search results at the time, but a friend gently guided me to the light. friends help friends workshop their bits


#kcjkyyq