Also have an #orly -next 🦉running on imWald 🌲 (The owl is in theforest 😂), but I need to work on the Apache settings for the protocol upgrade, or something. Later.
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku
i have no idea about apache or nginx for reverse proxy stuffs
#orly🦉 is going to have a web UI
just building the first part to get the user to log in because they have to be logged in to use it (and be on the whitelist)
once that's set up, it's simple to then add configuration and post management tools etc for admins and cool stuff like "download all of my events", probably will end up becoming a client as well lol
well, wowsers that was quick. already seems to be working, test relay is full up with events from my follows. gonna deploy this on the test
it does a one time sync, has a marker for that, when it's done, so it doesn't do it again, and then it does a default hourly sync of the last two hours of events to catch everything, so if it's your personal relay it keeps all your relevant messages to see what's happening in your circle. which i think is also a nice thing for a paid relay to do as well.
gonna start with a simple spider aggregator that seeks to sync up the admins' follows events everythere it can find them, so within the sync period it has everything (setting to 1 hour because it's a bit of an operation) but also if users have the relay on their list they already publish to it.
just something to put the content in there mainly to see it in relay feeds
#orly🦉 #devstr #progressreport
back to the relay, i've got a stress tester tool now to profile heavy load, and the benchmarks are working again and strangely giving more reasonable numbers for events/s bulk write test. probably the client code has been changed to be better mannered, i dunno.
actually implemented the protected events thing, it won't store events with those markers unless the author of the event is authed.
now to find some useful things to add in there
The Talos Principle is on super special on Steam right now
been meaning to pick it up
#steam #games #gamestr #special
i think it's on the latest, i haven't touched it in days, been in a nostr client vibe coding frenzy
Which tag are you running here, nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku ?
the other two notes didn't work but this one i'm replying to is on orly
you can just run bitcoin core 27 forever
there's still 16s on the network
Make Housewifery Heroic Again
this is why i have the xapo bank account... i keep always bitcoin and only right when i spend i exchange to pay the card. it's kinda frustrating because about 18 months ago i had 10 bit cents. yes. 0.1. but hey, the QD OLED is nice lol.
Yes, this is a great improvement over dumb paid relays that only store what their users write to it. However, if the relay wants to be even more proactive, and allow its users to discover great content from people they don't follow directly, then you need more sophisticated tools that deal with reputation.
For example, instead of using the follow-list of a user, you could use it's 2-hop-follows, or 3-hops. But then how to mitigate spam? This is recreating personalized pagerank basically.
For each user, you create a list of "probably interesting" people by computing the personalized pagarank and applying a threshold for spam mitigation.
So you end up with his follows, and his most "reputable" follows of follows, and so on. And you don't have to build all of this from scratch, you can just call RecommendedFollows of nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qpqkpt95rv4q3mcz8e4lamwtxq7men6jprf49l7asfac9lnv2gda0lqpsy38p , and all of this is taken care of.
it's still a good distribution pattern tho
i just had an epiphany about the function of follow lists as being like a consensus hint for replication pattern of data, combined with relay lists.
if you have a relay that you pay a subscription to be able to write to it, it makes sense that the relay would proactively real-time subscribe to other relays where relevant events may pop up, in the background, if other relays also use this "pull-subscribe" pattern they automatically replicate like a programmable replication algorithm, when the relay has some set of users, their events and relevant events are all received in real time.
each relay then becomes a replica with high availability for its users most requested data, and each overlaps with copies going across the multiple relays that the user has configuration.
each of the lists is different on each relay and the data goes exactly where it's wanted, automatically, all using built in protocol primitives and a simple background service on the relay.
this enables nostr data to be widely distributed and replicated in accordance with the preferences of the users, all automatically and instantly.
it's just about designing the queries and adding the service and relays become a mesh for user data.
my mistyping of definition got undefineded
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9u2mk7fe I cant unfollow this bullshit itz because I cant unfollow the #music tag
that is one of the holes in the spec that i've noticed. follow lists don't have a proper defintinition of where to put hashtags in follow events. i've seen there is many clients that put hashtags in p tags
ok, it's quite a long way then. roughly the midpoint on one side of the two anomalies is around the mediterranean north of libya and egypt.
yeah, but it's in the same region where the ocean motion will be less in the rotation
or like this guy, hundertwasser:

