| DOSE: |
20 mg |
smoked |
5-MeO-DMT |
(powder / crystals) |
I had read that 10-20mg was a 'fully psychoactive' dose and was please to discover that it was possible to obtain 500mg by mail for $175. So I placed my order. About a week or two later, a small package arrived from the Southern US with my name on it. I opened the package to find a small wax paper envelope sealed in a mylar bag. Therein lay the object of my desire. I should preface the following with the fact that I have had a multitude of experience with psychoactive compounds from LSA to Datura, nutmeg to MDMA, LSD, etc...And while all of these allys had their potential, there was always something missing from the experience. In retrospect, perhaps it was that I did not respect them as they apparently deserved. None of them had ever taken me beyond the known world to a point where I could not rationalize my experience, and for this I think I denied them their dues.
Feeling a great amount of anticipation, I eyed the little yellowish crystals in the wax paper, almost with a sense of awe. Something about their very presence seemed powerful, as if they were trying to tell me something. I decided that there was no time like the present, and having read that nothing can really prepare you for what happens, I asked my girlfriend if she would make sure I was safe. She agreed to watch over me while I tried this new substance.
I smoked a cigarette (I no longer smoke) and filled a pipe with ashes to buffer the melting crystals and stop or at least slow their retreat from the flame and vaporization. In retrospect, I would not smoke beforehand as I am not sure what effect this may have had on my experience. Looking at the pile of 5-MEO-DMT, I noticed that there was a particularly large crystal, about the size of a blue-tipped match head, in with all the smaller crystals. I also read somewhere that the effective dose was about this size, so, lacking a scale, I went with that crude measurement. I gathered the crystal from the pile and placed it in the center of the bowl of ashes.
Looking at my girlfriend, who was also smiling and excited, I felt completely safe. The environment was warm and I was in our bedroom. I felt that the setting was optimum and that my set was positive and clear of subjective expectations. I took a deep breath, lit the lighter, and exhaled as completely as possible. Holding the flame to the crystal, I inhaled slowly, touching the flame to the yellowish chip until it sizzled and melted. I inhaled deeply and was pretty sure that I got all of it.
00:00- I turn to set down the pipe, still holding my breath. I looked back at my girlfriend and notice that her face was already starting to shimmer and become disorganized from itself. I exhaled.
00:05- I felt a rushing sensation as though something was being forced into my body, or spirit, from somwhere unseen. I laid back on the bed and took another deep breath, almost as if to try and realign my senses. This was, of course, to no avail. By the time I was able to think about how I felt again, I was so high that it was a shock. It was all happening so fast that my brain could not wrap itself around one second's worth of experience before the next second came and was twice as intense as the previous one.
00:10- Eyes wide open, the 'real' world was not at all within the reach of my senses. It had been almost instantly replaced by an undescribable (though I will try) world of rings within rings, spinning and rotating, seemingly constructed from multi-colored static and deep as the ocean is wide. It occured to me at this moment, 'You have forgotten to breathe' so I took in a shuddering breath, still awed by the almost complete absence of anything familiar. I though for a second that I might have overdone it. 'Ok, you're going to die, you're gonna forget to breath and suffocate.' with that I took another breath, this seemed to aleviate my paranoia somewhat, and as unbelievable as this is to me now, I think I decided that even if I was dying, it didn't seem like a terrible thing. I accepted mortality and relaxed.
00:15-30?- The rings faded into what I can only describe as an awareness of something else. This something else was big, I mean huge, perhaps infinite. It was warm and I felt as though it reached out and connected with everything. I became aware that this something else more than connected with everything, rather, it was everything...I was everything. 'I', what is that? 'I' became 'It' and IT was everything.
00:30-1:00- Bliss...'I' am floating in a sea of warm energy. Little ripples would pass through 'me' and 'I' would sense their rippling going on forever, into what I had now realized, was infinity. I can sense other beings in this web of something else. They are happily floating here too and perhaps unaware of their connection at all. It does not matter, it really is all good.
1:00-2:00- 'How could I have forgotten about this', was the sensation the I felt, as if I was remembering. I had contacted a feeling that while totally new to my current version of my self, was somehow familiar on a deeper level, almost as though it were a Deja Vu.  'All is one' These thoughts were not formed as common thoughts like 'I want a cup of coffee' or 'I'm going to take a shower'. They just were.  They just were.
2:00-3:00- Ok, I'm coming back. I can't see the room and I just want to stay in that place. When I relax and close my eyes (which I was later told were open for the above two minutes) I can easily drift back to that connected feeling. I decide to linger there for a little longer.
5:00- I am elated. So excited that I have finally 'broken though'. I start to try and explain and find that I really still cannot talk. I can see my girlfriend, she is smiling, anticipating what I have to tell her. I must have looked so high for the last few minutes. I exhale a deep breath and it sounds like I am on N2O, a spring reverb echoes around the sound of my exhalation.  I take another breath and try again to focus on baseline reality, whatever the hell that is.
10:00- I am still very high, nowhere near where I was ten minutes ago. I am amazed and begin to explain to my girlfriend what happened while I was 'inside' of that feeling. She relates to me what happened while she watched from the 'outside'.
30:00- almost normal...still some fuzzy LSD like touches here and there, a brightness to things. Feeling a little nausea.
45:00- The slightest hint of high hangs on. Just enough to feel like I am in the first 25-30 minutes of an LSD trip, light buzz, nausea has completely faded.
60:00- Sober, but changed. I feel like I have held the truth in my hand and then sat with it for a while. It was inviting, not at all like I assumed. Truth is comforting, albeit, perhaps, subjective.
After Effects:
Honestly, there was nothing notable. Looking back though, I feel like I was held back by the lack of breath thing at the beginning. If I could go into this with the knowledge of that problem, I feel as though it would not be an issue. (Subsequent experiments proved this to be correct) Otherwise, the after effects were all on my consciousness. I have long been a believer that everything relies on everything else for balance and survival, this experience put me directly in contact with that reality. I will never forget the lesson that I have learned. Whether 5-MEO-DMT is responsible for it or not, I decided to start taking better care of myself at that point. Quit smoking, exercise, break free of unhealthy relationships, etc.
Conclusions:
I believe that in the proper setting, with advanced education about the experience and with the support of competent guides, this substance could profoundly impact the course of humanity. It has given me a respect for all things and their place in the world that was there previously but not at all reinforced by experience in my life before this experiment.
CAUTION! I would not recommend this for 'solo-trips' I have since guided people with this substance and have seem some weird responses to the fast onset (like getting up and trying to walk away!!! This is not good when you are not in touch with every day reality and under the influence of a major psychoactive chemical!!!)
Oh yeah, after all this I was shocked at how many of these experiences I potentially could have (500mg divided by 20mg = 25 mind blowing trips at about $7 each.) so I gave some to responsible friends and dosed a few other people figuring that sharing this experience was more valuable than hoarding it.
Go with care and respect for yourself, your ally, and the universe.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


