jetbrains junie uses claude, default to 3.7, it also plans very well, i guess that's claude

the masks are off... it has always been sales/marketing driven and the official narrative is that programmers are expendable

that's gonna go pear shaped really fast for them in the next few years.

the reason why i pick #golang and stubbornly stick to it is because of the difference in the management culture of the Go project. to a lesser extent, the Java developers are similar, but i hate objects and they plague you with slow compilation.

most of the rest of the development companies behind the other languages like Javascript, Python, Rust, C++ and others have a marketing driven management system. marketers think that people keep paying for new features, because they field so many feature requests.

Go's management is engineering driven. they don't listen to marketing, because features create engineering headaches. they also wind up creating headaches for the idiots that buy into the feature creep culture of most development toolchain projects, and even to the point where there is a cultish mentality that i have seen over and over again among developers that go is deficient in some way because of what features marketing pushed engineering to give them. they are literally brainwashed idiots, not qualified, in my opinion, to be called engineers. they are cultists. the cult of objects, the cult of expressive and sprawling and ever growing language syntaxes and toolchain features.

i don't have anything against individual projects that want to build new features, but the moment their marketing driven minds turn to direct engineering, is my red line.

i'm an engineer, not a fucking theatre performer. there is a big difference and if the marketers interfere too much with engineering, you have all kinds of nasty accidents and problems coming from it.

the mainstream cultural zeitgeist is driven by marketing, which is used because megalomaniacs see that it lets them arbitrarily herd people into whatever paddock they want them to be in, no matter how bad it is for them as individuals.

in most of software development, the inmates are in charge of the administration. i'm not joining that circus. tyvm. gfy feature creepers.

btw, for 20 eur/month you get practically unlimited LLM queries for junie and the ai assistant, on the AI ultimate plan. i'm finding that it's more than sufficient. i also use a local LLM for the AI assistant, because i've been finding that Qwen 3 14B is more than adequate for writing documents and commit comments. but you need a decent video card for that, mine is probably about $400 current market value, RX 7800 XT. plays games nice too, though for new games mostly i stick to FHD, a lot of older games it can do 2k or 4k smoothly over 80fps

like the majority of development toolchains

jetbrains main customer base is java and go devs, and those two languages have sane policies on feature creep. go is the best of course.

i should add it to the default spider relay list then

also, i advise being careful to not have it make big changes that cut across multiple scopes, because it becomes very difficult to roll back changes. commit when it does the new thing properly, then you can just stash or dump the changes

i don't use this one you use, i tried it but it seemed too aggressive and prone to missing out things, and it doesn't make tests or check stuff properly, maybe if you tell it to, but not by default

jetbrains junie does. i only have to rein it in when i haven't given it sufficient scope limits

this only covers kind 0 events though, right? still good but i think relay lists, follow and mute lists should be included

yes, and it does it initially when the database is empty when you set an owner, according to what you define for the spider. it doesn't become responsive until it has the follow lists of owner and follows, and the mute list of the owner, which functions as the relay blacklist (which determines who can store events)

the rest of the spidering happens in the background at first start, and is repeated hourly to update the events you tell the spider to spider.

also, PKDNS is a consensus, which means that everyone has to follow it, or it doesn't work.

that's not how nostr works. nostr is only a protocol, not a consensus protocol. there is good reasons why you might not want to use the same protocol. like closed and private relays, companies will not want this information broadcast either, if it links to the company. the users directory events, though, are perfectly fine to be pushed and pulled from company relays if they decide to, it just leaks membership.

that assumes that you don't create push or pull schemes to sync them

i've been saying it maybe 6 months that "directory" events need a strong consistency consensus. this means broadcasting them and fetching them and keeping the latest versions, at least.

that's user metadata, follow and mute lists, relay lists, there is probably others that need to be added to that list but until the nip guardians and their fans recognise this, it's just gonna be me saying it.

it has to be recognised eventually. we don't need to broadcast everything, just the map.

i can't think of anything more i want to add to it particularly, but most of the features since adding the spider have been small refinements based on observations and reflection on what was done so far