also, the region near egypt in the mediterranean is where is expected to be the pivot point, 90 degrees between (notably, hawaii is near it). this is an area where ocean motion will be the lowest. the mediterranean is shallow compared to the atlantic.
interesting, i have been saying for a long time that sympathy is what creates social concordance and empathy is reading people but not feeling it (sympathy is where it moves you emotionally in sympathy) to read someone and not feel them is the root of how you can do horrible things to other people.
the atlanteans moved there for the 12000 years ago event, and left around 5000 years ago. i explored a lightning map and it was interesting that the whole plateau under egypt has a very low lightning strike frequency. there's a few others, iirc mongolia doesn't get lightning strikes very often either.
i didn't know the nodding forest man gif was robert redford. well there you go.
that could have been because of shifting from equatorial to polar position tho. they wouldn't have been prepared for it. even if the place doesn't get washed away the changed temperatures will probably kill off most food sources growing and living there.
also it's telling that there is evidence, that wasn't washed away or buried deeply, of the existence of these people. they just would have been living in a lush high altitude plateau in the warm subtropical zone and then are suddenly temperate zone. everything freezes in winter and nothing was prepared for it, except a few outliers and burrowing animals and many trees would not survive that transition very well. though, ok, a lot of things would make it.
point being that there probably was no food for some years while herds built back up and people got adapted to the new weather and adjusted their construction to adapt.
also, heavy storm winds are no good for dirigibles, they'd get thrown into the sea. unless maybe at very high altitude and consider also the problem of potential total electrical failure, and some metallic materials being fused by atmospheric electricity or radiation
nah, the ocean doesn't go over everything, but it goes over a lot, and at fault areas it is possible to either go up or down as well.
the northern carpathian mountains are under a very thick base and far inland. but yes, other places are mongolia and eastern rockies. km to the ocean plus metres above sea level, and you want to be over 3000, 4000-5000 is ideal
i think that wherever the pole is, it aggregates a very strong field alignment due to how powerful the field is, and the rock around it will tend to align north to south in that position. so, it seems logical to me that it would tend to be a pair of poles that you find during each period there is magnetic anomalies in those areas even though they may not be especially thick parts of the crust, it just used to be the pole point.
the field is from the highly compressed, high iron containing core of the planet, and the pressure and gravity makes it more or less directly turn the gravity into a magnetic field, like a dynamo, imparting magnetism from the forces going into it.
the crust is just dotted with material in various patterns of magnetic permeability and there are numerous dense areas in various layers of the crust and even the mantle has high and low magnetic permeable areas in it, these have been measured and estimated their shape from the field effects.
the main thing is that normally the viscosity of the material the earth sits on is higher, and when more electricity gets into the earth, it gets hotter, and that lowers viscosity and then at a certain point, the magnetic field outside, from the galaxy, couples with these anomalies and pushes them into alignment with the gravitational pole, ie north/south pole of the core.
in the process, there can be shifting of plates as well as new faults forming so some land as well as being flooded, may rise or fall compared to its current location. the himalayas and mongolian plateau are examples of land that uplifted a lot at one point, pressing plates together.
yeah, it's probably pretty rough time to be around on the planet lol. that's why i am planning to be inland and up high sometime in the next 3-5 years.
well, fossils can only happen in places that get inundated with mud very suddenly. high pressure and low oxygen is what lets them turn into carbon instead of carbon dioxide.
90 degrees is what you would expect from a sine wave magnetic field oscillation on each phase of the cycle, which is ~25000 years
i think it only turns over every ~12000 years tho, the 6000 year point in between is a disaster but on a much smaller scale. magnetic field maximum is what causes the 6000 year, this one coming up is when the field goes to/thru zero
there is two massive magnetic anomalies in an axis that i have started to call the bermuda/dragon's triangle pole. one puts the south pole at what is around where the bermuda triangle is, and a second one is near japan and has similar legends around it. these are permanent aligned areas that have a predominant field direction that is 90 degrees (opposed) to the currrent north-south pole direction, which is mostly controlled by the core, and the crust doesn't move around much underneath it (though it is constantly turning) when the crust/mantle boundary heats up due to piezoelectric and thermoelectric effects from increased solar energy due to weaker field due to opposition from the galactic current sheet.
when this happens, the current magnetic anomalies move to their other positions relative to the core magnetic field. it happens over a day or three period and most of the land is covered by 1km of ocean water washing over, and then washing back.
was that you i remember talking about seasteading? this is a viable way to survive, if you have large sea vessels.
It will be near the equator soon enough. That's also why they found petrified forests under the ice, from previous flips. I mean, if there isn't any more clear evidence of pole shifts meaning the crust moves, the forests under the ice of Antarctica kinda prove the sun once pointed directly at what is now in shade half the year.
personally i already pegged most of the people who have joined in the brigading as suspect a long time ago. and core's actions had already started to become suspicious 4 years ago.
there is professional public relations narrative controllers behind the curtain. all of the people who have piled in are bullies, and easy to give them a sense of safety in numbers and authoritative figures to defend their vicious behaviour.
i think that they are just coming out of the closet.
they already have the kernels of their militias running. they will have to "defend" and "avenge" the "oppressed" now.
it will go from assassinations to kidnappings and ransoms and arson and bombs next.
they have to defend those poor refugees too you know.
this is the usual gif, but with a subtitle

