Sir Alecks Gates

https://activitypub.agates.io/users/agates

Podcasting 2.0 consultant
Master of the protocols
Knight of Podcasting 2.0

INTJ-A

#Wisconsin

Essays: Observations with Alecks (npub1cxd…p4kj)
XMPP: xmpp:[email protected]
$XMR: 84wFU6XzrCGYWE2rEcG4ZGP5mbkvfmx74Kmh6ctEso884wHxd5uQ3h9YW9tU4iT2Rvfxk4Z7mXCBATzFwn2b6JjUG1GJeL8
GitHub: https://github.com/agates
Lightning: [email protected]

Public Key

npub1x70fkrjzd4ujwdhdjp4da8d9qd45x9cynm66eeye48fdfjkx09fs6n4uc9

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsr085mpepx67f8xmkeq6k7nkjsx66rzuzfaadvujv6n5k5etr8j5cprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt6xtyy0

Publishing to

relay.momostr.pink

Author Public Key

npub1x70fkrjzd4ujwdhdjp4da8d9qd45x9cynm66eeye48fdfjkx09fs6n4uc9

Show more details

Last Notes

2024-09-19 00:50:41 GMT

- reply

Leaving pretty much all social media, except linkedin

2024-09-19 00:38:19 GMT

Going to delete my AP instance and NATube tonight.
Cheers.

2024-09-18 21:08:04 GMT

- reply

I mean I agree in general regarding most usage of social media.
The problem is the proposition of the reliance of Nostr in podcasting, and related implications to actually make that work.

2024-09-18 20:55:23 GMT

- reply