there's probably the odd one or two more important small changes needed but yeah, it was probably fine for such use before.

i added one important feature today, a refinement, that allows designated owners to delete any event - only by e tag though, it would be a fairly big API change for the save/query functions to do a tag deletes as well. and kinda unnecessary, since for the most part you have already got teh option of owner mute list and getting all the IDs of their events and deleting them as owner.

so, yeah, should be good. do let me know if anything especially squirrelly happens. also be careful with the spider, this is why i have settings on it, privacy setting stops it reaching out to find events and there is three levels of spider, one is off, second is only to fetch directory events, and third is to pull in ALL of the second degree of follows into the relay, which happens on an hourly basis.

in the dark, bright light destroys your ability to see in the direction the light is coming from, so it causes disorientation. deer and rabbits and other nervous animals this causes shock, their blood pressure drops because their pulse weakens. cows are quite nervous animals too, but not as nervous as rabbits or deer, and animals like cats and sheep and goats (and weasels and raccoons) are just crazy so when they get that shock reaction their adrenalin surges and they run. humans are somewhere in between.

the thinner the base the more paper?

even if the bright light doesn't actually put the animal into a state of catatonia, it still is disorienting. this is why many gun mounted tactical lights have flash modes to disorient the targets so they can't shoot back.

zuck is a psycho. i already knew this but i had no idea the depths he had already plumbed. i quit using facebook because i found out they were deliberately isolating me from the social graph in 2018. but this goes beyond the pale.

all meanwhile zuck was helping along with the russia hoax and all, i mean, they are all in it together, and we need to shun them, and warn our friends. unfortunately normies are not gonna pay attention until they get their identity stolen or their bank accounts drained or blocked or suffer a physical attack because of someone using that information hacked out of their insecure systems.

some people are gonna suffer a lot, but there's not much you can do except warn them. they have to take the action to learn how to defend themselves. authoritarianism is the disease they need to cure, and they will never reject it while they are infected with it and feel no pain.

yeah, maybe not actually shoot them but they will scatter with some loud bangs. the horn is not scary enough for them. if you can use regular guns just put blanks in them, or get maybe a flare gun and hit a couple of them and they'll get the message. flare guns are probably the most universal solution you can apply anywhere in the world you need to drive through cow crossing paths

you misspelled jerk

that is now done, so the more insistent and persistent the pest is, the more vigorous the response.

note that this also will mean that users using clients that don't do auth with outbox will effectively be permabanned until they use a client that doesn't.

and so it should be.

i pay for my relay to run. i'm paying for their stupidity. not anymore.

you asked if it's true

the answer, is it's true to the extent that they have good, current images of the locations, and how frequently they are updated as the landscape changes

it is now deployed and the latest tag on https://orly.dev now has this functionality.

was driving me nuts for the last few weeks watching blastr type servers keep on doing it.

i'm gonna get the agent to escalate the ban time by double every time also.

they are normalizing the idea of constant universal recording of everything.

their ability to do it does increase over time, and will accelerate as the storage cost is reduced to updating recognition models of LLMs but at some point enough people will feel that glare of the panopticon and start to passively resist it in dozens of ways. one being, to no longer publish photographs.

they are just creating a patch for the consequences of a patch, for the consequences of a patch, for actions of a small group of psychotic megalomaniacs.

eventually there will be no patient, only bandages, and at that point, the system collapses.

i'm getting a bit tired of stupid relay bouncers that keep on submitting events to my relays without authing, and then just keep on doing it no matter that they are getting blocked: auth required messages.

so i'm employing my LLM coding agent to spin me up a temp ban system so that it blacklists an IP address for 10 minutes after it repeatedly attempts to publish event without paying attention to the response.

hopefully the agent will not make a total hash of this and with a small bit of checking i will have it implemented.

if your fucking event publish script doesn't stop trying to publish when it gets responses, you are an asshole, and the default standard response to assholes is shunning.

10 minutes is long enough to cut the traffic level down. you will just get "connection reset by peer" or some similar message over and over again in your fucking logs, if you fucking even use logs, you assholes, and my logs won't be spammed with constant bullshit.