protest is the program they have been drilling into people. i remember back like 1995 reading stuff about direct action and in my opinion, those books were building up for getting people into the idea of terrorism. but i had my own interpretation of direct action. the cypherpunks did my version. create a parallel, good society and especially marketplace. move out of the cities full of NGO funded protestoors and use the internet to talk to the other humans who aren't in a brainwashed dream world, and do business with them, and live more and more outside of their horror clown world.
no, it's a reference to a popular gif that bitcoiners use to signify approval, from the mandalorian
this_is_the_way.gif
yeah, so call this a feature request:
move all of the nostr relay communication code into one directory
i think it's because it's small so it hasn't got overwhelmed with complexity but maybe you need to have a look at organising it before new features because this last week i've noticed a few bugs creeping in. feeds not loading, some events not publishing (even to only two relays), and a few other quirks.
you would have a good excuse to tell all the feature requesters to shush for a while also :)
what would be better is a queue that just tries, when it succeeds, remove the item from the queue, and retry the others with an increasing delay until it's like 5 minutes then give up
btw, back then, i wrote this little text, that explains psychological manipulation techniques, i encoded it into a set of 9, and all of them use a word to describe them, as a mnemonic, starting with the letter C:
https://gist.github.com/mleku/ebc69873963c0f1c74729bac8a577796
i've done a lot of psychedelics and amphetamines over the years. meth, in particular, has had some rather strange effects i've observed involving memories, for years every time i dosed i'd get flashes of dream recall of this one dream over and over again that recurred a lot in my childhood and even again later.
in the dream there is a scene a bit like the final scenes of The Labyrinth where i'm walking through this "dump" sort of place, full of these rusty old metal skulls and i'm like sure that under my feet somewhere i'm going to step on a trigger plate and have them close on me.
then there is another scene where i am floating on some kind of boat, at first it's like a ship, but it's adrift in a canal surrounded by mangroves. then it becomes a raft, and i'm looking around at the water, sure there is crocodiles in there who might attack me.
this dream sequence almost consistently popped into my mind in the first hour or two almost every time i dosed for most of my mid 20s.
the theme, if you don't quite get it, relates to the hidden triggers that people have that cause them to judge you unfairly, and a sense of being alone in this awareness of the dangers in the waters (emotions) of myself and people.
deleting deletes is not the same as expiring a delete.
it is not contrary to the spec for clients to send delete events with expirations in any way. you probably just were too caught up with your admin powah to realise that relays are not prohibited from deleting delete events on the basis of expiration. because they are. just like you as relay developer and administrator can override this.
come to think of it, i possibly haven't got an exception to allow administrators to delete delete events. since that's outside of spec and any prohibition of this is contrary to the sovereignty of teh node operator i should check that, making a mental note.
the spec says nothing about any events being excluded
NIP-40
======
Expiration Timestamp
--------------------
`draft` `optional`
The `expiration` tag enables users to specify a unix timestamp at which the message SHOULD be considered expired (by relays and clients) and SHOULD be deleted by relays.
#### Spec
```
tag: expiration
values:
- [UNIX timestamp in seconds]: required
```
#### Example
```json
{
"pubkey": "
"created_at": 1000000000,
"kind": 1,
"tags": [
["expiration", "1600000000"]
],
"content": "This message will expire at the specified timestamp and be deleted by relays.\n",
"id": "
}
```
Note: The timestamp should be in the same format as the created_at timestamp and should be interpreted as the time at which the message should be deleted by relays.
Client Behavior
---------------
Clients SHOULD use the `supported_nips` field to learn if a relay supports this NIP. Clients SHOULD NOT send expiration events to relays that do not support this NIP.
Clients SHOULD ignore events that have expired.
Relay Behavior
--------------
Relays MAY NOT delete expired messages immediately on expiration and MAY persist them indefinitely.
Relays SHOULD NOT send expired events to clients, even if they are stored.
Relays SHOULD drop any events that are published to them if they are expired.
An expiration timestamp does not affect storage of ephemeral events.
Suggested Use Cases
-------------------
* Temporary announcements - This tag can be used to make temporary announcements. For example, an event organizer could use this tag to post announcements about an upcoming event.
* Limited-time offers - This tag can be used by businesses to make limited-time offers that expire after a certain amount of time. For example, a business could use this tag to make a special offer that is only available for a limited time.
#### Warning
The events could be downloaded by third parties as they are publicly accessible all the time on the relays.
So don't consider expiring messages as a security feature for your conversations or other uses.
any relay that implements expiration tags the users can set their targets as well, just sayin'
nothing you as administrator can do except make your relay ignore these tags, which is kinda shitty.
deletions with long expiration tags would be a good approach, like a year or so, to save storage space since after a while users will stop trying to re-save deleted events.