INTRODUCTIONSpeed . Accuracy .  -- Rick Osborne
ByteRace is a challenge for minds that have honed the art of problem solving. This competition presents challenges for you to solve using code.
So if you get the adrenaline rush when you see a difficult problem in front of you then this is definitely for you.
Rules:
1. This is an Online event, which will be held on HackerRank/Codechef platform.
2. This is an individual event and any form of violation of platform rules will lead to disqualification.
3. Competition consists of 5 algorithmic puzzles to quench your thirst for the unsolvable.
4. The judgement of the organizers will be final.
5. Participants can participate from their room or from the CC.They need to have a HackerRank/CodeChef handler.
Venue and Timing:
Day and Date :Time :Venue :
Important Declaration:
1. Please keep checking the Celesta app, website and Celesta, IIT Patna facebook page for any future updates.
2. The rules can change without prior notification.
3. In case of any dispute, the decisions made by the organising committee and judges are final and binding.


The J2SE 1.4 platform included the "Crimson" reference implementation for JAXP 1.1. The J2SE 5 platform includes a reference implementation for JAXP 1.3 based on the Apache "Xerces" library.
Because these implementations come from entirely different codebases, and because the JAXP standard has evolved from 1.1 to 1.3, there are some subtle differences between the impementations, even they both conform to the JAXP standard. These two factors combine to create the compatibility issues described in this guide.
However, while XML applications written for 1.4 do suffer some
incompatibilities, JAXP 1.3 in the
J2SE 5 platform provides some
compelling advantages:
That's the good news. The bad news is that some compatibility issues have survived all attempts at eradication. The remainder of this document discusses those issues.
While the reference implementation in J2SE 1.4 supported the DOM Level 2 API, the implementation in J2SE 5 supports the DOM Level 3 family of APIs. This section covers the impact of those changes on programs that used the JAXP 1.1 reference implementation:
For more information, see the complete list of changes in the DOM Level 3 Changes appendix.
In DOM level 3, additional methods were defined in the following interfaces:
The added methods only affect applications that implement the interfaces directly, and only then when the application is recompiled. Applications that use the factory methods to obtain implementation classes for these interfaces will have no problems.
These changes affect an application that reads in XML data into a DOM, makes modifications, and then writes it out in a way that preserves the original formatting.
In JAXP 1.1, extraneous whitespace was automatically removed on input, and a single property (ignoringLexicalInfo) was set to false to preserve entity nodes and CDATA nodes, for example. Including the additional nodes made the DOM somewhat more complex to process, but because they were there, adding whitespace output (indentation and newlines) produced highly readable, formatted version of the XML data which closely approximated the input.
In JAXP 1.3, there are four APIs that the application uses to determine how much lexical (formatting) information is available to process, using the following DocumentBuilderFactory methods:
The default values for all of these properties is false, which preserves all the lexical information necessary to reconstruct the incoming document in its original form. Setting them all to true lets you construct the simplest possible DOM, so the application can focus on the data's semantic content, without having to worry about lexical syntax details.
Note:
When adding new nodes, the application must add any indentation and newline formatting that is needed for readability, since it is not provided automatically.
Following are the changes made between SAX 2.0.0 and
SAX 2.0.2 that might affect compatibility.
DeclHandler.externalEntityDecl
now requires the
parser to return
the absolute system identifier for consistency with DTDHandler.unparsedEntityDecl
.
This may cause
some
incompatibilities.In SAX 2.0.1, an application can set ErrorHandler, EntityResolver, ContentHandler, or DTDHandler to null. This is a relaxation of the previous restriction in SAX 2.0, which generated a NullPointerException (NPE) in such circumstances.
So the following code is legal in JAXP 1.3:
SAXParserFactory spf = SAXParserFactory.newInstance();
SAXParser sp = spf.newSAXParser();
XMLReader reader = sp.getXMLReader();
reader.setErrorHandler(null);
reader.setContentHandler(null);
reader.setEntityResolver(null);
reader.setDTDHandler(null);
The vast majority of applications are unaffected by this change, because the DefaultHandler implementation class has been modified to declare the additional exception, and very few applications use the DefaultHandler in such a way that they will run into a problem.
The only way an application can be affected is if it overrides the resolveEntity() method and also invokes super.resolveEntity(). In that case, the application won't compile in J2SE 5 until the method is modified to handle the IOExceptions that super.resolveEntity() could throw.
and the following new property:
For a complete list of Xerces features and properties, see http://xml.apache.org/xerces2-j/features.html
and http://xml.apache.org/xerces2-j/properties.html.
Note:
One point of compatibility is also worth mentioning. Namespace
recognition was turned off by default in J2SE 1.4 (JAXP 1.1). For
backward compatibility, that policy is continued in J2SE 5 (JAXP
1.3). However, namespace recognition is turned on by default
in the official SAX implementation at www.saxproject.org. While not
strictly a compatibility issue from the standpoint of JAXP, it is an
issue that sometimes comes as a surprise.
Code that uses the standard JAXP APIs to create and access an XSL transformer does not need to be changed. The output will be the same, but will in general be produced much faster, since the XSLTC compiling transformer will be used by default, instead of the interpreting Xalan transformer.
Note:
There is no significant difference between Xalan and XSLTC performance for a single run on a small data set, as when you are developing and testing an XSL stylesheet. But there is a major performance benefit when using XSLTC on anything larger.
Code that uses the standard JAXP APIs to create and access an XSL transformer does not need to be changed. The output will be the same, but will in general be produced much faster, since the XSLTC compiling transformer will be used by default, instead of the interpreting Xalan transformer.
Note:
There is no significant difference between Xalan and XSLTC performance for a single run on a small data set, as when you are developing and testing an XSL stylesheet. But there is a major performance benefit when using XSLTC on anything larger.
JAXP 1.3 provides the standard XPath API for evaluating XPath expressions. We encourage users to use this API. Xalan-interpretive is not included in the reference implementation. If an application explicitly uses the Xalan XPath API to evaluate a standalone XPath expression (one that is not part of an XSLT stylesheet), you'll need to download and install the Apache libraries for Xalan, put them on the classpath.
This change does not affect applications that confine themselves to using the standard JAXP APIs. But applications that access implementation-specific features of the XML processors defined in previous JAXP versions will have to be modified to take into account package names that changed in JAXP 1.3.
The change has several effects on previous applications:
In J2SE 1.4, the fact that JAXP was built into the Java platform was a mixed blessing. On the one hand, an application could rely on that fact that it was there. On the other, most applications needed features and bug fixes that were available in later versions.
But adding new libarires had no effect, because internal classes always take precedence over the classpath. The solution for that problem in 1.4 was to use the endorsed standards mechanism. However, that was a new mechanism, and one which frequently placed an additional burden on the end user, as well as the application developer.
The solution in the JAXP 1.3 reference name is to change the package names of the Apache libraries used in the implementation. That change lets you reference newer Apache libraries in the classpath, so application developers can use them in the same way that would use any other additions to the Java platform.
The new names given to the Apache packages in the JAXP 1.3 reference implementation are shown below:
JAXP 1.1
JAXP 1.3
JAXP org.apache.crimson
-/-
com.sun.org.apache.xerces.internalorg.apache.xml com.sun.org.apache.xml.internal XSLT org.apache.xalan
org.apache.xpath
org.apache.xalan.xsltc
com.sun.org.apache.xalan.internal
com.sun.org.apache.xpath.internal
com.sun.org.apache.xalan.internal.xsltc
Applications that specifying system properties on the command line with -D, in the JRE's lib/jaxp.properties file, or by hard-coding them into the application, generally do so in order to access functionality that is not present in the standard APIs.
JAXP 1.3 contains many new additions. When upgrading such applications, it is advisable to look for standard APIs in the javax.xml.* packages that will do the same job, because that's the best way to keep from having to change the application in the future. If absolutely necessary (either because of functionality restrictions or lack of time to investigate the new APIs), the property values can be changed by converting old-format package names into the format:
org.apache.somePackage --> com.sun.org.apache.SomePackage.internal
Similarly, internal implementation classes all use the new package names. If your application is using implementaton classes (it shouldn't!) those package names will have to change, as well.
While XML does not allow recursive entity definitions, it does permit nested entity definitions, which produces the potential for Denial of Service attacks on a server which accepts XML data from external sources. For example, a SOAP document like the following that has very deeply nested entity definitions can consume 100% of CPU time and large amounts of memory in entity expansions:
<?xml version="1.0" encoding ="UTF-8"?>
<!DOCTYPE foobar[
<!ENTITY x100 "foobar">
<!ENTITY x99 "&x100;&x100;">
<!ENTITY x98 "&x99;&x99;">
...
<!ENTITY x2 "&x3;&x3;">
<!ENTITY x1 "&x2;&x2;">
]>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=...>
<SOAP-ENV:Body>
<ns1:aaa xmlns:ns1="urn:aaa" SOAP-ENV:encodingStyle="...">
<foobar xsi:type="xsd:string">&x1;</foobar>
</ns1:aaa>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
A system that doesn't take in external XML data need not be concerned with the issue, but one that does can utilize one of the following safeguards to prevent the problem:
entityExpansionLimit
system property.


Ejaz Shah refutes rumors of deal with opposition
by https://www.facebook.com/dunyanewsISLAMABAD (Dunya News) – Federal Interior Minister Ejaz Shah on Tuesday clarified that there is no deal or NRO in case of Nawaz’s removal from ECL.
Talking exclusively in Dunya News program “On The Front,” he said Nawaz is being given health facilities on human grounds and Asif Zardari can also avail heath facilities if medical board recommends so.
He said PM Imran Khan had barred ministers from doing politics on health on Nawaz Sharif and provided all possible facilities. He said PM Imran listens to his ministers, adding that a person is put or removed on ECL on the recommendation of institutes and cabinet approves it.
Shah said PM has said that Nawaz can get his treatment abroad but it does not mean he stays there for whole life.
Answering about JUI-F’s Azadi March, he said every one gave opinion on the sit-in and we never created hurdles in the path of March.


Share a joke
Category
All
Programming
Miscellaneous
Dark
Pun
Spooky
Christmas
Blacklist
NSFW
Religious
Political
Racist
Sexist
Explicit
Share in Chat
Share as notification


National Spatial Planning Data Repository
Integrated Spatial Planning and Land Use Management
Data Repository
The NSPDR Ecosystem enables the sharing of spatial planning information across all spheres of government, as well as the private sector, and supports key objectives of the NDP, and most importantly, SPLUMA. [Learn More]
E-Lodgement
From the very beginning, our application was developed with SPLUMA at the centre of the design process. Resulting in a workflow that’s completely aligned both with the act itself, but also its regulations. [Learn More]
New Planning Paradigm
The CHALLENGE for any planning framework in South Africa, has always been the question of how to balance the technicality of spatial planning and land use management, with the broader issues of socio-economic development.
Data Repository
A digital and innovative ecosystem for national spatial planning, that will enable the sharing of spatial planning information and data across all three spheres of government.
E-Lodgement
This application’s main objective is to honour the Department’s responsibility in terms of SPLUMA, by fully automating the land development application process.
Enable SPLUMA
With mechanisms to support and strengthen provincial and municipal capacity to adopt and implement an effective spatial planning and land use management system.
Participatory Framework
The NSPDR Ecosystem will enable sharing of spatial planning information across all spheres of government and the private sector and will support key objectives of the NDP.
Implementing Policy
The NSPDR Ecosystem will be a major enabler in the implementation of SPLUMA. Two ways this will be achieved is by providing provinces and municipalities with . . .
... integrated development planning across the spheres of government as required by key planning policies and legislations such as the NDP.
... the necessary tools and capacity building to enable SPLUMA-compliant spatial planning and land use management practices.
Responsive Technology
Cross-browser compatibility:-
Works in all modern browsers . . .
Enables sharing of
spatial planning data.
The NSPDR ecosystem will ensure the most up-to-date integration of government project data for efficient and effective spatial planning. It enables the sharing of spatial data throughout the country, across all spheres of government including the private sector, through and with the guidance of the SDI Act.
Capital expenditure
represented spatially.
The NSPDR ecosystem will support the monitoring of all capital and operational expenditure within the public sector (which currently is not done in a collaborative manner), through the digital representation of such projects spatially. Furthermore, the level and access to data will have modern encryption and security protocols to ensure sensitive data is protected where needed.
Visually monitored
decision-making tools.
The NSPDR ecosystem enables management to monitor contributions and data maintenance by all departments through a comprehensive, visual monitoring dashboard system.
By indicating the status of the contribution, as well as the status of the individual projects themselves, the ecosystem ensures planning is done with the most recent information at hand.
Land use innovation
through automation.
Currently, there’s only one online portal which is accessible in just two provinces that can assist municipalities with spatial planning and land use management issues.
Addressing this deficiency, the NSPDR ecosystem through it’s E·Lodgement application, provides a portal readily available to all municipalities in all provinces, thereby ensuring national coverage.
[Learn More]
Data Driven Spatial Planning
The NSPDR Ecosystem will ensure up-to-date integration of most government project data for efficient and effective spatial planning. It will also enable sharing of spatial data throughout the country and across the public and private sectors.
Spatial Data
Source datasets and models derived from spatial data provided by base data custodians, SDF guidelines, as well as the E-Lodgement application layer, can be used to design customised data models, validations and a whole lot more.
Geo-Analytics
The portal hosts and contains an amazing variety of advanced GIS tools and functions. The portal will be the main place where users can access various web maps, mapping services, metadata, and E-Lodgement amongst others.
E-Learning
This easy to use platform is dedicated to help create and achieve an environment that appeals to everyone’s learning levels. It allows learners to acquire skills faster, retain knowledge longer, and apply these skills in the real world.