there is a property in common between the need for a single global currency for the internet, which #bitcoin provides, and #nostr - which is the need for a single social network identity.

there will be an eventual convergence on nostr as an identity system because it lacks the limitations of all of the others: transportabliity and the ability to store attestations of other network identities.

the property of bitcoin that has made it the dominant cryptocurrency is called "moneyness" and this stems from a market need for marketability of the commodity that is to be used as money. this is why bitcoin keeps on growing in value and userbase.

the equivalent in an identity system for the internet is the need to be able to identify a singular point at which anyone can go look and see "that's this guy". keybase (RIP) had a scheme for attestation to link network identities together, but it didn't have the self-sovereign identity base for it. so it never took off for this purpose, even though it made it quite easy to do.

what people want to be able to do is just publish one event that says "i'm this user on X, this user on facebook, this user on gmail, this user on protonmail..." and so on. there is only one place on the internet right now where you can do that, where connecting accounts together can be achieved:

nostr.

one thing that i feel is missing from #jumble nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl is follow list management. i had to use coracle to prune my list because it had ballooned to 98, and looking through the list on coracle i found that a lot of them were ded or irrelevant.

i mean, i don't really mind needing to resort to using another app to manage follow lists, just that nowhere in the interface you can even see it let alone edit it.

in case it isn't clear:

nostr becomes the best option for all-in-one-place network identity attestation

ok, but ultimately many protocols don't provide for the ability to store an attestation. github does, but telegram doesn't, for example. and it's a combinatorial problem because how do you keep them all updated across many accounts?

so you have to constrain how wide you throw the net. some can't be verified, others can be.

anyway, fuck pubky. it's unnecessary, and will die like all altcoins eventually die, because network identity shares properties with moneyness.

if the nostr profile event contains all the outbound references to other protocols, teh other protocols can just refer to it and cover all bases.

HTTP has a standard for this, the proto prefix:

so you could have telegram://mleku1 and nostr:// and pubky:// etc etc

almost universally, user profiles on almost all web apps and protocols have fields in profiles for other network identities. it should just be a tag list, even:

["U","",""]

almost all secret keys are valid across all curves, also. so it's really just about registering them. all you need is to have fields for them in the profile metadata events

yeah, it's only missing the net around the hat

kanzan, saberhagen, and a bunch of others, all just troll bitcoiners here for fun. i wish y'alls would stop talking to them

i can't see it in nostrudel or coracle mleku1 is my telegram

i'm looking for a #job ... 8 years experience #golang programmer, lots of experience with APIs, #cryptography, #bitcoin and #nostr, badgerDB key value store, concurrency, #network and #protocols

i'm open to a temporary contract, full time, anything at all that will get me some more runway for something better if it's not long term.

yeah, all of them were. bulgaria, serbia, france, spain, italy (heh), germany, austria, mongolia, china, egypt, probably czechs had one at one time too.

really it was just generations of dynastic professional bullshit artist murderer baby eating cunts moving from one place to the next wherever the booty was.

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl is my own personal nostr client Jesus. finally someone built a nostr client that actually makes it easy to test relay functionality.

https://jumble.social it has relay global feeds

also, my custom nostr-specific JSON unmarshal function is nearly as fast as a binary decoder for an optimized binary encoding. about 20% slower. it's also the fastest json event decoder in all nostr land.

further, all the relays that use RDBs and NoSQL DBs are automatically indexing all those tags whether you like it or not.

i write database engines from scratch using a KV store, and it's not really that difficult, and the tailoring of the implementation greatly improves performance. i don't think i'm exaggerating when i say that the #orly database engine is the fastest in all of nostr. it uses an engine that is used for a moderately popular graph database called dgraph, and you can't do that shit without highly optimized iteration and log storage strategies.

if primal forks off the main nostr network GOOD

also, fuck primal. their days of big reach are coming to an end with KYC all the things. i don't think that KYC friendly normies will like the content and probably all kinds of bluehairs will complain to google about it and get their listing chopped despite all the bending over and presenting of the fuck hole that they do.