fair
got me wondering how people intend to handle years or decades old information (they probably haven't thought about it)

2024-09-18 20:49:56 GMT

- reply

Why is that relevant?

2024-09-18 20:37:01 GMT

- reply

It's literally incapable of reliably doing at least half of the shit people want it to do without centralization!

2024-09-18 20:33:51 GMT

NOSTR HAS *NO* PERSISTENT STORAGE LAYER.

2024-09-12 00:00:31 GMT

- reply

What if I don't identify with any of the above?

2024-09-11 14:30:28 GMT

- reply

Which URL was that?

2024-09-03 02:41:00 GMT

- reply

It's almost as if @npub1fmx…wp74 and his co-host John have been doing v4v for No Agenda for a very long time, before bitcoin ever came into the picture.

2024-08-30 22:51:46 GMT

The podcast index pays less for all its linode compute than the lowest end single SQL server managed instance costs in azure government cloud.
lol

2024-08-30 13:17:03 GMT

- reply

Any time I look into self hosting matrix it looks like a nightmare. It might have an advantage in long-term community group chats but for 1-1 conversations I don't see the point.
That's not even considering the security/privacy concerns with how matrix is designed but I'm not really qualified to talk about that.

2024-08-30 06:37:33 GMT

Reminder that #xmpp is a great alternative to signal/whatsapp especially for 1-1 chats and voice calls.
If you want to self host, try out snikket. They have paid hosting available too.
https://snikket.org/hosting/
For Android users, Conversations is a fantastic client.
Of course, most people making noise about it all still want the convenience of a free service.

2024-08-29 17:56:20 GMT

- reply

Node screening based on compliance "risk"
https://github.com/lightsparkdev/python-sdk/blob/3166c28896dad185d9eddbe3afab59f6a43bb21f/lightspark/lightspark_client.py#L638-L647
```python
def screen_node(self, provider: ComplianceProvider, node_pubkey: str) -> RiskRating:
"""
Screens a lightning node using its public key. In order to call this API,
you need to have the API key stored in your account setting page for the selected compliance provider.
"""
json = self._requester.execute_graphql(
SCREEN_NODE_MUTATION,
{"provider": provider, "node_pubkey": node_pubkey},
)
return parse_enum(RiskRating, json["screen_node"]["rating"])
```

2024-08-29 17:53:11 GMT

- reply

Demo python implementation of VSAP compliance service
https://github.com/lightsparkdev/uma-demo-vasp-python/blob/main/uma_vasp/demo/demo_compliance_service.py

2024-08-29 17:51:19 GMT

- reply

https://github.com/lightsparkdev/python-sdk/blob/main/lightspark/objects/ComplianceProvider.py
```python
# Copyright ©, 2022-present, Lightspark Group, Inc. - All Rights Reserved
from enum import Enum
class ComplianceProvider(Enum):
"""This is an enum identifying a type of compliance provider."""
___FUTURE_VALUE___ = "___FUTURE_VALUE___"
"""This is an enum value that represents future values that could be added in the future. Clients should support unknown values as more of them could be added without notice."""
CHAINALYSIS = "CHAINALYSIS"
```

2024-08-29 17:35:58 GMT

- reply

Furthermore:
Compliance in LNURLP Responses
In LNURLP responses, compliance is a critical component that ensures adherence to regulatory requirements, particularly in the context of financial transactions between Virtual Asset Service Providers (VASPs). The compliance data is encapsulated within the LnurlComplianceResponse structure, which includes several key elements:
KYC Status: This indicates whether the receiving VASP (VASP2) has verified the Know Your Customer (KYC) information about the receiver. This is crucial for ensuring that the parties involved in the transaction are properly identified, reducing the risk of fraudulent activities.
Signature: A DER-encoded signature provided by the receiving VASP. This signature is generated from a payload that includes the receiver's address, a nonce, and a timestamp, all hashed using SHA256. This signature helps in verifying the authenticity of the transaction request.
Signature Nonce: A random string included in the signature payload to prevent replay attacks. This ensures that each transaction is uniquely identified and cannot be fraudulently repeated.
Signature Timestamp: The timestamp at which the request was made, which is also used in the signature. This helps in ensuring the timeliness of the transaction and that the data has not been tampered with.
Subject to Travel Rule: This indicates whether the receiving VASP is subject to the travel rule regulations, which involve reporting cross-border and domestic transactions to regulatory bodies. This is important for compliance with global financial regulations.
Receiver Identifier: The unique identifier of the receiver at VASP2. This helps in ensuring that the funds are sent to the correct recipient within the VASP's system.
These elements collectively ensure that the transaction adheres to the necessary regulatory standards and that both the sender and receiver are protected under the law. The inclusion of these compliance details in the LNURLP response is mandatory for transactions under the UMA protocol, reflecting a robust framework for secure and compliant financial exchanges between VASPs.

2024-08-29 17:35:26 GMT

- reply

From their AI Search thing in their docs:
How UMA Handles Compliance
UMA (Universal Money Address) handles compliance through a combination of internal and external checks to ensure that transactions meet regulatory requirements and organizational policies. Here's a detailed breakdown of the compliance process:
Internal Compliance Checks:
UMA systems verify transaction details and user data against the organization's compliance requirements. These checks are defined by the compliance team within the organization and are tailored to meet specific internal standards and policies.
External Screening:
UMA utilizes node public keys and Unspent Transaction Outputs (UTXOs) for additional screening. This is done with the help of external compliance providers, which helps in assessing the risk associated with the transactions.
Pre-Screen Transactions:
Before processing a payment, UMA conducts pre-screening of transactions. This involves verifying the transaction details such as the amount, the recipient, and the sender's information against compliance requirements. If the transaction is deemed high-risk or fails to meet compliance standards, it is not processed.
Post-Transaction Compliance Registration:
After a transaction is completed, UMA registers the compliance data for transaction monitoring. This includes passing post-transaction compliance data to the sending VASP (Virtual Asset Service Provider) through a callback URL. This data is crucial for ongoing monitoring and ensuring that all transactions continue to comply with regulatory requirements.
Compliance Service Integration:
UMA integrates with compliance services that perform these checks and maintain records of compliance data. This integration ensures that compliance checks are thorough and are performed in real-time, enhancing the security and reliability of transactions.
By implementing these comprehensive compliance measures, UMA ensures that all transactions are secure, legal, and align with both internal policies and external regulatory requirements. This approach not only minimizes the risk of non-compliance but also builds trust with users and regulatory bodies.

2024-08-29 15:31:27 GMT

- reply

This isn't just lightning. This adds on a bunch of compliance crap to verify KYC payments and trade export restrictions between lightning nodes.

2024-08-29 14:18:12 GMT

- reply

how is this universal?

2024-08-27 16:54:56 GMT

- reply

I am so far removed from front end development that getting back into it with modern tools brings out the worst sort of anxiety and decision fatigue.
Maybe it's because of how hacky everything used to be.
I'm sure I wouldn't really have an issue, but it's a dreadful thought.

2024-08-24 06:32:53 GMT

- reply

I tried copilot for 5 minutes with podping and turned it off right away and went back to pycharm. Don't have any other experience with it but it was just extra noise for me.
But then again, I wrote my own event handling library so the llm probably hadn't seen it before

2024-08-24 02:59:34 GMT

- reply

I use their IDEs whenever I can. Python especially, Rust too.
Haven't used it for javascript/typescript in a while but i imagine it's still great.
Honestly sometimes I see people advocating for neovim etc and I'm left wondering if they've ever used a real IDE. I'm sure some have and just prefer the simplicity of a text editor, but I'm not convinced that's the norm.

2024-08-23 23:54:15 GMT

@npub1rcn…dw4h phpstorm is great, used it at Wayfair.
And that was all before AI. Their refactoring and symbol matching is unmatched.
The auto fill stuff was there too. No AI.

2024-08-22 14:49:45 GMT

- reply

basically it's like a join that can reference tables from other joins

2024-08-22 14:46:14 GMT

- reply

you should've seen me when I learned about LATERAL joins in postgresql.

2024-08-21 21:08:33 GMT

- reply

It's not just Bitcoin. They are looking at being a Google/Apple wallet alternative.
@npub1gw9…74re

2024-08-19 15:23:45 GMT

- reply

Similarly, specifying “ISRC code" would appear to limit the usability of the license to music.

2024-08-19 15:20:11 GMT

- reply

Also not sure specifying “SOUND OR VIDEO RECORDING” is a good idea because this could be used for other types of media.

2024-08-19 15:17:04 GMT

- reply

Why is bitcoin specified in the license when this project is bitcoin agnostic?

2024-08-16 23:36:11 GMT

in before Apple demands 30% of revenue from funding tag links in the podcast app

2024-08-09 01:58:51 GMT

- reply

I quite like bop.
Although my habit is still htop which is arguably better to see the process list anyway.

2024-08-06 21:55:13 GMT

- reply

I was just talking to Dave about htmx which seems like it would be trivial to use with web components as a compromise. Haven't tried it though.

2024-08-06 20:36:59 GMT

- reply

I'm pretty sure it's standardized and available in all browsers, maybe with a polyfill for safari.
Not sure why it didn't take off.

2024-08-06 20:10:30 GMT

- reply

Wasn't web components supposed to solve that?

2024-08-06 00:35:50 GMT

- reply

Russell, as much as I despise advertising in general, the problem with these solutions such as this proposed advertising ID is they want highly targeted advertising with extreme levels of tracking.
Dave has proposed more simple solutions previously (to merely accurately track a podcast listen) and they have been ignored.
I really don't know what's so complicated about this concept that these people don't understand. Stop tracking people and maybe those people will be more willing to cooperate.
Until then, I'm going to continue by every means I can to block tracking where I can and provide false or useless data about myself otherwise.

2024-08-05 22:03:00 GMT

- reply

"The UID2 system is light and inexpensive to operate."
This entire system is unnecessary and the whole thing is a last ditch attempt to try to stay relevant.
They really need a consulting firm to come tell them the harsh truth that their industry is dying and that they need to pivot completely.
Whichever architects got paid to put this together should be ashamed of themselves. I can see it's all advertising and data companies as part of their "alliance" or whatever it's called.

2024-08-05 21:52:46 GMT

- reply

is this thing a joke?

2024-08-02 17:39:59 GMT

- reply

I finally tested out opening a channel from Olympus. Got a 1mil channel for like 16k sats.
Here's my URI, at your convenience.
02b66d7caae1acb51a95e036fc12b1e6837d9143141fcff520876b04b9d82f36d1@ol76v42x2lyyq3cy4s3oyhsnj3lelswaepzbanbjw5ciqe54bzzsvoid.onion:9735

2024-08-02 13:59:57 GMT

- reply

Yes, it is online.
@npub1z6g…amwj @npub1gw9…74re @npub1rcn…dw4h

2024-07-31 20:16:19 GMT

- reply

I can probably expand the use of rfc3987 to require an authority for http:// and https:// schemes in the IRI. Sound reasonable?

2024-07-20 18:59:40 GMT

- reply

"Simple shell scripts" are you the guy maintaining the hundreds of Korn scripts on AIX I have to analyze for requirements and migrate?

2024-06-29 20:42:13 GMT

- reply

The mint is effectively custodial lightning. Anyone telling you otherwise is arguing semantics. The details are mostly in the implementation and the bank scenario is essentially same as what Alby does.
The reason the available mints are a feasible implementation for the Podcast Index (and other businesses) is there is a Strike backend which allows PI to not be a money transmitter.
It's also a "standard" API so if [RSS.com](http://RSS.com ) for example wanted to offer a mint for their users with their own business Strike account, they could.
There could probably be backends for other exchanges long-term if someone wants to add them.

2024-06-29 17:05:45 GMT

- reply

Frankly, mints were inevitable.
See the blocksize wars and various paid actors involved in those decisions.

2024-06-21 05:37:55 GMT

- reply

As far as I know right now we only plan to add these mediums

2024-06-21 05:24:09 GMT

- reply

Yeah I'm using the json schema instead of pydantic because it's easier to keep up to date across several languages.
I only added it to the schemas package recently.
https://activitypub.agates.io/media/dd7d5993-a4c5-4ed1-8841-a14a6262d9eb/image.png?name=image.png

2024-06-21 05:17:51 GMT

- reply

https://github.com/Podcastindex-org/podping-schemas/blob/v2024.06.16.060318/schema/org/podcastindex/podping/podping_medium.capnp
https://activitypub.agates.io/media/995a5028-e51a-41fb-bbb7-8db2fb55d05f/image.png?name=image.png

2024-06-21 05:12:16 GMT

- reply

Yep... been two years since I touched this so working out the kinks.
They should all be under livetest

2024-06-12 14:03:17 GMT

- reply

How exactly do you intend to include independent hosts, standalone apps, and one off feeds in this?