i'm not joking.

kind definititons are very nebulous, some subprotocols use one, with tags (eg kind 1) and others use multiple kinds for a single subprotocol.

indexing all tags is not complicated, that's what hash functions are for.

i was building a db engine that could do it, it wasn't that complicated. kinds, however, are not self describing. neither are single letter tags. it's my biggest disagreement on the design of nostr aside from the use of JSON instead of an email-style line structured sentinel based format. the reason i prefer this type of encoding is a) it's also plain text b) it's self describing and c) it's cheaper to parse it, json's english-style structuring nearly doubles the processing requirement.

#orly #devstr #progressreport

so, i got it done... again the damn configurations, but also in this case i forgot to put in a label in an outer for loop so it actually worked

the replication path is now this:

try the replicas one by one

if success, done

if fail, try another

all of the replicas do the same thing, in addition to not sending to relays that have their key listed in the X-Pubkeys header and voila. 3 replicas, 3 messages, 100% propagation.

if for whatever reason one of the replicas can't connect to one of them but the others can, it will be gotten to.

this will mean that replication can scale at O(1) so message delay of propagation is linear to the number of replicas. which is much better than the previous uncivilised format.

so now ORLY can set up as a cluster or replicator, either option is possible, and two or more relays can now automatically push their new events to the other peers and instantly any subs on the other peers will also get their events. if any of the relays ded, then the message won't get to them but no user would be on them either.

in theory, the main reason for ded replica would be connectivity. but of course it could be bug, but i'll never mind that for now. still more tasks to complete on this one, but mainly just the reverse proxy and the DNS configuration and then writing a configuration system that generates the necessary configurations for a cluster deployment and voila. the world will have high availability ORLY relays that behave almost like a single big relay on a faster connection.

this will be great for censorship resistance since it would be easy for multiple individuals across jurisdictions to use the config tool to set up their own relay identity and then share their address and key to the other members and no single person can be a target for a total takedown.

and yes, it would work as equally with relays at different addresses as it would for a round robin DNS, the difference being that with different geographical locations, users could be selective for the local replica but users in other locations can use their local one... so, optimising local latency while enabling propagation at not too much slower speed.

this will be very useful for business deployments.

i would further add "and am very much in favour of fuck you primal and you snooty little bitches haha payback for being such attention whores"

if the user can enter any relay address they want, including, like is common in japan, simple IP addresses, those bureaucrat's can't compute this, so they are just gonna blanket ban nostr clients from mobile app stores.

if there is no client, there can be no access to relay.

bureaucrats are not programmers. they are firstly thinking only:

people only use mobiles

web apps are already covered by age requirements in many places

policing web apps out of jurisdiction is going to be extremely expensive for a lot less show and bluster than just blocking social apps

if they do decide to start playing that game, their target audience is people who are already using open platforms and may have moderate technical knowledge and off they go to get VPNS and now while the politician appears to have "protected the children" all they have really done is cover up the "problem" and done their victory laps because politicians have tried the great firewall game a few times and it has never been very successful. the campaigns have been very unpopular because only china does this shit. and apparently, children don't use computers.

so, yeah, the whole point of nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h 's OP is about the fact that mobile devs are going to be the first on the chopping block for being locked out of mobile platforms

the digital rights mob will just keep hammering at the alt app systems, and campaigning against the policy decisions of apple and encouraging people to ditch them, which they won't, because they are hypnotized zombies and i wuv my apple bro don't hurt my brain.

politicians are lazy. that's why they are politicians. if they can get a big fluster over anything to appease some squeaky wheel they are gonna do exactly what is demanded, by said squeaky wheels, which are mostly nosy karens who bewieve in pwoteking teh chlirdrens

those karens are dumb as toast and are not going to squeak very much about geeky kids who have figured out the bypass and because the cross jurisdictional shit... honestly, they can only swat the big guys.

that's the point of the commentary. you get big and popular on play store, you are in the crosshairs

if the dumb karens don't see it, it doesn't exist to the politician whose job is about appeasing these tabloid fodder.